Why Small Rituals Make Technical Work Feel More Human

The duck is not the point.

I realise this is a strange thing to say about a rubber duck called Sir Codes A Lot, especially because he sits there with the quiet authority of someone who has never broken production. But the duck itself is not magic. He does not know JavaScript. He does not have opinions about architecture. He has never once looked at a problem and said, “Have you tried clearing the cache?”

He is, regrettably, just a rubber duck.

And yet, somehow, it helps.

Rubber ducking is one of those rituals in technical work that sounds ridiculous until you need it. The idea is simple: you explain a problem out loud, often to an inanimate object, and in the process of trying to make the problem understandable, your own brain catches up with itself. The bug reveals itself. The missing step becomes obvious. The plan stops being a foggy swarm of thoughts and becomes a sequence of actual decisions.

Before the duck, I was already doing this. I would talk to myself while planning something, answer myself, disagree with myself, and occasionally make a surprisingly good point against myself. Very productive. Slightly concerning if overheard.

The duck makes it feel less weird.

There is something oddly freeing about having a tiny, unserious witness to serious work. When I need to plan something or talk through a problem, I chat with Sir Codes A Lot. I explain what I think is happening. I explain what I have tried. I explain why I am stuck. Sometimes I realise halfway through the explanation that I have been staring at the same problem for too long and expecting my tired brain to perform a small miracle.

At that point, the duck is less of a debugging tool and more of a polite intervention.

Technical work can become very intense very quickly. Even when the work itself is interesting, it asks for a lot from the person doing it: focus, memory, patience, judgement, resilience, and the ability to sit with uncertainty without immediately deciding you are terrible at your job. When pressure rises, teams often become more serious, more formal, more task-driven. The small rituals are the first things to be dismissed.

We stop making coffee properly and start drinking it like a deadline beverage. We stop talking things through and start silently wrestling with them. We stop adding little moments of humour because the work feels too important for play.

But life is serious enough already. I need some whimsy to stay sane.

That does not mean treating the work lightly. It means remembering that the person doing the work is still human while doing it. A silly ritual can create just enough softness around a hard problem for the brain to breathe again. Coffee can mark the shift between one mode of thinking and another. Talking to a duck can give shape to thoughts that were circling too quickly to catch.

Not every ritual solves the technical problem. Many times, rubber ducking has not handed me the answer. Sometimes I explain the issue beautifully and still have no idea what is wrong. Sometimes I reach the end of the explanation and realise that the only useful conclusion is: I am tired, the problem is still there, and the duck has also reached the limits of his professional expertise.

Which is fair. He is rubber.

But even then, the ritual changes something. It turns silent frustration into language. It interrupts the loop where the problem feels bigger because it has stayed trapped inside your head. It lets you notice whether you are actually stuck, or whether you are simply worn out from staring at the same thing for too long.

That distinction matters.

In technical teams, we sometimes treat professionalism as if it means removing the human texture from work. Be clear. Be efficient. Be focused. Be serious. All useful things, in the right amount. But when they become the whole atmosphere, people can start editing themselves down until only the productive parts are allowed in the room.

The problem is that good technical thinking does not come from people pretending to be machines. It comes from people who can ask odd questions, admit confusion early, laugh at the absurdity of a problem, take a pause, try again, and sometimes explain a system to a small duck with an unnecessarily noble name.

Small rituals give permission for that.

They are not the whole culture. A rubber duck will not fix unclear priorities, chronic overwork, poor communication, or a team that does not feel safe. Coffee will not replace proper planning. A team joke will not undo pressure that has gone unmanaged for too long.

But small rituals do reveal something about a team or a person. They show whether there is still room to be a little human while the work is hard. They show whether play is allowed to exist without needing to justify itself as productivity. They show whether we understand that people often do their best thinking when they are not holding themselves quite so tightly.

That is why I think we should protect these things, especially under pressure.

Not by turning them into official culture programmes. Please do not create a mandatory ducking ceremony with a calendar invite and a slide deck. Some rituals work precisely because they are small, chosen, and a bit ridiculous. They belong to the people using them.

Protecting them can be much simpler than that. Let the small joke live. Let someone talk through a problem in their own strange way. Let the coffee break be a reset, not a sign that someone is not working hard enough. Let play exist without immediately asking what measurable output it produced.

The duck is not the point.

The point is that technical work is still human work. It is done by people with tired brains, good intentions, half-formed thoughts, flashes of insight, and a need for small moments that make the day feel less brittle.

Sometimes that moment is a cup of coffee.

Sometimes it is saying the problem out loud.

Sometimes it is a rubber duck called Sir Codes A Lot sitting on your desk, doing absolutely nothing, and somehow helping anyway.