Live data from Hacker News

A collection of things software developers should know

github.com

61–70 of 175 posts

Re: A collection of things software developers should know

#62
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?

The problem is until you try something new you can't be sure you really enjoy what you're doing that much. After 15 years of sitting in a chair and doing what I loved I found out I love other things just as much and I'm sad I didn't know earlier.

Re: A collection of things software developers should know

#65
post #12

Every programmer should know cpu cache read time? How many times is this going to come up. Barely anyone in the world needs to know that.

Programmers don't actually have to know how computers work either, but sometimes it comes in handy.

Re: A collection of things software developers should know

#66
post #59

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://…

> Very glad to see "Falsehoods Programmers Believe About Names" included in this list [1]. I still struggle to always get this right. In the real world, you'll constantly have to interact with external or internal systems that are based on the "wrong" concept, so implementing it "right" makes your system really awkward to work with.

The same was true about Unicode text not too long ago. If we don't start trying to do things correctly, we will never get to a better place.

Re: A collection of things software developers should know

#67
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'm not OP but I took it as 'get a life [outside of work]', i.e. don't get bogged down in the crazy 100-hour work weeks and stressing about climbing corporate ladders if it's not what you enjoy. What you do with your free time is up to you, it's just a reminder that it's your free time not your companies.

Your quoting style is simply depressing.

Re: A collection of things software developers should know

#68
post #58

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.

Agreed, there are some people who deserve the term idiot. At the same time you're probably an idiot if you call people idiots, even if they are. You're going to make your own life harder.

Re: A collection of things software developers should know

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

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…

While I agree with you in principle. I think the original poster's intent was keeping a work life balance. Work will consume you. Corporations will consume your life. You may be perfectly happy living in your work, but if you have loved ones they will suffer.

Experience has taught me don't get caught up and lose that balance. Its a long journey to recovery after you have suffered both emotionally and physically.

Re: A collection of things software developers should know

#70
post #67

Earlier quoted context omitted.

I'm not OP but I took it as 'get a life [outside of work]', i.e. don't get bogged down in the crazy 100-hour work weeks and stressing about climbing corporate ladders if it's not what you enjoy. What you do with your free time is up to you, it's just a reminder that it's your free time not your companies.

Your quoting style is simply depressing.

I'm so sorry.
Post reply on HN