4 ms·

read project code from a year ago. also have a person review your code in a language you are new to.

• unfunco 12y ago
  I would suggest this also. Every so often it's humbling to look back on your older code and think about how you might write it differently. If you cringe with frequency, you're likely improving.
  • atwebb 12y ago
    Agreed, if you don't cringe either you were already pretty good or you still don't know the same things you missed before.
    • nostrademons 12y ago
      Or you've changed focus. I look at my old code from 10 years ago and on a line-by-line aesthetic basis, it's pretty good. It's probably better than the code I wrote yesterday, given that I haven't yet setup my IDE to reformat it into a consistent style... But that's exactly what's changed in the last 10 years. Now I consider my code in the context of the world around it, and don't waste time doing things that I can get machines (or other people) to do for me. So while my actual code has gotten worse, I'm much more inclined to use third-party libraries and frameworks when appropriate to solve problems. The problems I solve are more important to me. I pay more attention to how the code fits into the rest of the world around me than how it looks inside.
  • deleted 12y ago
    [deleted]
• myth_buster 12y ago
  Going through your previous implementation gives one sure sign of whether you are improving. When on a steep learning curve, its very easy to spot bad implementation. It's akin to getting your code reviewed by someone with additional year of experience. Although, some of the mistakes you spot may be attributed to perhaps your enhanced domain knowledge but you will be able to distinguish between the two. Additionally, to remain on the steep learning curve, I think its imperative to expose yourself to well written code and solving different set of problems.