Re:Don't Call Yourself a Programmer
by icebraining on Saturday October 29, 2011 @05:08AM
(#3171532)
I think the point is to make your job description less technical, not more. You're not a programmer, you're "the guy who made $X for your company last Y".
[ Parent
| on HN ]
Doesn't that depend on what sort of job you're trying to get? If someone is hiring for embedded systems development, and your resume has no details about your technical skills, but lots about Providing Value, there's a good chance they're going to wonder if you're technically qualified. They certainly won't be impressed if your attitude in the interview is: ok, sure, I don't yet know all of these details, but anyone can pick up a language in 3-4 weeks; did I mention I'm really good at creating business value?
That's a good point, it's not just about what you do, the effects matter. But again it fits into the scoring social points game and making yourself look extra important to companies.
Re:Don't Call Yourself a Programmer
by dpritchett on Saturday October 29, 2011 @02:37PM
(#3172475)
It's not just social points, it's access to fulfilling work. The better you do at conveying your unique value, the more likely you are to find someone who's willing to pay you appropriately for work that's right at the edge of your abilities. If you don't market yourself properly you'll be stuck on an HR salary scale (e.g. Programmer III at 105% of standard compensation) doing fungible work.