mike.mainguy

I've seen a few Chuck Norris programming posts, I thought I'd do my own about the Chuck Norris programming language. Chuck Norris Programming More fun Check Norris Facts Here are the primary features: * Chuck Norris doesn't need a revision control tool, all versions of the code are always available. * Code in Chuck Norris is always optimal. * Chuck Norris never dies. * Chuck Norris can parse invalid XML * Chuck Norris can divide by 0. * Chuck Norris can compile syntax errors. * Braces are for weaklings, Chuck Norris doesn't need them. * Chuck Norris doesn't need Exceptions, he makes the rules and they get followed. * If Chuck Norris Norris DID have exceptions, they could be thrown through a brick wall. * Check Norris doesn't need Iterators, he's going to do everything once and at the same time. * Chuck Norris doesn't kill processes, they get destroyed. Any other features?

I was explaining to a developer the other day how we didn't need a lot of the java code we where writing because there where tools that did these jobs better (or at least as well) that already worked. His response was (half jokingly) something along the lines of "well, if I don't write this stuff, I what am I going to do?". This was a little bit of a shock to me as I assumed everyone on the team understood there where about 40 projects we couldn't do because we "didn't have the bandwidth" and management was not going to hire 40x more developers to do the work. Because I knew this, I've been spending a lot of time reducing the amount of manual labor we expend building software as well as trying to get us into the mode of reusing as much as possible. What I didn't do is explain to the team that we aren't doing this to reduce headcount, we're doing this to be able to deliver more cool stuff faster and more reliably. The big problem we...