1. 58
  1.  

  2. 8

    This was probably the best programming humor article I’ve ever read. Thanks for sharing.

    1. 5

      Agreed. My solution was to build my own company and keep the idiots out. It’s been working well for the past 10 years, at least.

      1. 3

        I’d love to hear about the company and the story behind it – what’s your hiring technique, what kind of projects are you working on, which technologies and processes you use?

        I’m trying to do something similar myself and I have to admit we do have our moments resembling the ones in the article (though I like to believe they’re not as drastic :)).

        1. 7

          I could write a post, but it would probably be one of the most boring “successful” (so far) business stories around. The basics:

          • “Lifestyle business,” software development consulting, charge competitively, pay well. Reasonable hours.
          • We only hire people we have worked with and can personally vouch for as great developers and great personalities. This naturally keeps the team small. Also, if you vouch for someone, you better mean it.
          • We don’t take on more work than we have the team for. No winning big bids and then trying to find people to fill a team. That’s a recipe for disaster (or just sub-par work).
          • Added bonus of consulting is that people generally listen to what you have to say, though not always (their loss).

          Many of the above may not transfer to a product company, but it’s certainly possible with a carefully-grown, bootstrapped one.

        2. 2

          As a software engineering student, while reading I thought to myself: “This won’t happen to me, I’m going to make my own company!”. But thinking it twice, is it really possible to fight the system? Don’t you have deadlines to be met and requirements to be implemented? How do you manage?

          1. 2

            Besides programming, a professional developer will also be skilled in managing requirements and deadlines. Absurd requirements and inhuman deadlines aren’t good for business on either end.

        3. 4

          I did menial labor for my first 8 years of being an adult, and now I’ve been an engineer for the last 10. I will have to say that menial labor felt much more soul draining than this. Don’t be babies guys. At least you get paid well and, for the most part, are respected.

          1. 3

            My first thought after reading that is that somebody clearly needs a hug.

            Our code really isn’t that bad. It’s just that it has to interact with everybody else’s code, which is clearly a witches' brew of nonsense. Like the thingy that happens to throw exceptions that Visual Studio won’t catch, or the database that doesn’t do CTEs for some reason (cough, mysql, cough), or the ORM that you can tell to delete orphaned rows, but will only actually do it sometimes, or…

            1. 2

              To me all these codes we write look like genies and daemons, who are just waiting for you to give a wrong command. A little slip of the tongue and they will pounce on it, and do things you never intended them to do.

              Bartimaeus Triology anyone?

              1. 2

                Or Jack Vance’s sandestin magic.

                1. 2

                  A whole novel based on this concept in reverse: http://www.baenebooks.com/p-1632-the-wizardry-compiled.aspx

                  Significantly better than the “back of book” would lead you to believe.

            2. 1

              Dang, I was really hoping for “Why haven’t you made the next Facebook yet?” or “You need to march into Google and demand they give you a job” but “What’s wrong with my laptop?” is just as good because it’s even more painful