Passion doesn't even correlate with outside events OP lists.
Little point having a side project when your employer often asks you to sign a contract giving them ownership of all code inside or outside of work. I've walked away from job offers because they wouldn't strike this.
Where's the passion coming from in the 90 of 100 programming jobs that are programming payroll, fuel pump displays, stock systems and the 1,001 other not exciting, not full stack, not web dev role? OK, there's probably someone, somewhere, who can get passionate about fuel pump programming, but...
Also consider the employer's point of view. Unless junior code-monkey is needed, and even then, I would far rather see a well rounded individual with some non-IT to the fore. With at least a fighting chance of some social skills and some other interests than discover all free time is spent at the laptop working on other stuff. It can help when understanding client needs, or bring the idea from the model engineering or some other hobby to the task at hand.
As with almost everything, balance is the key. If, as a parent, you can't read one programming book a year, or spend a couple of weekends worth of time on a bit of tinkering there's something wrong. The reason a lot of parents end up no longer developers is they probably became senior enough that they're herding cats (staff) instead of bits.
So I'll stick with DHH and heavily favour work-life balance.