Live data from Hacker News

Don't Call Yourself a Programmer

kalzumeus.com

161–170 of 274 posts

Re: Don't Call Yourself a Programmer

#161
In most domains engineering is not the biggest challenge. The challenge is in a dozen intersecting domains that have little to do with engineering. Calling yourself a programmer is like a guitar make telling people he is a carpenter.

Re: Don't Call Yourself a Programmer

#162
post #25

Networking, networking, networking... "The classic its not what you know but who you know". Also super confidence (even if your wrong). I wish it was different but then again I'm not smart so maybe I'm glad :)

I agree. However, I have begun modifying it slightly to describe what I think to be the true objective of what networking is: "It is not what you know but who knows you".

Re: Don't Call Yourself a Programmer

#163
71~94: Your equity grant is worth a lump sum of money which makes you about as much money as you gave up working for the startup, instead of working for a megacorp at a higher salary with better benefits.

Or phrased differently, you get to work for a startup you believe in and enjoy instead of a soul-crushing megacorp, with (almost) no cost.

This counts as a win in my book.

Re: Don't Call Yourself a Programmer

#164
I love corporate, boring, "soul-crushing" work. Why? Because I can sit down, whip out a basic CRUD form with a small approval cycle in a day. It saves a company 100K over the year, I am loved by the customers, and because it is so simple, it normally requires no maintenance. Maybe we update the fields once a year or so.

At the end of the week, I've already saved the company more than my salary. After a year, I am a critical asset to the company.

After 3 years, I've optimized everything, the ROI slows down, and I move on.

This pattern is not a tragedy. It doesn't crush your soul. It makes you a prized commodity in the business world, with a chance to make a change in your life every few years.

I have usually alternated between 3 years doing this, then 2 years doing startup work. It has given me a much broader base of experience and skill than anyone who stick to one one side of the coin. It also has given me years of experience in large industries (banking, energy, etc.) which I then use to find very real problems to which a startup can be applied.

I have led a very satisfying career, doing this for almost 20 years now.

Re: Don't Call Yourself a Programmer

#165
post #8

>>"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…

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 sayi…

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

#166
post #46

Earlier quoted context omitted.

Assuming he had a green light on the project itself, and it creates value, I don't see why that would be selfish.

Suppose the OP leaves. It's going to be hard for the his former coworkers to maintain the Ruby app.

Hard for them to maintain, or they wouldn't be as inclined to, if it were written in their language du jour?

Re: Don't Call Yourself a Programmer

#167

Okay, I guess as someone with hard-won expertise I'm duty-bound to take slight exception to this line: Put a backpack on and you can walk into any building at any university in the United States any time you want. First, the nitpicking: Technically you can't get into Harvard's excellent libraries without actually (a) being a Harvard student, or (b) working for Harvard. (And if you're a programmer, I'm not sure which…

> It's not that great a career; you have to love it to stick with it forever.

Many are driven to stick with it because if they don't, they'll get deported.

Re: Don't Call Yourself a Programmer

#168

Earlier quoted context omitted.

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 sayi…

Or to put in a comic-friendly way: "It's not who you are, it's what you do that defines you".

Agreed, I'm doing programming.

Re: Don't Call Yourself a Programmer

#169
post #71

Does anyone else think that this article is in poor form? On the perils of describing yourself as a programmer: If you're hiring someone to provide a specific skill set (programmer) you want them to be good at programming. Would you hire an accountant if they didn't know accounting? Should lawyers not describe themselves as lawyers? Doctors as doctors? On the perils of selling yourself as an expert in a certain techn…

Reprising a comment of mine from earlier: the actual work performed by most lawyers is letter-writing at $X00 an hour. No lawyer describes themselves as a "professional letter-writer" or "professional letter-writer specializing in Mostly Empty Threats." When "programmer" starts showing up with lawyer and doctor on "high status occupations used as the canonical examples of professional jobs since you were three years…

How about a surgeon? Their actual core competency is performing surgery. Should they not describe themselves as Surgeons?

Edit:

Are accountants high status? I'm not sure. They are generally regarded as making a fair bit of money but they are boring. Probably a bit more high status than a programmer, perhaps. But I wouldn't suggest to my accountant friends that they stop selling themselves as experts at accounting.

And anyways, high status = social status, and how is that relevant to any of your points? Social status is mostly useful for when you're trying to get laid (because that's mostly when you are trying to impress people) or prove something to your parents. We, as programmers, still get paid very well and are valued by many many companies.

The lack "high status" thing in comparison to doctors and lawyers is just because:

A) Laywers and doctors generally make more money. A lot of lawyers and doctors make over 200K. Programmers, not so much.

B) Laywers and doctors are almost certainly better educated than programmers. This education is validates a person in lots of ways, in that you are automatically learned about a variety of topics with which to converse with at parties, and that you are smart enough not only to perform as a lawyer/doctor but to achieve the level of education necessary to do so (unlike programming, where you only need to be good at your job and not necessarily good at 6+ years of higher ed).

C) The laywer and doctor professions have been around longer and are therefore safer. Doctors are the most ancient and historically valuable professions. Laywers, not nearly as much so, but for the past few hundred years they have emerged as a staple profession. I like law a lot but I would devalue lawyers over doctors a bunch.

D) It's harder to become a lawyer/doctor than a programmer, so it's a bigger achievement.

E) The jobs generally require more social skills than working with computers.

Programmers will probably never be a high status job because of the above reasons. But that doesn't really affect your argument, which is describing how you should sell yourself to potential employers.

I'd like to reiterate that I'd prefer to well rounded people who are good at programming and specifically good at our tech stack. That's the ideal. Take classic ASP.NET programmer and tell him to write a complex Ruby on Rails project and watch him flounder for months no matter how good he was at ASP.NET. There's just a lot to learn. Now, for someone who is more seasoned, used to unix, used to working with actual HTML+CSS+Javascript (instead of .net controls) used to writing tests, used to dynamic languages, that person will adjust fast, but not everyone will.

Re: Don't Call Yourself a Programmer

#170
post #66

Earlier quoted context omitted.

what? your last: - 'you can strive to be unique in a one-person class that is more immediately profitable and scalable than a commodity programmer.' seriously? if this guy wants to become an expert in the technologies he mentioned then why is that so wrong? if he enjoys programming and has the drive to get to the top then he should absolutely go for it. smart employers are going to appreciate and see value in someone…

Think back to the now-wealthy Googler who wrote the code that 97% of $BILLIONS in revenue passes through. Do you think that person introduces him/herself as "C++ programmer with 10+ years of industry experience"? You'll get better work on better terms if you focus on results rather than tools, even if your technical skillset is fundamentally the same as another dev with a poorer sales pitch. You're finding the best m…

Say that person leaves google and spends all his/her money. What jobs do you think that person will be most qualified to apply to next?

Senior C++ Programmer jobs.

And what do you think they'll have to prove to potential employers? That they are capable of writing lots of C++.

Post reply on HN