Live data from Hacker News

Do call yourself a programmer, and other career advice

yosefk.com

91–100 of 123 posts

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

#91
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…

"Daddy, how is software made?" "Well, when a programmer loves an idea very much they stay up all night and then push to github the next day"

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

#92
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…

"Daddy, how is software made?" "Well, when a programmer loves an idea very much they stay up all night and then push to github the next day"

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

#93
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…

"Daddy, how is software made?" "Well, when a programmer loves an idea very much they stay up all night and then push to github the next day"

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

#94
post #85
post #84

Earlier quoted context omitted.

I've recently found myself in a leadership role as well, and I don't think it has to do with whether people are business types or not. Humility is necessary to fit in with peers and to get along with superiors. Confidence is necessary to influence people (be they peers, superiors, or subordinates), and you can't manage without influence. A piece of advice I've seen in a couple places is to focus on service, whether t…

Edit: Yes, I know this sounds kind of... angry and juvenile. Bitter. That is what I meant when I said that I clearly don't have the correct solution. a big part of the problem is that I don't even know what most of these words I'm using mean - And honestly? I think it's "confidence[1]" that other people say they do. Of course, I know I'm not competent enough in that area to know that for sure. >I've recently found my…

It's like entropy: the emotional bullshit in a closed system only increases. Until one person leaves, or you bleed off the pressure outside it.

With negotiation, my understanding is that the real negotiation starts weeks beforehand, because the game is about getting an information advantage, enough to make the other side's shady tactics irrelevant. All the nonverbal skills are just used to hide the math layer of the exchange. Assuming you can't dump the shady opponent for one who thinks win-win, but even then having more information can't hurt.

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

#96
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.

I'm going to regret this joke, but: I posit the difference lies in how much cache you need.

well done.

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

#97
post #50

Earlier quoted context omitted.

My replies to your points: 1. Do you have stats? In absolute terms, a whole lot of people hiring programmers have programmed themselves. How do you know the other people hiring programmers are "the vast majority"? (I sincerely wonder about it. I cited two numbers by two bloggers, one says it's 80% of the cases, the other says 90%. I have no idea, but I intuitively feel it's less than 50%. Are there real stats?) 2. I…

1. There are far more non-programmers than programmers. Even with a correlation between being a programmer and hiring programmers, it is plausible that the vast majority of hiring managers are non-programmers. This becomes more plausible if you step back a layer to the budget allocation for headcount rather than specific hiring decision.

Isn't it also plausible that after the first programmer hire (by non-programmer), any subsequent hiring will at least involve this first programmer?

I would even go as far as saying that an 'expert opinion' from a programmer would typically be involved in the hiring decision (be it from an external consultant, a friend or what not). Given that the non-programmer would typically realise they don't have themselves the skills to evaluate programming abilities or CVs.

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

#98
First of all, taking patio11 too seriously is a sing of having inadequate mental representation of so-called reality.

Ironically, there is some unintentional truth is his blogpost - one really shouldn't call oneself programmer, because what he described is a dumb coder. Programmer could realize what is blogging, not vise versa.)

A programmer (one who understands how things works and why) will easily avoid such scenarios like ending up in a coding sweatshop or toxic things like PHP, Java or JavaScript. It is obvious that one should avoid certain things, like one avoids scams, frauds or just wrong things.

Real programmers, such as rtm, pg (god forbid!) sysoev would always find a niche for oneself and a project to do. The difference is that they themselves would choose what to program and why, not someone else.

Another point is about whose opinion one should value and why. Programmers usually does not care what "talking-heads" are broadcasting, intuitively and correctly anticipate that there would be zero useful or even interesting information for them. It is like to read, say, Oracle's press-releases and PR pamphlets about mysql instead of actual Changelog files.

So, right, do not call yourself programmer if you're mere a coder or blogger. There is some truth in it.)

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

#99
post #21

Earlier quoted context omitted.

That's pretty funny. In case anyone's wondering, the full term is "garota de programa", literally "girl of program" or "program girl". Obviously, the English is "call girl". Normally, "programa" just means events, like "what's the program for the evening?". Here, of course, you can figure it out yourself.

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

Guys, please keep this stuff on /r/programming. The signal to noise ratio on HN is already bad enough.

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

#100
post #73

Earlier quoted context omitted.

This so obvious I'm amazed that it isn't discussed every time this topic comes up. Programmers seem to think that there is something "dirty" about adjusting your language according to audience.

> Programmers seem to think that there is something "dirty" about adjusting your language according to audience. Yes. I am struggling with this right now, myself. I mean, not specifically that, but this general idea that putting effort into social bullshit that has little to do with my actual competence is dirty. It really /does/ feel dirty, and I have a difficult time articulating why. The problem is that I have mov…

Have you done any study on our current understanding of the brain and cognitive science?

[http://www.npr.org/templates/story/story.php?storyId=1290271...]

not everyone agrees on the above model, but I think its safe to say that the part of the brain that deals with leadership existed before we invented civilization .. wolves have leadership, apes have leadership. So much of social nonverbal communication probably comes from the primitive, instinctive part of our brain, not the logical, planning part.

I think if in the past you had to deal with some really irrational people, and you were intelligent enough to be able to use logic to figure out their bullshit, at some point in your life it was probably really helpful to just reject all irrational bullshit. At one point in my life it was really helpful to me to suppress all instinct and rely solely on logic. But since then, seeing how some completely illogical people can in many situations be more efficient than me in navigating life's obstacles, I have had to learn from my mistakes and revise my behavior. I do think social nonverbal communication is ethically neutral. It's not the smartest behavior, but it is faster than the smartest behavior, and there are many situations where that ends up being more important. Not all. Unfortunately at this time I do not know of any better way to figure out which is which other than experience.

Post reply on HN