Skip to content
CONTACT

The Real Programmer, part two: habitat, rituals and habits

THE REAL PROGRAMMER, PART 2

The Real Programmer isn't a profession: he's a protected species. He lives in captivity in offices, feeds on cold coffee and reproduces by copy and paste. This is the second chapter of his user manual, to be kept near the router.

The Real Programmer's work

The Real Programmer doesn't do simple things. Ask him for a contact form and he'll deliver a framework for contact forms, with documentation coming soon.

  • The Real Programmer writes the software that decides when the car park barrier goes up. That's why the barrier has feelings.
  • The Real Programmer wrote, single-handedly, a management system that still holds up three companies today. Nobody knows how it works. Not even him. But if you switch it off, you hear a wail.
  • The Real Programmer doesn't work for glory. He works for the moment a test goes green first time, which has happened twice in his life, and one of those was a mistake.

In his spare time

The Real Programmer plays the way he works: in front of a screen. At the end of the month he's genuinely surprised to receive a salary. He'll never say so, because he wants a pay rise.

  • At parties you'll find him in the kitchen, by the fridge, explaining to another Real Programmer why his editor is better. The other guests drift past, listen for ten seconds and go back to the living room looking like people who have just watched a documentary about mushrooms.
  • On the beach he draws diagrams in the sand. When the wave comes, he says it was a rollback.
  • At restaurants he splits the bill with an algorithm. It takes him forty minutes. Meanwhile the waiter has closed up.
  • During a power cut he sits perfectly still, like a geranium in winter, waiting for the electricity to come back.

Natural habitat

The Real Programmer costs the company a lot, so it pays to know his ideal environment. Around his three monitors you will usually find:

  • seven mugs, none washed, some containing life forms that have already passed the interview;
  • a Post-it reading DO NOT TOUCH, stuck to a server nobody remembers buying;
  • a mechanical keyboard that sounds like hail on a tin roof;
  • a cable that connects nothing, but if you pull it out the network on the floor above goes down.

The Real Programmer performs best under pressure. If he has five weeks to finish a project, he spends four optimising the colour of his terminal. He does the real work in the last week, at night, with music in his headphones and the gaze of a monk in a trance. The boss, meanwhile, ages ten years. The Real Programmer doesn't: he's been old inside since 1998.

Any other business

  • The Real Programmer forgets birthdays, but remembers the root password of a server decommissioned in 2009.
  • The Real Programmer knows there's never enough RAM. He bought twice as much. Still not enough. He opened the browser.
  • The Real Programmer makes backups ever since, one Tuesday many years ago, he lost everything. He doesn't talk about it. He still has hard-disk-shaped nightmares.
  • The Real Programmer publishes his code for free. Four people in the world use it, and three of them write to complain.
  • The Real Programmer deploys on Friday afternoon. Not out of courage. Out of faith.

Corollaries

  • The Real Programmer doesn't comment his code. The code explains itself. Unfortunately it speaks a dialect only he knows.
  • The Real Programmer names his variables x, xx and x2_def. If you find a variable called total_monthly_invoices, it was written by an intern. Or by the Real Programmer on a day he was ill.
  • The Real Programmer uses an AI assistant to write code. Then he rewrites the lot, because the AI put comments in.
  • The Real Programmer doesn't read the manual. The manual reads him, and takes notes.
  • The Real Programmer counts in binary. When he says he has ten years' experience, it's two.

Errata from the veterans

Some of my older readers have sent in corrections, which I report with the respect due to old soldiers.

  • WHAT cloud? The server was in the cellar, on top of the washing machine, and in winter it heated the rumpus room.
  • WHAT USB stick? We saved to floppies, and to be safe we made a copy on another floppy, which broke out of solidarity.
  • WHAT artificial intelligence? The only intelligence in the office was the fax machine, and it jammed anyway.

Final footnote

When a program finally works, the Real Programmer doesn't celebrate. He eyes it with suspicion. A program that works first time is just waiting for the right moment. Usually Friday afternoon, straight after the deploy.


Loosely based on an old piece from the teneraerbetta.it archive