How can I make my Claude more strategic than tactical?
So for context, tactical and strategic programming is back on debate these days because of people claiming ‘coding is solved’.
In fact the way common people use AI is to build a feature in a big codebase and claude can build it quite easily, but did it do it in a way that is maintainable over time and architecturally sound?
For example: you can tell claude to make a button and sure it will make you a button. It’s gonna make you that button so fast, you will be impressed. However, over time in the course of coding you notice it has been creating the same button from scratch every single time. It should have rather made a shared button component and reused it any time it had to make a button!
So coding is solved, yes, as long as you are talking about tactical coding. But how do you solve strategic programming with agents? I am not a super senior engineer but I do care about code base maintenance and health and sound architecture decisions.
What are some ways people using Claude to prevent it from AI slopping your codebase over time?
Posted Sep 5, 2026, 4:01 PM UTC