4 ms·
I took two things away from what patio11 said. One is to do things start to finish. Tests, deployment, faqs, code, marketing, polish, etc. You learn to appreci
by rgraham 15y ago
I took two things away from what patio11 said.
One is to do things start to finish. Tests, deployment, faqs, code, marketing, polish, etc. You learn to appreciate the people and teams around you. You also gain useful skills.
The other is to emphasize learning the most for areas that have the largest payoff. For most programmers this means stuff that isn't programming. This dovetails nicely with an idea that CrossFit points out: Pullups make downhill skiers better. That exercise has no direct functional application to downhill skiing, but improving your big weaknesses in fitness often pays off more than perfecting your strengths.
- nostrademons 15y agoI think your last point is heavily situation-dependent. What you really want to do is maximize the area of your Voronoi-diagram: the problem space for which you or resources you control are the best available solution. Sometimes the best way to do this is to eliminate a weakness, so that it's no longer a dealbreaker for people that wish to use you as a solution. But many times, the best way is to perfect your strengths, so that you're clearly better than the alternatives around you. People are willing to forgive and work around many weaknesses if you're very, very good at your strengths.