News for hackers. Stuff that matters.
Re:Don't Call Yourself a Programmer by credo on Friday October 28, 2011 @10:00PM (#3170835)
>>"Programmer" sounds like "anomalously high-cost peon who types some mumbo-jumbo into some other mumbo-jumbo." If you call yourself a programmer, someone is already working on a way to get you fired.

I call myself as a programmer because I enjoy programming and do a lot of programming as part of my job.

It is unlikely that I'll get fired because I run the (tiny) company I work for :). and customers seem to like the products we sell in the app stores.

Prior to starting this company, I was a Principal Development Manager,SDE Lead and Software Design Engineer at Microsoft. Describing myself as a programmer or a developer didn't hurt me there either.

This is not to say that Patio doesn't make a good case about the need to focus on value created. Regardless of profession, you have to focus on the value you create. A doctor saves lives, a construction worker builds homes, a pilot takes people home etc.

It is definitely possible for all of them to use MBA-speak mumbo-jumbo job-titles to describe what they do. Alternately, one could be a bit more of a plain-speaking, straight-talking person and just say that you're a doctor or a programmer or a pilot etc.

Re:Don't Call Yourself a Programmer by mechanical_fish on Friday October 28, 2011 @10:40PM (#3170908)
Once you run the company it doesn't matter what you call yourself. That is probably a great topic for another essay, assuming PG hasn't written it already.

It might matter what you call the company or the product, however, since that is the brand that the people who pay you are seeing.

Programmers are so literal. Let me try and translate: When Patrick says "don't call yourself a programmer" he isn't necessarily saying "never use the word 'programmer' in the same sentence as your own name". What he's saying is: When someone asks you what you do all day, don't just say "I program... stuff" or "I program in Lisp". What do you program? Why? What value do you create thereby?

Re:Don't Call Yourself a Programmer by angelbob on Friday October 28, 2011 @11:16PM (#3170969)
Right. I might say "I'm a computer programmer", but I usually say it right after "me and five other guys track everything about all video plays for ESPN.com" or a rough equivalent.
Re:Don't Call Yourself a Programmer by mechanical_fish on Friday October 28, 2011 @11:24PM (#3170988)
See, there you go, that is awesome.
Re:Don't Call Yourself a Programmer by Jach on Saturday October 29, 2011 @02:43AM (#3171351)
I'm a programmer. I program things. What, specifically, changes pretty frequently still. Going into detail can be useful when trying to score social points from the smalltalk question of "So, what do you do?" But depending on what you program, I think for most people "programming" is sufficient compared to "I currently write software to manage an elastic computer server farm running data analysis jobs for people."

In fact I think the former "programming" can give you more social cred--if you program things the other person can't comprehend an immediate use for, it may hurt you. "Oh you're one of those people that don't do anything useful." If they really want to know, they'll ask, and ask for more details if they care.

Of course, I agree in general that when whoring yourself out to the corporate world it's best to make yourself sound as important as possible as long as possible, which is basically what I got from Patrick's post. "Programmer" doesn't contain enough information to make you seem important enough in BigCo. It's fine for scoring social points.

Re:Don't Call Yourself a Programmer by lazerwalker on Saturday October 29, 2011 @02:01PM (#3172385)
If you were a carpenter, you wouldn't tell your friends "I hammer things all day", you'd tell them that you make things out of wood. I'd argue that the fact that you spend your day "programming" is more of an implementation detail of the bigger picture that your job is to create software.
Re:Don't Call Yourself a Programmer by forensic on Saturday October 29, 2011 @03:33PM (#3172593)
If you were a carpenter, you'd tell your friends you're a carpenter.

If you were a janitor, you'd tell your friends you're a sanitation worker.

If you were a stripper, you'd tell your friends you're an exotic dancer.

Patio is saying we should say "engineer" instead of "programmer" because programmer has similar connotations to janitor.

Re:Don't Call Yourself a Programmer by screwt on Saturday October 29, 2011 @05:30PM (#3172862)
In my experience, 'engineer' has closer connotations to janitor than 'programmer'. Certainly in the UK, engineering as a profession has a big image problem because the average person doesn't distinguish between e.g. a heating engineer (who fixes the boiler) and say, a civil engineer (someone with a Masters degree + 4 years professional experience and accreditation).

People I know who are programmers all have professional jobs and by and large are earning more than those I know who are engineers. That's probably not a representative sample of 'programmers' though.

tl;dr: 'engineer' doesn't sound too professional either, at least in the UK. IMO Software Developer sounds better than either, and that's what I tell people I am.

Re:Don't Call Yourself a Programmer by forensic on Saturday October 29, 2011 @07:35PM (#3173132)
In North America an engineer is either a train operator, someone with a university degree in "Engineering", or a programmer. So you can see the difference.
Re:Don't Call Yourself a Programmer by LargeWu on Saturday October 29, 2011 @11:21PM (#3173549)
What you describe as an engineer would probably be called a technician here in the US - somebody with a relatively specialized skill set whose responsibilities are mainly operation or maintenance of equipment or systems.
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".
Re:Don't Call Yourself a Programmer by _delirium on Saturday October 29, 2011 @10:30AM (#3171944)
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?
Re:Don't Call Yourself a Programmer by Jach on Saturday October 29, 2011 @08:08AM (#3171705)
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.
Re:Don't Call Yourself a Programmer by nassosdim on Saturday October 29, 2011 @08:57AM (#3171759)
Or to put in a comic-friendly way: "It's not who you are, it's what you do that defines you".
Re:Don't Call Yourself a Programmer by bad_user on Saturday October 29, 2011 @09:06AM (#3171782)
Agreed, I'm doing programming.
Re:Don't Call Yourself a Programmer by jtheory on Sunday October 30, 2011 @11:27AM (#3174566)
Another way to frame this point -- that's kind of like asking a novelist what they do, and having them answer "I type out sentences, in English".

No, even if they started with "I'm a full-time writer", they'd follow up with "well, I've had two novels published -- I guess you'd categorize it as literary fiction? -- and I'm finishing up the draft of a third."

If you are a "programmer", what does that mean? Do you do anything of value? To whom? Do you know? Or do you program whatever you're told to program (inasmuch as you can figure it out, and it's their problem if the specs were bad) because that's how you earn your paycheck?

If you're in the latter category, and that's the only thing you grasp about the work you do, that's a pretty big limiter on your future.

Re:Don't Call Yourself a Programmer by kennywinker on Friday October 28, 2011 @10:14PM (#3170855)
It's a very business oriented article.

E.g. "You’re in the business of unemploying people. If you think that is unfair, go back to school and study something that doesn’t matter.)"

I for one have created more jobs than I've destroyed in my coding career. By building a business, as you've done, you're going in the opposite direction of this kind of sentiment.

Re:Don't Call Yourself a Programmer by emmett on Saturday October 29, 2011 @01:09AM (#3171191)
Don't take this the wrong way, but ... really? I find that hard to believe. Pretty much all programming is in the short term unemployment producing, since pretty much all programming is automation. Automating a job means that no one does it anymore, hence one fewer job.

In the long run those people are usually repurposed into productive work, and there are occasional moments where a programmer will create a massive number of jobs (see: whoever implemented adwords, creating an entire industry of professionals to optimize purchasing them). But that's the exception, not the rule.

Re:Don't Call Yourself a Programmer by scottschulthess on Saturday October 29, 2011 @09:49AM (#3171858)
There are types of programming that create jobs, but you're right, most of them eliminate jobs while making the rich (owners of our companies) richer. Which kind of sucks if you think about it.

The programming that creates job is the kind that sells to consumers. Pretty much any consumer product will create jobs. B2B will eliminate jobs. Most programming is B2B (I think...) because it's easier to take money from other companies.

Examples of programming that creates jobs:

Games

Iphone Apps

Todo lists

Products that make money by showing advertising

Re:Don't Call Yourself a Programmer by mseebach on Sunday October 30, 2011 @09:30AM (#3174309)
> Which kind of sucks if you think about it.

Yeah, it totally sucked that the tractor came along and eliminated all those coveted farm hand jobs. Software is the tractor of our time.

> Pretty much any consumer product will create jobs.

Such as the iTunes store that overnight closed pretty much every single brick-and-mortar music store in the world (mild, but only mild, hyperbole)?

> Examples of programming that creates jobs:

Games doesn't automate a physical task, but it's silly to assume that they haven't displaced other kinds of entertainment, say, perhaps, comic books. (I consume neither games nor comic books, so I'm speculating)

Whether an iPhone app has destroyed or created jobs depends on the app, after all it's just a computer program like any other. Take magazines and newspapers: There is NOTHING these businesses would like better than to shut down their printers and distribution divisions. Those are, if anything ever was, pure cost centres. Also, any app that lets you do something from your phone that you otherwise had to call a call centre to do probably isn't exactly a job creator.

I don't know how todo-lists earned a spot on the list, but there is no reason to believe that they (and any other "productivity" app, say, a good e-mail client or calendar app) don't, on the margin, raise the barrier to needing a personal assistant/secretary.

Advertising online is just one example of the lower-barriers-to-everything that the Internet has facilitated. Whether the Internet is a job creator probably depends on who you ask: A self-taught Rails dev or a Borders employee.

EDIT: My point, which took a little while to crystallise, is that at businesses the things being automated away are larger and have individual accounts, so savings/consequences are very visible. When you download NYT to your iPad, they don't fire three guys in the printshop, they need a small fraction of one of them less. When you send an e-mail to your mother, a fraction of a person in the mail- or greeting cards industry is less needed. Etc.

Re:Don't Call Yourself a Programmer by redthrowaway on Sunday October 30, 2011 @04:41AM (#3173943)
If you work for a publicly-traded company, then you aren't really "making the rich richer", or at least not totally. Some of the biggest investors are pension and mutual funds, so it's quite likely that the success of your company is being shared by many fairly ordinary people.
Re:Don't Call Yourself a Programmer by guard-of-terra on Sunday October 30, 2011 @07:12PM (#3175676)
As pg pointed out, everybody should be concerned with creating more wealth instead of creating more jobs.

There are economies where are a lot of jobs (low unemployment) but very few wealth and it doesn't seem to stick regardless of what they do. You probably don't want that.

As long as you do your job of creating wealth you can hope somebody else to work at improving wealth distribution process.

Most of programming either creates wealth or conserves wealth, which is a good thing.

Re:Don't Call Yourself a Programmer by maaku on Saturday October 29, 2011 @03:42AM (#3171453)
Either you're in a Cost Center or a Profit Center. As nearly all day-to-day programming is automation of some kind, costs are cut by eliminating menial labor. Revenues are increased by selling that automation to customers and clients. The sad sorry truth: your software puts people--somewhere--out of a job, thus saving money for that person's employer/customer. That's your value proposition.

Now of course, the economy on the whole is not a zero-sum game. But you don't see that at the micro-economic level. It is rare indeed that a programmer creates new jobs without negative consequences somewhere else in the world...

Re:Don't Call Yourself a Programmer by angusland on Friday October 28, 2011 @10:21PM (#3170870)
I think he was merely responding to the idea of unfairness by pointing out much software automates jobs away.