This was an interesting read: Making Python Lazy.
I thought the idea of making Python lazy was fine. But around the end he has a philosophical thought that made me think.
I spend so much time reading papers, documentation and textbooks for things I want to build and truly understand. I also very rarely find people I want to work with that understand what I'm trying to achieve.
But I digress what I've noticed about one project I've worked on after trying Claude code, is that I almost never look at the code. In the earlier stages I knew exactly what was being built and how. I knew why what I was building was important and why it was differentiated.
Upon using Claude code, I noticed I thought less. A lot less, to the point that it became challenging to care about what I was doing. It did a great job in most respects, and I would make all the engineering decisions. But I just had no passion.
While I respect the tool and the people who use it, I think I will continue to put guardrails on myself. I do not denounce the use, but I think actively deciding to use less of it will be better for me.
Using it to check bugs or push a version is fine. I cannot use it to fully automate the build of a feature or an entire project, or it calls into question what I'm even doing this for to begin with.
I believe you will become better at system architecture when you actually attempt to build the system.