[aristofun]

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.

[fedd]

I would agree but I am adding the people that pay for the coders work into this equation ("managers"), and they need function in time. Some (most?) of them seem to consider the design decisions the coders problem. It's in the coders interest to make the code easily expandable, integrable, reusable, readable, to make the coders life easier, to allow them to easily meet the business goals.

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

[afarrell]

> only accumulate through experience

You need both experience and also reflecting on that experience —-- usually in a social process.

[fedd]

You say "usually", so I assume googling forums for similar design decisions and having internal discussion within myself can count, without having a crowd of fellow programmers physically beside you? If you're capable to hold such an internal reflection, then basically you can "google for experience"

[aristofun]

“Internal discussions with myself” can be helpful. But on their own they will never get you very far.

Unless you’re already very experienced and talented to build your own unique path.

[afarrell]

It depends on the quality of the conversation

[aristofun]

I consider it a part of experience process

[afarrell]

Which is reasonable. I’m making it explicit for the sake of the perplexed.

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.