Who wrote this shit?

It is a beautiful rite of passage for a bright-eyed junior developer to join a team, take some tasks full of enthusiasm, and have the life and joy sucked out of them one sprint at a time. Soon enough, they sit in planning meetings, miserably complaining, accusingly asking who wrote that shit. Their transformation to a full team member is complete. They have become one of us.

I was once that bright-eyed junior developer. Many encounters with PHP4 later, I could no longer look forward to creating new features. Instead, I looked back and complained about old ones. Trashing legacy software is fun. It creates camaraderie. Who wrote this? What were they thinking? Looking at the commit log showed names that meant nothing to me. Ghosts that moved on long ago, leaving nothing but their terrible code.

One day, I was pair programming with my friend Torben. Torben was a senior developer who had introduced me to the team months earlier. When I found some weird code, I followed the tradition. Who was dumb enough to write this shit? I opened the commit log, and for the first time, I recognized a name: “Torben.”

Since then, I remind myself that legacy software is written by people like me. Torben had constraints I knew nothing about. He worried about deadlines long past. Torben had learned a lot since then. Development workflows had evolved, infrastructure had gotten better.

And to all the junior developers who have complained about my trash code to my face: I forgive you, I understand.