Back to Blog

My own product was the only one with no deadline

By Maria Catalina Kovacs · 23 September 2026 · 3 min read

I had been the client the whole time, and I had never once hired myself properly.

I have been an engineer for twenty eight years and I have never once needed a CV. One client recommended me to the next. That is the whole of my career and I am not complaining about it. But I have been thinking about what it did to my own work, and I think it is a more common problem than anybody says out loud.

Somebody was always waiting

Everything I have built for twenty eight years had somebody waiting for it. A date, an invoice, a person who would ring on Monday and ask. That pressure is not pleasant, but it is what turns a thing into a finished thing. You do the boring parts because somebody is going to look at them.

Then I started building something of my own, and for the first time there was nobody on the other end.

No date. No invoice. Nobody ringing on Monday. Every week I chose between work somebody was waiting for and work nobody was, and I made the responsible choice every single time. That is the whole mechanism. Twenty eight years of professional standards, applied everywhere except the one place that was mine.

I had been the client the whole time, and I had never once hired myself properly.

It is structural, not charming

People call this the cobbler's children and say it with a shrug, as though it were a charming personality flaw. It is not. It is structural. A deadline is other people's attention, and your own product does not have any yet, which is exactly when it most needs the discipline that attention brings.

What I am not saying

I want to be precise here, because there is an easy version of this that is wrong.

I am not saying I was lazy or that the work was sloppy. I am saying that for a year nobody checked it, including me, and that unchecked work does not stay level. It drifts. Not dramatically. One reasonable decision at a time, each of them correct on the day, and none of them ever revisited because revisiting was never anybody's job.

Distance, not insight

Then I had to stop for a while. Personal reasons, and they lasted longer than I expected.

Coming back after that is the only reason I saw any of it. A year of small drift is invisible when you are inside it and obvious the moment you have been away. That is not insight on my part. It is just distance.

The apparatus that client work comes with

So I did the only thing I know how to do about it, which is to give my own work the apparatus that client work comes with automatically.

I write down what I find before I fix it, because a list made while you are fixing is a list that flatters you. I export before I delete. I put a gate in front of the build that reads the output and refuses to publish if something is in there that should not be. It has caught two real faults so far and both were mine. None of that is clever. It is just the standard I would have been held to by anybody paying me, installed deliberately because there is nobody paying me.

The discipline had to become a system, because the pressure that used to supply it is not there.

The folder you probably have too

If you sell your skills for a living, I think you probably have a version of this sitting in a folder somewhere. The thing you would build if there were time. And the reason there is never time is not really time. It is that nobody is waiting, and you are extremely good at doing the work somebody is waiting for.

I do not have a clever ending for that. I just stopped treating my own project as the one that could wait, and started treating it like a client who happens to be me.

Happy coding.

MK!

Maria Catalina Kovacs