Work life · 20 relatable moments

20 Relatable Engineer Moments from Everyday Development

The error has disappeared. That should be good news, except you cannot explain why. Building software can put relief and suspicion surprisingly close together.

This collection follows the small moments around coding, questions and checking your work. It is a light read about the feeling of making things, not a technical guide or a report on how all engineers work.

The moments

  1. Every update feels risky

    If it ain’t broke, don’t fix it… or do you?

    #01
  2. Having more tabs open than memory can handle

    You have a system—no one else gets it.

    #02
  3. ‘Quick fix’ becomes a day-long project

    Nothing is ever as simple as it sounds.

    #03
  4. Your computer is your best (and worst) friend

    When it works, you’re unstoppable. When it doesn’t… chaos.

    #04
  5. Staring at the screen hoping for answers

    Sometimes, the bug fixes itself if you just stare long enough.

    #05
  6. The joy of fixing a tough bug

    You feel like a genius for at least five minutes.

    #06
  7. Naming variables is harder than coding

    You’ve used ‘temp’, ‘foo’, and ‘final’ more times than you can count.

    #07
  8. The ‘just five more minutes’ trap

    Five minutes turns into five hours before you know it.

    #08
  9. Explaining bugs to non-engineers

    ‘It just does that sometimes’ isn’t a satisfying answer.

    #09
  10. Version control drama

    Merge conflicts always happen right before a deadline.

    #10
  11. Deploying code on Fridays—never again

    You learn the hard way: weekend bugs are the worst bugs.

    #11
  12. Sticky notes cover your monitor

    You have a color-coded system only you understand.

    #12
  13. Remembering obscure keyboard shortcuts

    You use CTRL+Z and CTRL+S more than any other keys.

    #13
  14. ‘It works on my machine’—famous last words

    Deployment is where dreams go to die.

    #14
  15. You talk to your code (and expect it to listen)

    Sometimes it feels like arguing with a stubborn pet.

    #15
  16. Googling solutions is an essential skill

    Stack Overflow is your best friend.

    #16
  17. Debugging one line of code for hours

    The typo is always in the last place you look.

    #17
  18. Explaining your job to family is impossible

    ‘So… you fix computers?’ becomes your entire career summary.

    #18
  19. Endless coffee to fuel problem-solving

    You measure time by coffee cups, not hours.

    #19
  20. Code works perfectly… until someone is watching

    It runs smoothly at 2am, but crashes during the demo.

    #20

There is a story outside the code

You do not need to know a programming language to recognize a badly timed interruption or a problem that makes sense the moment you describe it aloud. Start with the situation when sharing an engineering joke with someone outside the field.

More familiar moments