3 ms·
Oh, I don't know how hard it is to get better. All you have to do is point yourself at challenges that are harder than what you've previously done, and then do
by eli_gottlieb 14y ago
Oh, I don't know how hard it is to get better. All you have to do is point yourself at challenges that are harder than what you've previously done, and then do them. Sure, that's a local optimization process that will be prone to reaching local maxima, but you can always broaden your view to find a larger challenge.
- dpritchett 14y agoMost of us spend more time on our day job and its dev problems than we do on extracurricular learning. Finding a job (or academic post) that is set up to help you push yourself consistently is the trick. Most dev jobs don't inherently scale difficulty up to match your constant skill growth. "Good" work (at least the metered, someone-else-is-paying-for-it kind) is subject to a lot of competition.
- michaelochurch 14y agoI wrote about this a fair bit: http://michaelochurch.wordpress.com/2012/01/26/the-trajectory-of-a-software-engineer-and-where-it-all-goes-wrong/ http://michaelochurch.wordpress.com/2012/01/26/the-trajector... It's hard to get to (or even near) the 2.0 level without continually getting high quality work. That kind of work is rare in the corporate world and most people never get it. It's also hard to push yourself to a 2.0 level if you can't work on it full time. Now, a neat thing about side projects is that they don't have to be 2.0+ to be useful and successful. There are other things that matter just as much. That said, if your goal is to become a 2.0+ programmer, you'll pretty much need access to a quality of work that most developers never get to do at their paid jobs.