As a long-time web/app developer getting into game dev, it feels like I'm entering "the big leagues" of software engineering. Tougher problems, more problems, more _interesting_ problems, and problems without prebuilt solutions. Much more fun than making yet another dashboard.
Combining player control, multiplayer, non-player control, and physics is one of the tougher problems. I got it handled (enough) for my project, but I'd be very interested to read the source if Easel's physics engine gets open-sourced.
Theory and practice are both important. A few analogues:
- fundamentals on an instrument vs performance
- low-level graphics programming vs using a game engine
- comp sci vs software engineering
The theory side here gets to the root of things, is valid for any sort of DAW/DSP software, and has the benefit of being easier to teach. Practice is obviously more important though, especially in the arts. It's better to grope in the dark than do nothing.
Living in LA, the LAPD helicopter noise really is incessant.
It's hilarious to hear flying cops try to be intimidating through when dispersing illegal concerts or singling individuals out in non-violent crowds. It's impotent posturing and an obvious waste of money. They really don't need to send 5 squad cars and a helicopter for noise complaints.
I will say though that the loudspeaker on those things are surprisingly clear, even through the buzzing of a helicopter.