this. an immediate family member is a prosecutor. as a software engineer who loves hard problems and agree that few professions rival the mental strain of hold

this. an immediate family member is a prosecutor. as a software engineer who loves hard problems and agree that few professions rival the mental strain of holding that problem in memory, but i can attest as to just how strong the parallels are between trial prep and architecting complex technical solutions. I can't speak for doctors, but the mental models required for non-trivial jury trails could rival those i've encountered during my career as a software engineer. one could probably even argue the analogy the lead prosecutor is a backed developer building system of arguments for logic meeting definition of law, ensuring redundancy and failover in event of error condition (new evidence, evidence struck, motions, etc), all while playing role of pm+designer creating the interface delivering accessible content in a way meaningful to the user (jury). again, i can't comment on other professions, but capital cases were the closest thing i've seen to hours/stress/effort of early stage start ups--with the difference being failure meant you live knowing a murder/rapist walked free, instead of a shitty exit or returning to a "boring" enterprise job. and then there's the imprint left once the project/trial is over. over the years, i've noticed that interesting/hard problems (the ones we dream about) tend to leave an imprint on my thought process on how i view complexity (e.g. the world). except for us developers/engineers, we just carry some vignette of organizing complexity, instead of being haunted by nauseatingly detailed accounts of how some asshole murdered his wife and children, or other sickening acts that prosecutors, cops, journalists, etc are required to become immersed into the details of. now that i think about this, it's almost funny how easy we engineers/developers/designers have it.