Live data from Hacker News

A collection of things software developers should know

github.com

101–110 of 175 posts

Re: A collection of things software developers should know

#101

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.

Yeah but Version Control is absolutely a must.

Re: A collection of things software developers should know

#102
post #84
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?

Not trying to offend, but . . . > If I enjoy xyz, who are you to judge me for that? I find this (common) sentiment troubling and frankly a bit arrogant. Whether or not you enjoy something is not always good metric for said thing's long term effects on your life. Other people have experienced different things than you and may have some really good insights. Assuming you know exactly what's best strikes me as arrogant.…

> Judgement and ostracization, while often misused, are effective tools for a society to encourage beneficial behaviours.

Conforming behaviours. Not beneficial. One could argue that conforming to mainstream is beneficial for the society, though I personally don't buy it - if you look at what the average of human interests is, it's all pretty petty. If we were all stuck at the lowest common denominator, I'm not sure if we would get far as a civilization.

Now, one good argument I've heard for following the "mainstream wisdom" on "getting a life" is regret - i.e. that if you won't live a life in a particular way (lots of social interactions, focusing on a spouse and kids, etc.) you'll regret that on your deathbed. I'm still relatively young (in the lower half of my expected lifespan), so I might be wrong about it, but I don't buy that argument either. I've come to the conclusion that regret will happen anyway - people basically regret what they didn't do. If I focus on cranking out widgets, I'll regret not spending time with the kids. If I focus on my family, I'll regret not doing anything actually useful with my life. Etc.

Bottom-line: I think that currently, the pendulum is still too far on the conforming side.

Re: A collection of things software developers should know

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

It probably would have been better worded as "Work to live, but don't live to work. Don't make your job your whole life."

"Get a life" has always at least had a negative undercurrent, and is often an overt insult implying that one's entire lifestyle is unworthy, and inferior to mainstream lifestyles.

Re: A collection of things software developers should know

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

Yeah, when I say that I do code as a hobby so I spent some free time on it, a reaction I get quite often from coworkers is: "I already code at work". Or "I would rather spent my time having fun".

Oh well, it is not for everyone. :-)

Re: A collection of things software developers should know

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

You're getting bent out of shape from a harmless common refrain to the general HN readership - not you - in a well-meaning context? Yeah, get a life.

Re: A collection of things software developers should know

#106
These are the other things that a developer should know -

1- Focus on the problem and not the tools ceremony around it. 2-Don't follow the herd and the hype. When given a problem, keep drilling the problem until it is absolutely clear to you and then only work on solution.

Meta-habit: learn to adopt different habits for different situations. With that in mind, some techniques I've found useful for various situations:

When developing for yourself or a small team, let problems accumulate and fix them all at once (or throw out the code base and start anew). When developing for a large team, never let problems accumulate; the code base should always be in a state where a new developer could look at it and say "I know what this does and how to change it." This is a consequence of the reader:writer ratio - startup code is written a lot more than it is read and so readability matters little, but mature code is read much more than it is written. (Switching to the latter culture when you need to develop like the former to get users & funding & stay alive is left as an exercise for the reader.)

Re: A collection of things software developers should know

#107
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

friends and/or a membership in a community can be nice too, and is one of those "often correlates highly with happiness" kinda things, so i'm just adding specificity from my life to an item in your list.

Re: A collection of things software developers should know

#108
#1 is stay humble. If you're humble you will never stop striving and learning to get better. By the way, that's probably the most important thing for everyone, not just software developers.

Whenever I think i'm hot shit I go watch some SpaceX videos on YouTube. That gets my feet back on the ground and my nose to the grindstone pretty quickly heh.

Re: A collection of things software developers should know

#110

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…

5: no. Sometimes an idiot is an idiot and if you have a real one in the team, sanity requires either of you change job
Post reply on HN