In the last post I proposed that the key to going from being a good programmer to a highly paid developer was a change in behavior. In future posts I’ll get into the nitty-gritty detail of what to do, when to do it, and how to know what to do. Before we get into the tactics, however, there are still a few strategy points to cover. None is more important than this one, though:
You are now in the sales business
Most programmers view sales and marketing with suspicion at best and, more commonly, disdain. Forget the people you’ve met form these departments for a moment and focus on the departments goals. The best description of marketing that I’ve read came from Seth Godin who said, "The job of marketing is to get people to know, like, and trust you." The job of sales is, quite simply, to close the deal. There are lots of books about sales such as The Little Red Book of Selling and it will help your career to read at least one, I’ve read several and they all have one thing in common: The Ask. This is probably the most important aspect of sales ever taught and in its simplest form it says:
You are unlikely to get something unless you ask for it
If you remember nothing else from this blog, please remember the line above. There is, of course, more to the sales process than just asking for the sale. The reason The Ask is so important is that without it, none of those other things matter. The future posts that talk about specific tactics are all geared toward getting a response of "Yes" to The Ask, but without asking for something, there’s nothing to say "Yes" to.
Are you shy about asking for things? You’re not alone, but by the time we get deep into the tactics section you’ll feel more confident about it and you’ll realize why The Powers That Be will actually appreciate you asking (Hint: It helps them figure out what you need. In other words you’ll be doing the hardest part of their job for them.)
Don’t miss a single post! Use the link on the left to subscribe by RSS or email.
This blog is dedicated to the career programmer – folks who make their living from turning nebulous requirements into working systems on a daily basis. If Joel Spolsky is right, and 80% of the software in the world is written for internal use, then chances are good that if you’re a programmer, you’re working in a corporate development group. The majority of programmers in corporate development fall into the "good" category so, once again, chances are that if you’re a programmer then you’re a good programmer in a corporate development group.
Chances are also good that if you’re a programmer then you are underpaid.
Actually, underpaid indicates that you’re not getting paid what you’re worth so technically you’re not underpaid – you’re simply not making as much as you can. The result is the same, though: less money is reaching you than could/should be. How do I know this? I’ve been a professional developer for more than a decade and in that time I’ve become a good programmer. Not superb, not fantastic, not even great. Just good. Solidly, smack-dab-in-the-middle-of-the-curve, no-better-no-worse good.
Despite being a merely good programmer, I’ve become a highly paid developer.
This wasn’t just a matter of luck, circumstance, or even "knowing the right people". I became a highly paid developer the same way you can: By changing my behavior. Being a Big Swinging Developer is all about behavior, not technical skills. You definitely have to be at least good and if you’re not then I recommend working on your development skills before putting ANY of the techniques on this blog into practice. Long story short, you must be able to walk the walk above all else. Being a highly paid developer is all about actually being more valuable than other programmers, but that means that you need to deliver that value reliably.
Are you underwhelmed by the generality of the "change of behavior = more money" revelation? Don’t worry, I’ll get much more specific in upcoming posts and show you how to see your job in a very different light. Use the link on the left to subscribe via RSS or email so you don’t miss anything!
In the last post I proposed that the key to going from being a good programmer to a highly paid developer was a change in behavior. In future posts I’ll get into the nitty-gritty detail of what to do, when to do it, and how to know what to do. Before we get into the tactics, however, there are still a few strategy points to cover. None is more important than this one, though: