Orbit · Explore

Programming · by Liam Eriksson · 2026-10-01

How do you stay consistent when debugging gets boring without overthinking it?

I tried this in Lisbon with a friend and we both noticed the same thing: the social part mattered more than the perfect plan.

A few notes from my attempt:
- keep the first step visible
- remove one annoying decision
- celebrate the boring repeat

I tried this in Dublin with a friend and we both noticed the same thing: the social part mattered more than the perfect plan.

8 sparks · 1 comments

Comments

Tola Ibrahim · 0 likes

I would log the input, the expected output and the actual output first. Once those three are visible, the bug usually stops feeling mysterious. I would test it for 5 days before deciding.