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.
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.
Excellent advice. But, you're assuming the OP wants to play "business" game instead of "programming" game, which is not necessarily true, and is not implied in the post.
You mean you have hundreds of people asking where Mankrik's wife is?
More seriously - what do you mean?
Obviously this idea doesn't eliminate all support requests, but I imagine it would reduce the deluge over time.
[1]: http://www.hilarymason.com/blog/ignitenyc-how-to-replace-you...
How does what you recommend make you a better programmer? Coming from a business background, I'd say I already have relevant domain expertise and decent soft skills. I don't really see how spending yet more time on those strengths will do much to improve my very mediocre coding abilities.
Like the comment above, my advice is learn how to deliver software instead of just program. Learn how to interact with customers and become an expert in your business' domain. In addition, learn how to solve real problems without using technology or programming.
Being a great programmer will get you in the door for an interview, but it is all the other soft skills that will get you the job (and the money that you want).
Don't forget, that 10 years of experience could just be 1 year repeated 10 times. A cardinal number of years doesn't always equate to increasing breadth of knowledge.
In my experience, someone with really strong domain expertise in something like bioinformatics, doesn't actually have 10 years building websites on MySQL.
1. Has built websites for 10 years
2. Websites have all been on MySQL
3. Is a verifiable domain expert in a field that is useful to you but isn't programming.
I'm also not that knowledgeable in MMORPG terms, but I do know things like "drops" and "PVP", and I can deduce other terms.
Just saying, it doesn't really sound like you.
I used http://www.standards-schmandards.com/exhibits/rix/index.php and copy pasted the grandparent comment in - got a reading ease score of 58.
Copy pasted some answers from http://www.anyasq.com/227-i-made-bingo-card-creator - got a reading ease score of 59.
Close enough for government work, I think. I never knew that patio11 played World of Worldcraft?
Edit: Oops, just read the response above me, learn something new every day. And no serious critiques of my methodology please, it was just for humor's sake. :-)
Have you seen this video? http://blip.tv/business-of-software/patrick-mckenzie-marketi...
A note with regards to specs: you may be tempted to dump all your points into the Programming tree. Don't. It gets nerfed every few years anyhow, and respec costs will be murderous. Instead, spread some points into Soft Skills and Domain Expertise. Get the ult in Domain Expertise and you'll melt your competitors' faces regardless of their programming ability on virtually any raid except Next Google. (P.S. Expected rewards per hour on that raid are terrible, since everyone wipes. If you're good enough to do it you could AFK your way through any number of raids, pick one of them instead.)
Many developers get deeply into debates over who has the best class. "My class is better than your class" doesn't kill mobs, no matter how many times you repeat it.
Improving one's grinding skill can improve gold per hour marginally, but understanding the economic meta-game has a much, much better ROI.