Formula: show up, comment on everything to improve your personal brand, bend every conversation to your personal narrative, speak very authoritatively with flowery down-to-earth gosh darn folksy language, and stay sufficiently out of the way so you can't be harshly judged (half term gov = "microisv").
My opinion about this is proof in itself it works. I just get annoyed realizing other people have programmed my brain without my express consent.
At its genesis, coding is problem solving. We are trying to solve someone's problem(s) using a computer. All the coding skills in the world won't help us come up with solutions to people's problems if we lack the ability to listen to the end user, translate their needs into code, and then explain to them why they need this and how it solves their problem. Also, I've found that developing your non coding skills also gives you different perspectives into problem solving.
One is to do things start to finish. Tests, deployment, faqs, code, marketing, polish, etc. You learn to appreciate the people and teams around you. You also gain useful skills.
The other is to emphasize learning the most for areas that have the largest payoff. For most programmers this means stuff that isn't programming. This dovetails nicely with an idea that CrossFit points out: Pullups make downhill skiers better. That exercise has no direct functional application to downhill skiing, but improving your big weaknesses in fitness often pays off more than perfecting your strengths.
If having more experience with different kinds of code is your idea of being a better programmer, then the OP is sufficient and more power to you.
Other people feel that a programmer's purpose is to create useful things, and the programmer who creates more useful things is better. In this light, Patrick's comment is relevant, because a little bit more domain knowledge will usually improve your program more than prior experience implementing a B-tree database.
I read it more as: don't be a better programmer, write better programs.
You missed the part where he discussed learning what to program.
While folks who leave that decision to PHBs may have good skills, I think that knowing what to program is an important part of being a good-to-great programmer.
You missed the part where he discussed learning what to program.
While folks who leave that decision to PHBs may have good skills, I think that knowing what to program is an important part of being a good-to-great programmer.
I remember you saying somewhere that you're into optimizing businesses and money is a great way to keep score, and in light of that, this comment even makes sense, but please keep in mind that for some people becoming a better programmer is not about maximizing ROI.