| ▲ | paladin314159 12 hours ago | ||||||||||||||||
I echo this sentiment. Even though I'm having Claude Code write 100% of the code for a personal project as an experiment, the need for thinking hard is very present. In fact, since I don't need to do low-thinking tasks like writing boilerplate or repetitive tests, I find my thinking ratio is actually higher than when I write code normally. | |||||||||||||||||
| ▲ | jernestomg 12 hours ago | parent | next [-] | ||||||||||||||||
I'm with you, thinking about architecture is generally still a big part of my mental effort. But for me most architectural problems are solve in short periods of thought and a lot of iteration. Maybe its an skill issue, but not now nor in the pre-LLM era I've been able to pre-solve all the architecture with pure thinking. That said architectural problems have been also been less difficult, just for the simple fact that research and prototyping has become faster and cheaper. | |||||||||||||||||
| |||||||||||||||||
| ▲ | Aeolun 12 hours ago | parent | prev | next [-] | ||||||||||||||||
And thinking of how to convey all of that to Claude without having to write whole books :) | |||||||||||||||||
| |||||||||||||||||
| ▲ | exodust 8 hours ago | parent | prev [-] | ||||||||||||||||
Agreed. My recent side projects involve lots of thinking over days and weeks. With AI we can set high bars and do complex original stuff. Obviously boilerplate and common patterns are slop slap without much thinking. That's why you branch into new creative territory. The challenge then becomes visualising the mental map of modular pieces all working nicely together at the right time to achieve your original intent. | |||||||||||||||||