This is like asserting that my former hometown of Washington, D.C., has several football teams: the Redskins, the Georgetown University team, and the Gonzaga High School team.
You should have distinct memories of you or someone under your employ having at least two separate incidents in the last four weeks in which they dropped everything they were doing and immediately took action to resolve these problems.
Last night during the hurricane, we could not telnet to one of our partner’s data centers from our primary data center. We could get there from our workstations and from our backup sites.
A traceroute revealed a router somewhere in Washington DC that was hanging things up between the two data centers.
So my question is, how could this happen? I would have expected all the TCP/IP packets to be rerouted automatically around the malfunctioning router? Isn’t that the way the Internet was designed to work?
Everyone on our production support team installed the following cron on their local workstation so we would know if anyone loses power and can’t get in touch with the rest of the team:
*/1 * * * * ssh server "echo '`date` `whoami` reporting for duty' >> sandy.log"
Love the new Slashdot logo.
I also love the neckbeard comments about how that wouldn’t actually be an accurate little endian representation “even on 24 bit machines”
Look, I love programming. I also believe programming is important … in the right context, for some people. But so are a lot of skills. I would no more urge everyone to learn programming than I would urge everyone to learn plumbing.
Jeff Atwood, “Please Don’t Learn To Code”
This is one of the dumbest things I have ever read.
The article is conflating “coding” with “professional software development”. Learning to code teaches you, among lots of other things:
- Divide and conquer
- Boolean logic
- Analytical thinking
- Logic flow
When a programmer gets requirements from a product manager or business analyst, they are ALWAYS incomplete. The edge cases are NEVER identified and none of the “what if” scenarios are played out. 9 times out of 10 it is up to the programmer to understand the nuances, to take things to their logical conclusions, to consider what happens in the case of N=0 or as N approaches infinity.
These are all skills I use EVERY SINGLE DAY, not just when I code, but in solving problems in life. Broken toilet? How do I figure out where the problem is? You bet I’m going to divide and conquer that shit (pun intended)!
This kind of thinking helps me in everything that I do in life and it wasn’t until I learned to code (in college, mind you) that I started thinking this way.
Do I want my son to become a computer programmer? I don’t care. Up to him. Do I want him to understand how to think critically and logically and in a structured & methodical way when approaching problems? Absolutely. And computer programming teaches these skills better than anything else I’ve ever done.