Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A collection of things software developers should know

github.com

Post reply on HN
Print view View original

111–120 of 175 posts

Re: A collection of things software developers should know

#111

Post by sbov »

koolba wrote: post #58
oldandtired wrote: post #26

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…

While I agree with the rest, this one is flat out wrong: > 5. You're as much the idiot as the person you consider an idiot. I don't throw the word "idiot" around lightly but when I do, in a work / programming context, it's apt. I'd imagine I'm not the only one in that camp.

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.

Re: A collection of things software developers should know

#112

Post by barryhoodlum »

brudgers wrote: post #80
ritchiea wrote: post #60

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…

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

Re: A collection of things software developers should know

#113

Post by LoSboccacc »

Tade0 wrote: post #45
smikhanov wrote: post #30

Earlier quoted context omitted.

It can't possibly be true that there is, so he probably doesn't

He may be implying manual testing. If not, then I'm out of ideas.

I've heard stories about the outernet but it's a weird imperfect place

Re: A collection of things software developers should know

#114

Post by new_hackers »

BatFastard wrote: post #71
amrrs wrote: post #48

Earlier quoted context omitted.

There's more to Life beyond Programming - [Marriage, Love, Kids] (not a sorted list)

My list in order Kids Health Happiness Money Marriage

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.

Re: A collection of things software developers should know

#115

Post by collyw »

ATsch wrote: post #31
oldandtired wrote: post #26

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?

For someone that loves algorithmic challenges, I am sure knowing about phone numbers is going to make them ecstatic.

Re: A collection of things software developers should know

#116

Post by cname »

oldandtired wrote: post #26

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…

5a. There are some genuinely shitty people out there that don't necessarily deserve a pass just because no one is perfect and everyone makes mistakes. Dealing with such situations can be exceptionally difficult. Avoid talking shit if possible but try not to be apathetic either (for your own sake as well as others').

Re: A collection of things software developers should know

#117

Post by SAI_Peregrinus »

new_hackers wrote: post #114
BatFastard wrote: post #71

Earlier quoted context omitted.

My list in order Kids Health Happiness Money Marriage

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:

Stability, Contentment, Kids.

When your situation is stable and you're content with how things are going, then consider kids. Don't try to wait until you're rich / happy all the time, it won't work.

Re: A collection of things software developers should know

#118

Post by sbov »

bitshift955 wrote: post #6

Very glad to see "Falsehoods Programmers Believe About Names" included in this list [1]. I still struggle to always get this right. One thing I'd suggest including is something about not rolling your own crypto in the security section. Does anyone know a canonical article for this? I've got [2] bookmarked but not sure if a guide with the pitfalls of designing your own crypto scheme is right for this list. [1] http://…

I consider the names article more a thought experiment. Consider the last point:

> 40. People have names.

Good luck getting names right.

Re: A collection of things software developers should know

#119

Post by psyc »

oldandtired wrote: post #26

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.

Re: A collection of things software developers should know

#120

Post by TeMPOraL »

sbov wrote: post #111
koolba wrote: post #58

Earlier quoted context omitted.

While I agree with the rest, this one is flat out wrong: > 5. You're as much the idiot as the person you consider an idiot. I don't throw the word "idiot" around lightly but when I do, in a work / programming context, it's apt. I'd imagine I'm not the only one in that camp.

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.

Post reply on HN