[another_twist]

I disagree. The real fun is in solving problems. Real user problems are harder than toy coding problems. Contact with users is what gives the craft meaning. Notions such as good code, clean code when chased as goals become stale too quickly. Good code is code other people can read, nothing more. Clean code is code that is modular and flexible enough for the near future. Next up are feature requests and feedback cycles which is the real fun part.

[lowlystatsguy]

Yeah, I actually don’t disagree with you. I’m speaking from my experience of being told that we don’t even want to modularize the code. It’s just slap the keyboard and make it work literally as fast as possible. The craft is anticipation of user requests, and not building it out in the moment, but knowing how to build it so it’s a smooth transition to the next feature. When you lose the ability to think (what I equate to focus time) before doing, you end up with unhappy developers, users, and managers. Every time I have tried to advocate for thinking first vs. doing first in my circles, I’ve met strong resistance akin to the perfectionistic claims. Even unit tests are seen as developers simply wasting time to make a product perfect despite said product already having hundreds of users and processing millions of dollars daily.