I mean there’s the art of software architecture, and there’s also generating a pile of shit code.
As it so happens, it takes experience to learn software architecture.
Anyone can code, there’s really zero skill required if you have a working brain.
Actually scaling software (not just performance but also organizationally so thousands of engineers can be productive and maintenance can be manageable, or managing a monolith or bunch of microservices whatever) takes skill.
I follow design patterns in my code and I tell AI to follow various rules. Like using layers as a low hanging fruit so it doesn’t jam crap into a single file. Single responsibility so it doesn’t write functions that do 10 things inside it. And so on.
Comments
Can you expand on that?
I mean there’s the art of software architecture, and there’s also generating a pile of shit code.
As it so happens, it takes experience to learn software architecture.
Anyone can code, there’s really zero skill required if you have a working brain.
Actually scaling software (not just performance but also organizationally so thousands of engineers can be productive and maintenance can be manageable, or managing a monolith or bunch of microservices whatever) takes skill.
I follow design patterns in my code and I tell AI to follow various rules. Like using layers as a low hanging fruit so it doesn’t jam crap into a single file. Single responsibility so it doesn’t write functions that do 10 things inside it. And so on.