> Or is this shower-type thought safe to chuck in the receptacle of non-sensical but good sounding ideas
Regardless of veracity, having an answer is reductive beyond the point of utility.
Like, yeah, it's reasonable to infer that someone who has chosen a career in programming might enjoy a nice game of Factorio. But beyond that, what is actionable or predictive about knowing?
It's worse than that. People will start making the hidden little assumption that the complexity of a deliverable is strongly correlated with the practitioner's propensity for complexity.
It's just blaming developers for bad software with extra steps. Instead of considering the dozen bigger factors that lead to shipping imperfection, we just have another reason to pull out the tired old excuse of blaming the programmers and their broken nerd brains that focused too hard on nerding instead of delivering business value.
No I totally see your point I think people are too unfair to programmers in general - seeing software as a cost center and not appreciating the complexity or difficulty inherent in it - and I get how even the question suggests a kind of negative stereotype that might damage people's interactions with non-programmers, for sure.
I came at it from a more positive viewpoint - not of the connection with complexity being a bad thing, but just exploring the dynamic and wondering what it means for us. I think a lot of the answers are really interesting tales born from that experience of working with it day to day, and I think wrestling with the complexity of the world is central to what we do. Celebrate our heroic victory, dance with the complexity of the world! :)
Regardless of veracity, having an answer is reductive beyond the point of utility.
Like, yeah, it's reasonable to infer that someone who has chosen a career in programming might enjoy a nice game of Factorio. But beyond that, what is actionable or predictive about knowing?
It's worse than that. People will start making the hidden little assumption that the complexity of a deliverable is strongly correlated with the practitioner's propensity for complexity.
It's just blaming developers for bad software with extra steps. Instead of considering the dozen bigger factors that lead to shipping imperfection, we just have another reason to pull out the tired old excuse of blaming the programmers and their broken nerd brains that focused too hard on nerding instead of delivering business value.