A collection of things software developers should know
1–10 of 175 posts
Re: A collection of things software developers should know
#2I hope this list stays brief. Every list so far I observed was eventually bloated to hundreds of items (useful or not) by helpful pull requests.
Re: A collection of things software developers should know
#3I almost entirely differ in thinking these are important to know.
Re: A collection of things software developers should know
#4I hope this list stays brief. Every list so far I observed was eventually bloated to hundreds of items (useful or not) by helpful pull requests.
it's already too bloated, some are things every systems programmer should know, the SEO is things every web programmer should know. The embedded programmers don't need to know it, really. Hardly any programmer needs to know the RegexHQ one, they can look that stuff up if needed.
Re: A collection of things software developers should know
#5Every programmer should know what they don't know.
Re: A collection of things software developers should know
#6Very 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://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b...
[2] http://loup-vaillant.fr/articles/rolling-your-own-crypto
Re: A collection of things software developers should know
#7Very 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://…
"Not rolling your own crypto" originally meant "do not design your own new algorithms without peer review".
It is a pointless HN meme to apply this to implementing crypto (ok, the C haters here won't have a clue, but that is a given).
Re: A collection of things software developers should know
#8I hope this list stays brief. Every list so far I observed was eventually bloated to hundreds of items (useful or not) by helpful pull requests.
That's because the people who make them don't know what pedagogy is. This is lazy pedagogy. It's like leaving a kid at a library instead of at a school.
Why do we have schools and teachers, when libraries with big lists of things to read have existed for hundreds of year?
If you want the answer to that spend a year or two looking at what good pedagogy is preferably with someone who is highly skilled at it.
Re: A collection of things software developers should know
#9Stay humble. You don't know as much as you think you do. That's the takeaway from these IMO.
Don't think anyone can commit all of these guides to memory but a very nice reference.
Re: A collection of things software developers should know
#10Every programmer should know what they don't know.
Deep