Live data from Hacker News

A collection of things software developers should know

github.com

151–160 of 175 posts

Re: A collection of things software developers should know

#151
post #55

Earlier quoted context omitted.

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

Honestly most things people are uniquely passionate about that take work outside of your workplace will get you equal or nearly equal weird looks. A lot of people want to go to work to make money and come home to watch TV. I worked for Obama for America in 2008 and spent months walking door to door in Indiana, most people went to to work, took care of their kids and watched TV. And didn't want to spend time doing much else.

As more nerdy and ambitious people, we are the weird ones. Programming in your free time might get slightly weirder looks than participating in local theater or something but I think some of the scorn you perceive is residual from the hostile environment that existed for nerds in grade school and high school. After that people still think you're weird but generally don't care that much, they're busy watching TV & taking care of their kids.

Re: A collection of things software developers should know

#152
post #111

Earlier quoted context omitted.

My personal version is this: 1. Everyone is ignorant of something, so don't be condescending. 2. Everyone does stupid things, including you, but it doesn't make them stupid.

I'd add: 3. Everyone has their own incentives, which may or may not be aligned with yours or the organization you work at. Understanding them helps you understand their point of view, and to decide whether to help them, ignore them or fight them.

4. All actions are strategies to meet basic human needs. Look for the needs behind the actions. This will bring effortless understanding and compassion.

Focus on the needs and look for multiple strategies to meet them, thus staying open and flexible in the implementation.

Re: A collection of things software developers should know

#153
post #74

Earlier quoted context omitted.

There are loads of people who don't actually know how to efficiently cut the loin from a pig, tack against the wind, or ensure proper close air support while bringing even a few thousand soldiers into territory held by an enemy force... But who still post that Heinline monologue about how specialization is for insects.

Heinlein's quote I think is not to be taken too literally. It's the notion that human beings can do so many things and there's a lot of synergy in knowing that many things. You'll start seeing connections between one and the other and solve problems in activity A while doing activity B. It's fun too! I might not know how to butcher a pig, but I know multiple programming languages, multiple human languages, I ski, I c…

You could probably butcher a pig. It's not rocket surgery.

Re: A collection of things software developers should know

#154

Earlier quoted context omitted.

He obviously touched a nerve. Maybe you should think about why rather than continue with this ridiculous overreaction?

That was an explanation, not a reaction.

Right. People from all over the world read and write comments on Hacker News. It's a big and diverse audience where not everyone is a native English speaker let alone an American in Silicon Valley. That's part of what makes commenting fun, interesting, and challenging...at least for me.

Based on the rest of the comment, I don't think a charitable reading is unwarranted. But that does not mean someone's negative reaction is unwarranted either. "Get a life" can be and is used as 'fighting words.'

Re: A collection of things software developers should know

#155

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 have had some fun reading the responses. So I'll add some commentary to my list.

1. I have been programming for nearly 40 years, even though I now care full time for my wife, I still create and modify various programs nearly every day. I am a geek, but talking with people (especially the young, including my children, my grandchildren and my nephews and nieces) opens my eyes to different wonderful perspectives. Learn new things every day, and share with people every day, it's a wonderful way of living. As well as that, there is a cultural difference between the US and other places. Get a life is about rounding out as a person. Programming is but one small aspect of our lives as people. As a geek talking with my geek nephews we often talk about geek things, but our conversation get quite broad. I suppose the one thing I am glad about is that none of my children became programmers.

I have a high functioning autistic grandson. His younger sister and brother have no such problems. Watching them and seeing them grow is an incredible, delightful and wonderful experience. Seeing my grandson in operation has opened my eyes to who I am and the slight autism that I have. I see him look at the world in a light that is so unique. I have seen and shared in other autistic children lives over the years and the universe is a more wonderful place for them being in it. So when you go and get a life, see the unique, wondrous world around us, especially in the people whose lives you interact with.

2. After nearly forty years programming, arrogance (I am very specific about using that word) is an occupational hazard for all programmers. We often forget that we really don't know everything. Good ideas come from all sorts of places. Been there, done that and have watched so many go down the same path.

3. There are many different programming "religious" wars. Many times each side has a valid point that can be used in conjunction with each other. So keep learning new languages and their basic concepts to see what is useful to you as a programmer. Understanding different conceptual bases often will give an insight in how to solve problems at hand.

4 Pretty self explanatory.

5. I thought this one was self explanatory as well, but, here goes. It doesn't matter how much knowledge you have in a specific area, if you start treating people as imbeciles and idiots for their lack of knowledge or the "silly" (are far as you're concerned) questions they ask, you have become very much what you consider them to be. In reality, we know little, and it should be fun to share our knowledge and in turn share in the viewpoints of others. This was a lesson I have had to learn a number of times over many years. There are no "silly" questions.

6. How many of you over your time of programming have had "critical" deadlines to meet which were no more critical than the specific coffee blend you have in morning? There are many who believe their project is of a "critical/important/world shattering" nature and yet if it misses by weeks or even months or never even reached completion, the world still goes on. You do what you can, you don't kill yourself over inconsequential things.

[Have made an edit to slightly more comprehensible]

Re: A collection of things software developers should know

#156
post #78

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…

And, arguably most importantly - 7. If you see a skunk, just slowly cross the road to the other side.

Here it would be, if you see a tiger snake, run like hell.

Re: A collection of things software developers should know

#157
post #119

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'm unable to think of any definition for the word "idiot" that would make number 5 generally true. "Human" doesn't work. "Imperfect" is closer, but still doesn't quite work since almost everybody readily admits that already. It's certainly not true that everybody is equally incompetent. Nor is everyone equally rude, or equally impulsive, or equally stubborn.

See my explanation above. I have learned the hard way to recognise that though there are obtuse and pigheaded people who will not listen to anything you say and are extremely difficult to deal with, don't for a minute ever treat them as an idiot.

I have dealt with various people over the years who are very intelligent and very expert in their fields of endeavour, yet will treat you as a idiot if you don't comport yourself with a total respect for their opinions and viewpoints. If you raise a question that they believe is irrelevant, their responses head rapidly south to treating you as an idiot.

Re: A collection of things software developers should know

#158

Earlier quoted context omitted.

Really? It would seem that: Happiness, Health, Money, Marriage, Kids would be the correct order to process these tasks? Without the previous item(s), the latter item is harder to obtain and maintain at full functionality.

Be careful with that. There's a growing body of evidence that waiting too long to have children causes some disorders. EG Autism is far more common in children born to older parents. Money is an especially difficult one, as it's very easy to move your own goal continually upward. Happiness is also difficult, since it's almost always going to be a transient state and not a long-term thing. A better list is probably: S…

Stability is relative. Contentment and kids are an oxymoron.

Don't wait is true. Than again, don't get married to someone you can't stand just to have kids.

Post reply on HN