3 ms·
I code, but it hasn't been advantageous to call myself a programmer for a while now.
by patio11 16y ago
I code, but it hasn't been advantageous to call myself a programmer for a while now.
- s-phi-nl 16y agoWhy not? What do you find advantageous to call yourself instead.
- younata 16y agoa hacker.
- dbz 16y agoI call myself a coder because I write code. I don't hack, crack, or (verb)script-kiddie, so I won't refer to myself as a hacker, cracker, or script-kiddie.
- kanwisher 16y ago*sigh I would hope people would understand the title of hacker on this website. Hint it has nothing to do with security
- mahmud 16y agoBut wouldn't it be nice if some script kiddie misunderstood and got hooked? A sample IRC log might look like this: SC1: yo dog, long time SC1: still haxoring Wordpress modules? HNer: naah man, WP is gey HNer: I am busy hacking Supply and Demand SC1: wtf? the economic model? HNer: yeah, making something people want -- SC1 has quit IRC (Quit: Leaving.)
- dbz 16y agoIt would be wonderful. But my point on not calling myself a hacker is not because I don't "hack supply and demand," but I don't "hack" stuff in general. Hack can be used correctly in two totally different contexts (not mistaken with crack), and that is the good helpful kind of hack.
- petercooper 16y agoSure, but this thread was about what it's "advantageous" to call yourself. Calling yourself a "hacker" in front of 99% of clients is not going to get you off to a good start.
- zackattack 16y agoexcept in front of silicon valley MBA types who're vaguely familiar with four steps to the epiphany
- nmcfarl 16y agoWell I'm in the parent's shoes - and I usually call myself a "Founder" or something along those lines.
- patio11 16y agoAt my former job, a programmer is the guy who transforms this instruction into Java code: "The 16th digit in the CSV is a field with 1 representing that the student is excused from the English speaking exam. Such students are to have their English written exam score proportionately increased such that it makes up 100% of the point allocation for the English subject, but it is not to be altered in reports showing sub-subject scores." A software engineer wrote that instruction. My company hired me as a software engineer, not a programmer (to the extent we had any of those, they worked in low-wage countries). I do not call myself a programmer around consulting clients because I charge much more money than my programming skills can justify. Most of them do not need a title to understand my skill set, since they asked for me in the first place, and to the extent I have one it is as "the guy doing X for us" (X is usually a combination of programming and marketing). "Founder" isn't too big in Japan, so I usually introduce myself as some variant of "Owner of a company." It is ridiculously superior to "programmer" in terms of social status and sets me up for an automatic conversation topic (given my age and pallor, "How the heck did that happen!?" is a common one).
- nostrademons 16y agoInteresting. At my job, a programmer (well, software engineer, but there's not all that much of a distinction) is someone who translates this instruction into some combination of C++, Python, Sawzall, JavaScript, and various custom languages: "Make users happy."
- derefr 16y agoThis may be a philosophical point, but unless you're a game designer, that sentence has to end with "...by increasing the odds that, and the ease with which, they will succeed in their goals." You can make people happy by just giving them opiates :)
- nostrademons 16y agoThat's actually a good but controversial point. My employer has recently made a number of changes that measurably increased the odds and ease with which users achieved their goals, but were met with widespread user unhappiness. Similarly, there was one recent feature I was involved in that was universally lauded as being a fun little easter egg, yet wasted several million hours of productivity worldwide. It's an interesting balancing act between giving people what they want and giving them what they need, and while we tend to err on the side of giving them what they need, it can sometimes be hard to do so when they hate us for it.
- watty 16y agoMy response to what I do is "computer stuff" and then I change the subject...
- angstrom 16y agoTuring Completionist?
- mechanical_fish 16y agoThis tallies with my pet hypothesis about programmer career paths. It is commonly observed that programming is a young person's game: there are lots of teenage and twenty something programmers but fewer and fewer as you look at older and older age groups. This is sometimes blamed on age discrimination, and sometimes on the idea that programming is an exceptionally terrible career. My hypothesis is that the "problem" with programming is that it has too much upside potential: If you learn to program, have a couple more skills than just programming and can keep your wits about you, you can find lots of business and professional opportunities... most of which carry job titles other than "programmer". You move up to "software engineer", and then you become "manager of X" or "founder of Y" or maybe you're just "the guy who does Z" where Z is something that makes money for the company, like marketing or strategic research or manufacturing operations. The most significant piece of code I ever wrote was written when my official job title was "product engineer", which kind of means "troubleshooter". My job title and description had nothing to do with software; software just happened to be what I did all day, every day, (not to mention a fair number of nights) in order to help make the company millions of dollars by finding manufacturing bugs more quickly.
- patio11 16y agoI agree, strongly. It is the same story in languages, too -- the difference between a "translator" and a "international business consultant" is a better suit and about, oh, $200~300 an hour.
- dawsdesign 16y agoThis is because we become managers :)
- dkersten 16y agoyou can find lots of business and professional opportunities We (Python Ireland user group members) recently held our own PyCon and I got chatting to a recruiter who confirmed what I was already thinking: that the "recession" hasn't really affected software devlopment jobs. Apparently there are loads of development jobs out there that pay above average. But, like you said, few of them have "programmer" job titles.
- tocomment 16y agoWhat are some better titles career-wise (in the US)?
- sbov 16y agoMy title is technically "software developer", so I just use that. Most jobs nowadays seem to use "software engineer" instead. I generally am not a fan of software engineer, because most software seems to involve a much higher level of trial and error than traditional engineering disciplines. To me, engineer implies a level of guarantee that usually can't be provide in most software systems. In extremely critical software systems the developers are probably software engineers, such as if the presence of a single bug in your code would cost someone their life or waste billions of dollars.
- Daniel_Newby 16y ago> I generally am not a fan of software engineer, because most software seems to involve a much higher level of trial and error than traditional engineering disciplines. Software engineers just have a very high standard for "it is now complicated enough". If an engineer is forced by circumstance or insanity to add lots of features to an analog circuit, they end up in the exact same tar pit as the software engineer. Ditto for chemical processing plants, jet engines, etc. In fact, the usual approach these days is to move a lot of non-software complexity into software when possible, so trial and error becomes a feature.
- ikbear 16y agoI am just a graduate student, i want to code more, but in fact i don't have to code. I just have to write damn papers, i hate it. So, i am not a programmer actually
- gaius 16y agoHere's the thing: no-one can make you be a manager. You might be aware of the downsides, sure, but managers aren't pressganged. So by and large, the people you find in management ranks are the people who wanted to be managers and not programmers. This is important because these people hold the budget and ultimately make hiring and firing decisions. Another factor is that angling for promotion is a full-time job in its own right. You can't do the maneuvering necessary and produce code. There just aren't enough hours in the day to schmooze at meetings and do work at a comparable rate to your peers who are mainly working. A manager considers him or herself "successful" and looks back at their own career and doesn't see that they were perhaps a mediocre programmer themselves (or actually bad and given a promotion so they wouldn't be able to break stuff[1]). Then they look at a candidate who is still programming after 20 years and they see a "failure". That's why ageism is rife in the industry. [1] It's very very difficult to fire someone these days. So you "promote" them sideways to get them out of the way. Problem is a couple of years later everyone has forgotten that, and their next promotion is a real one...