It's okay to mourn the craft of hand-writing code as AI takes over programming, but programmers should see themselves as builders whose broader craft—deciding what to build and how it should feel—won't be replaced.

181:36architecture? I don't think agents will replace all of that. Yeah, like, just the, the actual art of programming, it will, it will stay there, but it's, it's gonna be like knitting. You know? Like, people do that because they like it, not because it makes any sense. So the... I read this article this morning about someone that it's okay to mourn our craft. And I can... A part of me very strongly resonates with that because

182:07in my past I, I spent a lot of time tinkering, just being really deep in the flow and just, like, cranking out code and, like, finding really beautiful solutions. And yes, in a way it's, it's sad because that will go away. And I also get a lot of joy out of just writing code and being really deep in my thoughts and forgetting time and space and just

182:43being in this beautiful state of flow. But you can get the same state of flow... I get a similar state of flow by working with agents and building and thinking really hard about problems. It is different-... but... And it's okay to mourn it, but, uh, I mean, that's not something we can fight. Like, there is... the world for a long time had a... there was a lack of intelligence, if you s- if you see it like

183:10that, of people building things, and that's why salaries of software developers reached stupidly high amounts and then will go away. There will still be a lot of demand for people that understand how to build things. It's just that all this tokenized intelligence enables people to do a lot more, a lot faster. And it will be even more... even faster and even more because those things are continuously improving.