The second workday

The workday is over.

In theory.

I close one computer, go home, and sometimes open another.

This time there are no colleagues waiting in a meeting. No job description deciding exactly what I should do next.

There are client requests, unfinished ideas, a personal project with a bug, and one simple question: where do I start?

Welcome to the second workday. 😅

Two kinds of work, one brain

I work in digital communications. That role comes with deadlines, responsibilities, priorities and plenty of unexpected requests.

Outside that job, I'm building KAMIT, my small company, and personal products such as KUMBA.

These activities overlap in software, content, design and marketing. But they are not the same.

At work, I have a clear responsibility to my employer.

With my own projects, I also have to decide which problems are worth pursuing. Nobody hands me a perfectly ordered task list.

That freedom is exciting.

It can also be exhausting when everything seems important.

The productivity trap

A good idea arrives. I tell myself: I'll just try something quickly.

I open the project. Fix one detail. Notice another improvement. Then start rebuilding a whole component.

Hours later, I have been busy. But what have I actually achieved?

Software makes it easy to confuse activity with progress. Changing a screen feels satisfying. Choosing not to add a feature is harder.

I explore that problem in One feature too many.

Deciding what matters

When projects compete for the same hours, I try to ask:

• What have I promised? Client and work deadlines are real commitments.
• What creates the most value now? Fixing a broken payment matters more than adjusting a card shadow.
• What can wait? A new idea isn't urgent simply because it is exciting.

I'd love to say I always follow this order.

I don't.

Sometimes I spend too much time on an interesting technical challenge and remember a less glamorous task is still waiting.

Not every hour belongs to work

There is a quieter trap too.

When you love building things, every free moment can start looking like unused production capacity.

An evening? More code.

A weekend? A new website.

An idea during a walk? Open the task manager.

But fatigue isn't a bug you fix by importing a new library.

Rest, relationships and life away from screens aren't obstacles to productivity. They matter in their own right.

I haven't found a perfect balance. I'm just trying to respect that limit more consistently.

Why keep going?

Because I love building.

Because personal projects let me experiment, make my own mistakes and discover what I want to work on over the long term.

And because growing something doesn't happen in a straight line.

Some days I improve a product. Other days I mostly learn what not to do.

What I want to avoid is sacrificing everything important just to feel busy everywhere.

Two workdays don't give you twice the energy.

They force you to be more deliberate with the energy you have.

I'm still learning how.