3 ms·
Instead, when you've gotten to X ability level, go ahead and make something at X ability level, don't let learning about a new, better way of doing that somethi
by btilly 14y ago
Instead, when you've gotten to X ability level, go ahead and make something at X ability level, don't let learning about a new, better way of doing that something stop you from doing it.
There is a time that this is good advice, and a time that it is bad advice. It is good when it helps you get over analysis paralysis. It is bad when it helps people justify their turning the opportunity to gain 15 years of experience into having gained one year of experience, 15 times.
There was a saying that I'm going to butcher here from PHP: "While many people obsess over the little details that don't matter and quibble over language wars, the person that knows PHP just gets things done."
Being snarky, PHP stands as an example of where you should take a step back, and learn better ways to do it.
- sukuriant 14y agoIt is good when it helps you get over analysis paralysis. It is bad when it helps people justify their turning the opportunity to gain 15 years of experience into having gained one year of experience, 15 times. Absolutely. I agree 100%. It should definitely be a case-by-case basis.