Comment by hankbond

I don't know if this will bring you any comfort, but I think

> And you learn in your career that it's a bad idea to care about the code, especially in a business context, which one's career is very much trapped in the business context.

It's always been this case -- well before LLMs hard pivoted the field. You (theoretically) get paid to create net business value, you don't really get paid "to code". If the product you are creating is code, then yes the priority of code quality can be much higher. Especially in higher IC roles like Staff+, coding is just one of the ways to add that value.

At work I just have to solve the problem at hand with the minimal amount of effort to reach the first acceptable solution. After work while at play, I can explore 10 versions of something at my leisure, just to learn if I want. I can focus on working the thing until it's polished and elegant, because I decide what the priorities are. I can be as selfish as I want.

It's common in art circles that you have a series that you can churn out for money, and you have ideas you explore just for you (that often are far less appealing to non-artists). Pixar used to have a tick-tock cycle like this, "one for them, one for us". They would alternate a sequel bc it would make money and new IP because it would keep the studio fresh.

I don't think accepting this should be depressing. A good life is all about finding balance so that you can sustain it for the long haul!