Bad Programmer Pickup Lines, Part Deux



The original list is found here.

  1. Call me a retro AI programmer, but I like my women as I like my logic: fuzzy. Can I get a peek of your implementation?
  2. Dear God, I haven’t seen a stack like that in ages. It’s enough to make me overflow.
  3. If things get a little hot and heavy later, I’ll make sure to call ‘join()’ so that we finish together.
  4. You look a little compressed in those pants. Let me make you more comfortable by running ‘gunzip’ on them.
  5. My, my, my…your mother allocated quite a buffer on you. Mind if I address it with my pointer?
  6. When using my web services or spending some time in my bedroom, it’s recommended in both cases that you get plenty of REST.
  7. Now that we’ve gotten to know each other, it’s about time for production…and I’ve got my branch all ready for deployment.
  8. I just ran a ‘netstat -a’ on your luscious body, and fortunately for us, it reported back that all ports are open.
  9. Girl, let’s ditch this party and head back to your place for a code review on memory usage. I’m sure that we’ll find a few leaks which you’ll want me to address.
  10. How about we start a process together and get right to forking?

Peter Bolton is the author of Blowing the Bridge: A Software Story and has also been known to be a grumpy bastard on occasion.

About these ads

Bad Programmer Pickup Lines



  1. How about we improve our performance by wrapping your O() around my logn?
  2. I couldn’t help but notice that we’re ethnically diverse…and I’m all about fast and heavy race conditions.
  3. Girl, you’re so fine…as much as I’d try to hold my lock with you, I couldn’t stop releasing early.
  4. I’ve lost something, and I think that I might find it on you. Mind if I opt for a depth-first search?
  5. Care to swing by my office for a quick examination? I’m designing a new architecture, and I just found the perfect domain model.
  6. With an angelic rackspace like that, you must have just fallen out of the cloud.
  7. I suggest that we go home and remove these masks, so that we can finally see all the bits underneath.
  8. What’s your favorite configuration? Mine is where you’re the master, and I’m your slave.
  9. I can tell you one thing, sweetheart: there isn’t anything generic about your container.
  10. Are you a developer as well as beautiful? Because I’d love to push my code into your repo.

Peter Bolton is the author of Blowing the Bridge: A Software Story and has also been known to be a grumpy bastard on occasion.

Seven Levels of Hell: The Tech Edition



  1. First Circle (Limbo): For developers who can’t pick a language or platform as their given specialty.

    Punishment: All souls chained to this level will walk door to door with their résumé, only to have each one slammed in their faces with the phrase “You have no strengths!”

  2. Second Circle (Lust): Taking into account who we have to face each day at work and their respective level of resembling a troglodyte, we can go ahead and eliminate this possibility.

    Punishment: Not applicable. This level of hell is empty.

  3. Third Circle (Gluttony): For programmers who create memory leaks and perpetual loops, eating up all the memory and CPU cycles on the system.

    Punishment: Every single day, these offenders are presented a choice to either write an enterprise server application (with an embedded demoscene) that can run efficiently with only 2K of RAM or to eat an entire Alienware computer case.

  4. Fourth Circle (Greed): For IT managers who wouldn’t share resources or knowledge with other managers.

    Punishment: Chained to a wall and gagged, these souls must watch silently as their peers take credit for all of the damned’s projects and heap praises upon each other.

  5. Fifth Circle (Anger): For admins who blow their top and acerbically berate all users, both advanced and novice in technical knowledge.

    Punishment: Surrounded by blaring alarms about hard drives losing disk space, they will sit at a terminal for eternity and their fingers will only be able to repeatedly type ‘fsck’ (and other variations with more vowels).

  6. Sixth Circle (Heresy): For the sales managers at software companies who know the limitations of the product being sold but then promise everything else to the customer.

    Punishment: Unfortunately, this level of hell is full of innocent software developers. As with the world of the living, the salesmen have talked their way out of punishment and somehow placed the full load of misery onto the developers.

  7. Seventh Circle (Violence): For the developers whose nonsensical code causes headaches and dizziness to those who review it.

    Punishment: While being flogged with the “computer-mice-o-nine” tails, they must write the code for their next project through only the smashing of their heads against a vintage IBM Model M keyboard. ‘Click-clank-click’ will be the only soundtrack for eternity.

  8. Eight Circle (Fraud): For all IT staff who knowingly have taken one shortcut in their lives when they should have done things the right way.

    Punishment: Due to overcapacity (in that all fellow IT staff belong here), a huge volume of sinners will need to take turns being in the pit in order to accommodate the space. The punishment has yet to be determined since the domain model hasn’t taken all factors (like performance requirements) into account yet.

  9. Ninth Circle (Treachery): For any CIO/CTO who had a productive, strategic vision for the company but then abandoned that vision at the first sign of trouble (or a golden parachute).

    Punishment: Much like those stuck in Limbo, these souls must forever be denied employment by various prospective employers…but they must suffer while chained to an ex-spouse who perpetually complains about a lack of alimony or child payments.

Footnote: The title would be nine levels of hell, but since the second level is empty and the sixth level is misused, there’s actually only seven. That seems to fit, though, since nothing in tech has an implementation which matches the specs.

Peter Bolton is the author of Blowing the Bridge: A Software Story and has also been known to be a grumpy bastard on occasion.

Ways that Code.org Can Excite People about Programming



Unless you’ve been busy living under a rock or preparing inside your bunker for Armageddon, you’ve heard of Code.org and their goal to excite the public about the potential prospects for everyone in regards to programming. Codecademy even claims that it can empower the common layman with the skills to become an employable programmer…in only 3 months! However, despite all of their efforts to galvanize people, the impact has been nominal at best. What’s really needed is an effective campaign to convince people to join the world of developers. Some useful ideas that come to mind are:

  • Spread the rumor that advanced coders are able to summon the power of hadouken when they reach a high enough level.
  • Stress how developers gain an infinite amount of patience by dealing with the both complex systems and less-than-complex managers.
  • Pitch how one can become enlightened and attain a higher level of philosophical understanding about Hobbes’ sentiment towards mankind, as you attempt to make one Web page consistent across dozens of browsers and platforms.
  • Showcase the absolutely festive environment that one expects with the sausage party that is a programmer’s career.
  • Demonstrate the power of software development by showing how one junior developer can commit several lines of code and cause the entire downfall of a project and/or system.
  • Emphasize how programmers acquire skills that are essential assets in a modern technological society (but will become useless in the event of a great solar flare and its crushing blow to our global infrastructure).

Peter Bolton is the author of Blowing the Bridge: A Software Story and has also been known to be a grumpy bastard on occasion.

Lazy Costumes for Programmers



  1. Pour Mountain Dew onto your shirt (as a sugary adhesive) and then cover yourself in crushed Doritos, proclaiming to be the crumbs in a coworker’s keyboard.
  2. Create a noose from some spare cable and put it around your neck. When somebody asks what you are, state that you are the [fill in blank] server that’s always hanging for no good reason.
  3. Find that one guy in your office with anime figures and steal a few of them from his elevated shelf. Then, paint their faces with printer ink and walk around with them, boldly announcing to be the proud parent process of several zombie children. (Avoid the actual owner of the figures for the entire duration of the party.)
  4. Print out three copies of a cute puppy’s face found on the Internet, align them in a row, and tape them to your head. Afterwards, create a collar from a network cable and attach a large name tag which says Kerberos the Happy Scrappy Hero Authentication.
  5. Empty one of your rectangular wastebaskets, draw the face of a demon on its side, and don it on your head to parade around as a corrupted USB stick.
  6. If you and a fellow programmer are feeling a little adventurous, create a ‘cat-o-nine tails’ from the spare mice in the hardware closet and create a spiked paper collar using paper and staples. Now, with one person wielding the tails and with one person wearing the collar, be the sensation of your event by attending as a MongoDB master and slave configuration.

Peter Bolton is the author of Blowing the Bridge: A Software Story and has also been known to be a grumpy bastard on occasion.

The Function Name Hall of Shame



Over the years, I’ve participated in numerous code reviews, and I’ve seen a few function names that were worthy of true shame. However, the Hall of Shame demands only the best (or the worst, depend on your point of view), and so, I have whittled it down to a few of the most worthy. Consequently, I nominate the following for the Hall of Shame:

  1. NOTE: Could this function be any more ambiguous?
    private string GetTableData()
  2. NOTE: Our new programmer just might be dyslexic or suffer from something worse
    public int ManageJoinUsingDelete(…)
  3. NOTE: Do we need to know every step involved in the name?
    private int GetUpperRangeOffsetBySubtractingProductOfTwoSums()
  4. NOTE: I hope that this ‘body’ refers to text and not a dead hooker
    public void EndStreamingNoAttachIfBody(…)
  5. NOTE: This function needs more ‘temp’
    public int PopulateTempTemporaryTransfer(…)
  6. NOTE: This seems so wrong on so many levels
    public bool IsFalse()
  7. NOTE: He’s not exactly creative, is he?
    public void TransformData(…)
    public void TransfromDataPlus(…)
    public void TransformDataPlusExtra(…)
  8. NOTE: They do say that string mathematics is a dying art
    private string CalculateNextLessThanOrEqualNumber(string)
  9. NOTE: ???
    private string GenerateTempGetUpdateOrGetInsertWhereCriteria(int)
  10. NOTE: I like it…straightforward, single in use, and stupidly simplistic
    private string SurroundWithParantheses(string)

Peter Bolton is the author of Blowing the Bridge: A Software Story and has also been known to be a grumpy bastard on occasion.