I have the ultimate version that works really well:
0. don't touch with a barge pole articles about "things that software developers should know"
A collection of things software developers should know
81–90 of 175 posts
Re: A collection of things software developers should know
#82Missing 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.
Re: A collection of things software developers should know
#83Re: A collection of things software developers should know
#84This 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?
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.
Re: A collection of things software developers should know
#85Every Programmer Should Know LISP
I disagree; every programmer should definitely know a Lisp; and a bit about LISP just for a historic perspective.
Re: A collection of things software developers should know
#86Earlier 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.…
> Whether or not you enjoy something is not always good metric for said thing's long term effects on your life.
But isn't this the very definition of judging"?
When people say "get a life", they are implicitly saying that you current life isn't up to measure (by their own values).
Re: A collection of things software developers should know
#87This 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…
7. 'Dilbert' is a documentary.
Re: A collection of things software developers should know
#88Also, 'What every computer science major should know' by Matt Might:
Re: A collection of things software developers should know
#89The title of this should be:
Links for SW developers to look things up if needed
The claim that SW developers should know all of these things is plain ridiculous. I'd consider myself a fairly successful hacker (sold my small startup to BigTecCo and worked there for a while, licensed them some other code, now working on my own startup again). And I'd say I know perhaps 10% of what's on this list and I have a basic (not very detailed) understanding of maybe 40% more. The other 50% I have no idea about.
However I do know a fair amount of stuff (in detail!) related to my field that's NOT on this list and that's what sets me apart.
So bottom line: Use these lists to look things up. Specialize in what you like until you're really good at it. Be open to learn new things. But don't let anyone tell you that you do need to know all this stuff before you're a "real software engineer".
Re: A collection of things software developers should know
#90Every Programmer Should Know LISP
> Every Programmer Should Know LISP
Seriously, yes. Every programmer that wants to perform as high as possible, should grok Lisp, or a Lisp dialect. It makes sense, since they are "programmable programming languages."