How I Became a Better Programmer
There's a lot of value here, but I have to raise concerns about a few things.First, the title: written in the past tense makes it seem like he believes the journey is complete.  The article itself doesn't convey that message, fortunately.  But I think it's worth noting that a critical skill for a professional is constant education - don't be satisfied that you're already "better", get better every day.I also strongly disagree with the suggestion that you should ignore the form of your code.  Code is read many, many times more than it is written, so improvements to your own and your teammates' understanding can pay huge dividends.In particular, the advice to "not worry about" DRY and duplicate freely reveals a common misunderstanding.  DRY shouldn't be taken literally, it is a recognition that repetition is evidence of some greater underlying truth.  By duplicating freely rather than thoughtfully avoiding duplication, you're just creating opportunities for bugs.