Statements like "every programmer" are bad as they usually mean "every low level programmer" or "every web programmer" or similar.
For example why is it important that every programmer knows about SEO?
A collection of things software developers should know
11–20 of 175 posts
Re: A collection of things software developers should know
#12Every 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.
Re: A collection of things software developers should know
#13Anyone with a good resource on "function composition" should add it to the list.
Re: A collection of things software developers should know
#14Very 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 still struggle to always get this right.
I really like the FHIR Human Name data type[0]. It requires none of the fields... so it can represent someone without a name. It also has all the necessary fields for representing someone's name and their name in various forms and pretty much as many edge cases as possible.
The only problem is turning it into a UI that makes sense.
Re: A collection of things software developers should know
#15> and may in fact be a symptom of deeper string-validation issues
It may also be a sign that there's a very early filtering stage that drops request at a very remote edge, which is a very good thing to do. See [0]; basically, you configure your server to completely drop requests that contain any character that has any possibility of being suspicious.
[0] http://twiki.org/p/pub/Support/ConfigureFailsOnNext/mod_secu...
Re: A collection of things software developers should know
#16Statements like "every programmer" are bad as they usually mean "every low level programmer" or "every web programmer" or similar. For example why is it important that every programmer knows about SEO?
It's a clickbait title. Should be changed... Sure, it's an interesting list, but no. Not every programmer needs or would want to know.
Re: A collection of things software developers should know
#17Every Programmer Should Know LISP
Re: A collection of things software developers should know
#18Statements like "every programmer" are bad as they usually mean "every low level programmer" or "every web programmer" or similar. For example why is it important that every programmer knows about SEO?
It's not meant to be taken literally.
Re: A collection of things software developers should know
#19Statements like "every programmer" are bad as they usually mean "every low level programmer" or "every web programmer" or similar. For example why is it important that every programmer knows about SEO?
SEO is largely about understanding how people think and phrase their questions. If you're ever going to write something and want other people to read it, they typically have to find it first.
Even if the person has already found your project or your docs, following SEO principles will make them easier to navigate.
Here I'm referring to the "stuff people type into search boxes" aspect of SEO, not the "dirty tricks" aspect.
Re: A collection of things software developers should know
#20Statements like "every programmer" are bad as they usually mean "every low level programmer" or "every web programmer" or similar. For example why is it important that every programmer knows about SEO?
I find that learning how to work with list is like having a crescent wrench in your tool box. Not every tool box have one but I sure think they should.
If you don't know list you won't know when that is the right solution. I have seen many people just use a SQLite DB for something as simple as a 20 item list.