I think it was implied through the conversation but the other thing I have come to realise is that your hobby and craft should be about producing not consuming. Too many people think they like videogames or films and think they should therefore work in the industry only to be crushed by the industry. Even being a youtuber devolves into hours of storyboarding, editing and engagement farming which are orthogonal to your hobby.

With respect to code it's a little murky but I guess the tension really is enjoying the process enough while being able to output the desired quality, volume and velocity required of you.

Quality is usually the stickler because it's invisible to the end user and requirement setter but sometimes quality affects both ergonomics and future delivery and sometimes it's purely self-satisfactory. That isn't a value judgment, making things well is a gratifying and edifying experience - so much so that this practice overlaps with Shinto philosophy.... but not many people are going to pay you to have that experience.

We're not that far into this new era and I already see people go back to hand-writing the important bits and manually designing their architecture because it turns out that unless you have them spit out yet another boring web app, they aren't very good engineers at all, their errors and bad decisions are very hard to predict and accumulate over time, and the resulting mess becomes unmaintainable at some point, and it appears all the harness engineering in the world can only stave that off somewhat, not prevent it from happening. So perhaps IT won't become a monoculture of agent prompters after all.