Ask HN: How did you become a good developer?

A coworker shot me a message the other day asking how I became a "good" programmer. I don't believe I am that good - mostly average. A couple of areas slightly above average with other areas below average to counterbalance. So I tried to recount my academic, personal, and professional history. Turns out that I am very mediocre on paper, so I tried to walk him through some of the techniques I use. This is an abbreviated list of the things said in that coversation:

I keep reference books about design patterns and language quirks handy while making sure to never shoehorn them in. If it fits, use it. If it doesn't - that's fine. Not everything fits squarely into the GoF design patterns.

Use static analysis tools to look for potential hotspots, and learn why the tool would flag that snippet as a hotspot in the first place.

I don't do any serious fiddling with katas and code challenge sites unless it's exploratory. Find real-world applications instead.

I don't commit building algorithms to memory. Learn the properties, complexities and reasons for use of an algorithm. Someone has already written a bug-free version of it. Just Import it.

Also, don't be afraid to challenge the validity of a library or the code base. They were created by humans capable of screwing up. It's tough reading unfamiliar code, but it becomes significantly easier when you already know the code's intent.

Stop chasing frameworks, and start creating the most stable foundation you can. Most frameworks are templates for building and abstractions for things that have already been done plus configurable customization. Invest time in the techniques that power those frameworks. Learn how to build a single-page app without Angular, and then leverage Angular as a tool to develop instead of a crutch.