3 ms·
I would say that in my late 30's I was hitting my peak in terms of raw ability and experience. At least as far as ability is concerned, I really didn't hit a d
by mikekchar 10y ago
I would say that in my late 30's I was hitting my peak in terms of raw ability and experience. At least as far as ability is concerned, I really didn't hit a downturn until much later. Now, getting on to 50, I'm noticing that my ability to deal with complexity is quite a bit diminished. But my tolerance for complexity is likewise diminished. When I would have accepted a poorly factored solution, now I scratch my head until I find a way that allows me to understand it.
When you get down to it, do you really want to tailor your code base to the top 1% of coders? How will you sustain that practice? By paying people 4 times as much? Even then you aren't going to nab all the amazing people. Hire some people who know how to dumb down your code base. It pays dividends.
- dexterdog 10y agoYup. The "we only hire the best" thought process is delusional and irrational.
- initram 10y ago>When you get down to it, do you really want to tailor your code base to the top 1% of coders? I think I agree with your sentiment, but to me a "top 1% coder" is someone who knows how to make things simple and readable, and knows the best abstraction to use for the goal. It's not the person who can write and/or follow the most complicated code. To me complicated code is generally a sign of a poor coder. There are exceptions, but they're rare.