For me, the major insight was to realize that the best of the best are struggling just as much as myself. I often come back to this diagram for relief, and it's true.
> In the end, if you're not embarrased about the code you wrote half a year ago, it's a sign you're not progressing.
I just can't agree with this statement at all.
I have written loads of code years ago that I am not embarrassed about, but I feel that I am definitely a better developer than I was some years ago.
I really liken code to writing of any other sort. I don't feel embarrassed about everything I wrote from a few years ago. My opinions and styles may have changed, but it's not all crap. Some of it definitely is crap, though.
> In the end, if you're not embarrased about the code you wrote half a year ago, it's a sign you're not progressing.
Interesting opinion. I have that experience often enough when I look at rusty old code of mine. But I always was under the impression, that this is something of a problem, not a good sign...
Definitely a good sign. It even extends to other areas besides programming; as a non-native English speaker, at some point I was happy that I didn't really need to use the dictionary anymore. Then I realized that it actually meant that I wasn't pushing my boundaries enough and I started picking up more difficult books and learning Japanese (:
I'd replace (personally) "embarrassed" with "able to explain it's weaknesses"... And if applicable, strengths, even when that strength is "could be shipped in one week"
I just can't agree with this statement at all.
I have written loads of code years ago that I am not embarrassed about, but I feel that I am definitely a better developer than I was some years ago.
I really liken code to writing of any other sort. I don't feel embarrassed about everything I wrote from a few years ago. My opinions and styles may have changed, but it's not all crap. Some of it definitely is crap, though.