Skip to content

One Must Imagine the Bootcamper Happy

How the constant cycle of rm -rf at GoTo Engineering Bootcamp taught me to embrace the struggle

Published · Updated · 2 min read

Sisyphus pushing a pink boulder labelled rm -rf up a green hill towards a flag that says done

If I had to name the one person I’ve looked up to the most, it would be Sisyphus. That might sound strange at first: why admire someone whose whole existence is a punishment? He was condemned to push a giant boulder up a hill, only to watch it roll back down, again and again, forever. But even though he’s fictional, his story resonates with me. It feels connected to the way I see life.

What stands out most about Sisyphus is his persistence. He knows the boulder will never reach the top, and he pushes it anyway. That feels very close to the challenges we face in real life. Whether it’s studying for exams or finishing side projects, there’s always this cycle of effort and setback. You spend hours learning, only to realize you’ve barely scratched the surface. You fix one problem, only for another to appear. It feels like pushing a rock uphill, over and over again.

This really hit me during the GoTo Engineering Bootcamp. We were tasked with building simple projects. One was a geometry app that calculates the length of a line and checks whether two lines are the same line, given the coordinates of their end points. Another was Conway’s Game of Life, built once in Java and again in Go. Each one sounded easy, just like pushing a boulder up a hill. The catch was that every project had to follow the “non-negotiable etiquettes”, a set of rules on how the code should be written and kept.

The rules sounded harmless: commit every 10 to 20 minutes, end every file with exactly one newline, never check in a comment, and make test-driven development visible in the commit log. Break any one of them and the whole project went: rm -rf, git init, start again from an empty folder.

~/bootcamp
  1. $ git init geometry-app
  2. # attempt 1. how hard can a line be?

Attempt 1 · 0 commits wiped

Push commits up the hill. The rules are non-negotiable.

The first wipe stung. I lost an afternoon of work over a missing newline, and I remember staring at the empty folder, half annoyed and half embarrassed. By the third or fourth time, I stopped arguing with it. I committed smaller, ran the formatter before every commit, and wrote the test before the code without having to remind myself. Fittingly, the Game of Life is itself a little world where cells die and come back, generation after generation. The cycle of rm -rf and rewriting reminded me of Sisyphus: the rock will fall, but the climb still matters.

Albert Camus once wrote in The Myth of Sisyphus that “the struggle itself toward the heights is enough to fill a man’s heart. One must imagine Sisyphus happy.” The point isn’t the endless struggle, but the meaning you choose to give it. Instead of seeing repetition as despair, Sisyphus embraces it. He owns his fate, and in that acceptance, he finds freedom.

Looking back, the codebase got wiped every time, but I didn’t. The code was thrown away; the habits stayed: small commits, tests first, a clean diff. They’re still with me today. Sometimes success isn’t about reaching the top, but about how you approach the climb, and what the climb makes of you along the way.