Eh. It's cute. But I learned to distinguish between "programming as a hobby" and "programming toward some productive purpose / as a job". If I'm tinkering on

Eh. It's cute. But I learned to distinguish between "programming as a hobby" and "programming toward some productive purpose / as a job". If I'm tinkering on a 1976 project car in my garage for 10 years, that's one thing. If I'm working for Mazda designing the next production model, that process is going to look and feel different! There'll be more structure and team work and coordination in one of those activities! I can "program, motherfucker" for fun as much as I want to, all day long. Nobody is stopping me! If somebody else is paying me to accomplish something on their money, schedule, and risk... There'll be some processes and procedures and accountability. The two are not mutually exclusive. And they're not specific to programming - many activities have a "weekend hobby" and a "corporate drone" version - and everything in between. We don't have it particularly bad either - difference between me playing flight Sims or even flying a cessna at local club, and an airline pilot is far more stark, in terms of processes and control. And frankly, it's mostly the "I just want to program, motherfucker!" That screw it up for the rest of us, and half the stupid management methodologies and communication failures and misunderstandings are because of folks who are too cool for school and to coordinate with their team mates. I just don't think it's that "cool" and "edgy" to think we are some particularly special snowflake type of rebel. (I might just be getting old though, I'm sure the 15 year old me would be all over that :->)