Live data from Hacker News

Do call yourself a programmer, and other career advice

yosefk.com

51–60 of 123 posts

Re: Do call yourself a programmer, and other career advice

#51
post #23
post #21

Earlier quoted context omitted.

Now I'm wondering if there is a difference between call-by-value girls and call-by-reference girls.

If only my wife's body was immutable.

I think you want a mutable wife. Otherwise you'll eventually have to throw her out and get a new one.

Re: Do call yourself a programmer, and other career advice

#52
post #5

I was having a beer in this small Brazilian town, mid-afternoon. Two girls come to my table. We try to chat ; they can't speak any foreign language and my Portuguese is awful. - Me: What is your job ? - The girls: Programma - Me (for the next 30 minutes): Oh great, me too ! Which languages ? Even "Java" didn't seem to mean anything to them. Strange. I assumed they had special programming languages in Brazil. 10 years…

You should have told them that you specialize in back-end servers.

Re: Do call yourself a programmer, and other career advice

#53

You should call yourself whatever based on the situation. If you are hanging out with a group of consultants, you call yourself consultant; if you are a special effects programmer, and talking to a model, you say you're in the movie business; if you are interviewing with the author, you call yourself programmer. The best way to connect with others is to understand how they perceive things and find ways to relate to t…

Precisely. Add to that the fact that the situations you most commonly find yourself in are the result of choices you make, and therefore the behavior serving you best is a result of these choices as well, and you'll be making the same point as I'm making - namely, that there are different paths to be taken, and you'd want to behave consistently with your chosen path.

Re: Do call yourself a programmer, and other career advice

#54
post #32

There's a major point in this article that not many commenters seem to be picking up on: there's a fork in the road of careers. To one side is a multilane highway over fairly level ground leading straigh to predictable suburbia. To the other side is an uneven dirt path leading through mountains and countryside to parts unknown and has many forks of its own. Neither path is right for everyone. And hardly anyone needs…

I'm not sure which part of what I said is described by the "dirt path vs highway" metaphor, so I don't quite follow this thread. I was speaking of a more "programmery" type of career vs a more "businessy" one. Within the continuum between the two, there seem to me to be plenty of "highways" and "dirt paths" everywhere, regardless of where you are on that continuum.

Re: Do call yourself a programmer, and other career advice

#55
post #22

I don't agree with the point about later stage options: But what this misses is that you don't get paid in percentage points - you get dollars. A $100 share going up 20% to $120 means you make $20 per share. A $5 share going up 100% to $15 means you only make $10 per share. If you join a larger company, the shares will be more expensive but you will own less of them. Percentage growth is definitely the way to measure…

If you join a larger company, yes you'll get less. If you stay in a company while it grows larger and you then negotiate for more options, maybe you'll get relatively many, as you're now rather uniquely valuable to that company. What people do instead is decide that options aren't worth it any more because how much the price will rise at this point, and ask for relatively small salary increases instead of relatively large option grants. This is doubly wrong since their salary is already pretty high at that point and there's a ceiling on salaries for various reasons that I don't fully understand but which certainly exist, while there's much less of a ceiling on option grants.

Re: Do call yourself a programmer, and other career advice

#56
post #25

No, the person he's responding to is right. In general, hiring managers don't care about bits, they care about dollars. They're going to be looking for dollars you made for other companies because that translates into dollars you can make for them. Money. It's the universal language.

Sure it's a universal language. It's also a simple one that I talk myself and I don't need anyone's help with. I'm at a mixed AI/semiconductor company. We don't need brilliant minds explaining us the obvious (or, conversely, entirely opaque) financial consequences of having written this code or that. We need people who'll do it.

Now the question is how many people there are who need you to translate their dollar concerns into the language of bits, vs how many people there are who don't have trouble doing it themselves but what they do need is people who can then write the bloody program. I have no stats and I sincerely want to see some.

Re: Do call yourself a programmer, and other career advice

#57
post #43

Earlier quoted context omitted.

Not in Canada. It's illegal here to call yourself an 'engineer' unless you're a licensed engineer. It's a protected term, like 'doctor'. So unless you studied Software Engineering, which there are many schools that teach it, and hold a P.Eng, then you can't use the term.

That's technically true in many US states as well, but I've never heard of it being enforced outside of the fields where many practitioners are licensed (mostly Civil Engineering, to a much lesser extent Electrical and Mechanical Engineering).

It's enough of an issue in Canada that Microsoft stopped calling their peons "Microsoft Certified Systems Engineer", instead using "Microsoft Certified IT Professional".

http://en.wikipedia.org/wiki/Regulation_and_licensure_in_eng...

Re: Do call yourself a programmer, and other career advice

#58

You should call yourself whatever based on the situation. If you are hanging out with a group of consultants, you call yourself consultant; if you are a special effects programmer, and talking to a model, you say you're in the movie business; if you are interviewing with the author, you call yourself programmer. The best way to connect with others is to understand how they perceive things and find ways to relate to t…

Or with friends and family: Friends => "I'm a back end web developer", Parents => "I'm a programmer", Grandparents => "I work with computers".

Re: Do call yourself a programmer, and other career advice

#59
post #30

Earlier quoted context omitted.

I hate the trend of calling people who code 'engineers.' It's just not a good title for anything to do with software. And invariably people who embrace its usage seem to be trying to compensate or ignorant of what a real engineer actually does or is.

The trend extends to other words. Sometimes I hear Programmers calling themselves Computer Scientists or Computer Engineers [1] [2] [3] when in different cases they are a Developers or a Hacker. Which they get wrong too. You are what you are. of you're acting another role you should state that you're playing that role not that you are. Ex. Computer Scientist, who can fill the role of a Programmer. This discussion kee…

What's the difference between a computer scientist filling the role of programmer and somebody who is both a computer scientist and a programmer? If you can fill the role of X competently, why can you not rightly be said to be an X?

Re: Do call yourself a programmer, and other career advice

#60
post #24
post #17

Earlier quoted context omitted.

Haha I laughed to this. Specially because I'm brazilian. And yes, it is the same word, 'program' is a slang for prostitute work. We programmers here joke a lot about this :)

It goes both ways. In the US many "consultants" / "independent consultants" refer to themselves as "whores" especially when applying their talents (for money of course) to companies or projects they disrespect.

And a lot of contractors in the UK refer to agents as "pimps"
Post reply on HN