21–30 of 175 posts
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.
I 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.
Right now it's "Every Programmer Combined Should Know"
> 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...
> 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...
I think you meant to post in a different thread?
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 "important things" one is working on are just not that important, so get a life.
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…
Are you implying there is more to life than programming?
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?
It's not meant to be taken literally.
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…
> 1. Life is too short, so get a life. Are you implying there is more to life than programming?