Live data from Hacker News

A collection of things software developers should know

github.com

91–100 of 175 posts

Re: A collection of things software developers should know

#91
post #22

Earlier quoted context omitted.

I guess they should have done an AND instead of an OR? Right now it's "Every Programmer Combined Should Know"

Right, there are things that every programmer ANDED should know, but those are few.

And at that level of generality it could probably be pruned slightly more for a list of things that everybody who manages programmers or is a programmer should know.

Re: A collection of things software developers should know

#92
post #31

This is what every programmer should know: 1. Life is too short, so get a life. 2. Know that you don't know everything, so get don't arrogant. 3. Don't get caught up in the various programming "religious" wars, there's more to life than a specific point of view. 4. Laugh and enjoy the the wonderful beauty in the world around us. 5. You're as much the idiot as the person you consider an idiot. 6. Sometimes the "import…

I find that saying the phrase "get a life" to people that enjoy what they are doing is extremely condescending. If I enjoy programming all day, or having huge flame wars, or maintaining a huge collection of antique watering cans sorted by volume, then who are you to judge me for that?

I think there's a case to be made that it is possible to judge whether people's behaviours are helping them to enjoy their lives to the best extent.

It is a very extreme position to say that there is literally nothing which can be generalised about people's experiences, and so one person's heroin main-lining hobby is as good as another's model railway collection so long as they both profess an equal belief in their respective enjoyment.

There must be something more than this that we can say, since we have the distilled thoughts of millennia of some of the most capable humans thinking about these questions (what makes a good life) and lots of case histories of how people's lives have gone.

This is different from judging someone's moral worth or probity or what have you, and I think it is harmful to gloss over the distinction because it creates a kind of skeptical collapse.

This might be what the prior comment means to indicate by getting a life - that we should each individually research this question and not presume we've got a good answer already. If it is what they meant, I agree that their phrasing was unskillful.

Re: A collection of things software developers should know

#94

Missing topic: version control Obviously also missing is programming languages and e.g. good recommended books/links for each, but I understand that it's meant to be language-agnostic so listing any particular one would not work.

You don't need version control if you know Homoglyphs obviously.

Re: A collection of things software developers should know

#95

Earlier quoted context omitted.

When I'm reading HN I assume the commenters are at least somewhat similar to myself until I have evidence to think otherwise. The culture here is neither anti-intellectual nor anti-math. Given that we're on HN I'd say it's safe to assume no one is telling you to quit coding or stop caring about math. On this forum issues around workaholism and burn out come up all the time, "getting a life" is a step toward not burni…

In the US, the specific phrase 'get a life' carries the connotation of contempt for the persons to which it is offered as advice (typically unsolicited). In normal use, it is an insult that dismisses everything about a person. It isn't just used against nerds, it is also aimed at people who are doing some menial job or at a person who is complaining about some bad behavior imposed upon them by someone who tends to ge…

you're thinking about this too much. get a life.

Re: A collection of things software developers should know

#96
post #55

Earlier quoted context omitted.

My guess is in this case the original commenter means "get a life" if you feel pressured to only think about programming or work. If you are happy and fulfilled programming all day, go for it, program all day. Personally I would also encourage you to at least try and pursue some other interests because experiencing new things is fun & exciting, but if you're happy that's what's most important. But many of us, especia…

If this is how it was meant, perhaps a different phrase would have conveyed OPs opinion better. For me, "get a life" is strongly associated with "douchey jock" behaviour, bullying, nerd-shaming (is that word a thing? it is now) and phrases like "you like math? what a nerd, get a girlfriend bro", things I'm sure many people on HN have had to deal with.

As a person who lived through this as a kid, I want to express my strong support for your comment, and provide +1 data point.

IT going mainstream made life a bit easier for us - if you say you're a programmer, people no longer roll their eyes. But that's not because geeky/nerdy lifestyle is more accepted now. It isn't. If I say to my cow-orkers that I code a lot after work, most will be looking at me like a weirdo just as much as my classmates did when I was in secondary school. People who care about technology on an intellectual level - not just on a money-making level, or shiny-trinket level, are still rare and still treated as the weird ones.

Re: A collection of things software developers should know

#97
post #31

This is what every programmer should know: 1. Life is too short, so get a life. 2. Know that you don't know everything, so get don't arrogant. 3. Don't get caught up in the various programming "religious" wars, there's more to life than a specific point of view. 4. Laugh and enjoy the the wonderful beauty in the world around us. 5. You're as much the idiot as the person you consider an idiot. 6. Sometimes the "import…

I find that saying the phrase "get a life" to people that enjoy what they are doing is extremely condescending. If I enjoy programming all day, or having huge flame wars, or maintaining a huge collection of antique watering cans sorted by volume, then who are you to judge me for that?

I'm seconding this reading and I'd like to remind everyone that for many here, programming is still an intellectually stimulating experience first and a job second, if at all. Not all code - especially not the interesting one - is made at work.

I suppose GP meant "work-life balance", but for some of us, code is more part of "life" than of "work".

Re: A collection of things software developers should know

#98

This is what every programmer should know: 1. Life is too short, so get a life. 2. Know that you don't know everything, so get don't arrogant. 3. Don't get caught up in the various programming "religious" wars, there's more to life than a specific point of view. 4. Laugh and enjoy the the wonderful beauty in the world around us. 5. You're as much the idiot as the person you consider an idiot. 6. Sometimes the "import…

You don't need to know everything to be arrogant; you just need to know one complete way to build a system from the ground up and have an implementation to show it. At that point, everything which you don't know is unnecessary and the conditions are set for a vigorous arrogance to flourish.

Re: A collection of things software developers should know

#99
post #41
post #40

Earlier quoted context omitted.

> then who are you to judge me Any psychologist with a rudamentary understanding of what is required for a healthy mind. (not a psychologist myself)

Psychologists don't judge. They only try to help you if something is a problem for you personally.

Well.... I hate to tell you, psychologists judge, they just refrain from exposing their jusgement to their clientele. Psychologists, like doctors and police, are still human. Warts and all. But I get the sentiment and, like those same said psychologists, should probably have kept my opinion for me and my drinking friends =)

Re: A collection of things software developers should know

#100
post #92
post #31

Earlier quoted context omitted.

I find that saying the phrase "get a life" to people that enjoy what they are doing is extremely condescending. If I enjoy programming all day, or having huge flame wars, or maintaining a huge collection of antique watering cans sorted by volume, then who are you to judge me for that?

I think there's a case to be made that it is possible to judge whether people's behaviours are helping them to enjoy their lives to the best extent. It is a very extreme position to say that there is literally nothing which can be generalised about people's experiences, and so one person's heroin main-lining hobby is as good as another's model railway collection so long as they both profess an equal belief in their r…

I agree there's a case to be made. There's a strong case to be made. In fact, those of us who heard "get a life" shot at them probably made that case many time. The case is this: someone's hobby of tourism / enjoying cars / writing stories / riding horses / all kinds of sports / engaging in gossips and interpersonal dramas / whatever else mainstream does is at least as valid of a lifestyle as my hobby of geeking out about spaceships and writing code for fun.

This is what many of us had to (usually unsuccessfully) argue to our colleagues (and family members!) during school years, so if a full-blown dismissal of "get a life" phrase is a knee-jerk reaction, it's unfortunately a well trained one.

Post reply on HN