3 ms·

I like writing code that I don't have time pressure around, as well as the kind where I can afford to fail and use that as a learning experience. Especially the

I like writing code that I don't have time pressure around, as well as the kind where I can afford to fail and use that as a learning experience. Especially the code that I can structure myself. I sometimes dread writing code that's in a state of bad disrepair or is overly complex, think a lot of the "enterprise" code out there - it got so bad that I more or less quit a job over it, though never really stated that publicly, alongside my mind going dark places when you have pressure to succeed but the circumstances are stacked against you. For a while I had a few Markdown files that went into detail exactly why I hated it, in addition to also being able to point my finger at a few people responsible for it. I tried approaching it professionally, but it never changed and the suggestions and complaints largely fell on deaf ears. Obviously I've learnt that while you can try to provide suggestions, some people and circumstances will never change, often it's about culture fit. But yeah, outsource all of that to AI, don't even look back. Your sanity is worth more than that.

lokar 9mo ago
I wonder if some of the divide in the LLM-code discourse is between people who have mostly/always worked in jobs where they have the time and freedom to do things correctly, and to go back and fix stuff as they go, vs people who have mostly not (and instead worked under constant unrealistic time pressure, no focus on quality, API design, re-factoring, etc)
- KronisLV 9mo ago
  I’m pretty sure that the answer to that question is positive: those who have worked with code that sparks joy won’t like interacting with it closely being taken away, whereas the people for whom the code they have to work with inspires misery will be thankful for the opportunity to at least slight free themselves from the shackles of needing to run in circles for two weeks to implement a basic form because everything around it is a mess.

lokar 9mo ago

I wonder if some of the divide in the LLM-code discourse is between people who have mostly/always worked in jobs where they have the time and freedom to do things correctly, and to go back and fix stuff as they go, vs people who have mostly not (and instead worked under constant unrealistic time pressure, no focus on quality, API design, re-factoring, etc)

KronisLV 9mo ago
I’m pretty sure that the answer to that question is positive: those who have worked with code that sparks joy won’t like interacting with it closely being taken away, whereas the people for whom the code they have to work with inspires misery will be thankful for the opportunity to at least slight free themselves from the shackles of needing to run in circles for two weeks to implement a basic form because everything around it is a mess.