Good programming is not about writing perfect chunks of code or following best practices.
Its about making good design decisions. Period.
And this is something you can’t google, only accumulate through experience.
Its about making good design decisions. Period.
And this is something you can’t google, only accumulate through experience.
Of course every programmer would like to make the best design, but sometimes there's no time for it, and that's when slow/fast/experiensed characteristics come into play
You need both experience and also reflecting on that experience —-- usually in a social process.
I’ve found myself previously asking, “how do I learn to estimate?” Only to hear, “by experience”. It left me thinking for many years that I couldn’t also learn by having conversations about people’s experiences.
Unless you’re already very experienced and talented to build your own unique path.