“Domain Driven Design” by Eric Evans, aka the blue book. It’s very dense however and very object oriented, but concepts apply even if you dont work with object oriented languages, you might have to do more footwork to get from a domain model to services that adhere to the model.

“Head first Software Architecture” might be an easier on ramp and touches on simmiliar concepts.

yes, this is exactly what you have to think about. the left example even aknowledges that deadlines for “tasks” might be different from deadlines for “payments”, which suggests that the abstraction is not “clean”.

the gyro can be set to “joystick” and “as joystick” one of those allows you to limit the gyro to rotation around an axis, that should give you what you want.

you can at the very least map analog sticks to the decks gyro, i played one of the Dirt games like that. Should be great for arcade style games like sonic all stars racing or mario kart.

or from the guy who barely “survived” a zombie attack who turned right next to you while you were afk because the door bell rang.

i never was that guy, i sweare!

“logs show a reoccuring error in layer 8 everytime a subset of users engages with the system, reassigning this to the service desk to gather more information.”

i’ve read that on real ticket, i’ve laughed about it. it also makes me glad that i don’t do customer support, i don’t have the patience to keep explaining the same people that they keep doing something wrong and i lack the diplomacy skills to engage with devs that believe to be infallible and pretend that bug reports are personal insults against them.