delay does not exist

AUTHOR: Tiziano Gasparet DATE: January 29, 2026

Origin

I spent six months staring at a blank screen.

Not for lack of things to say. But because I had convinced myself that the only right time to start was January. I had turned the calendar into a hardware constraint that held me prisoner.

Every day that passed was a “delay” I was accumulating. Every week without publishing was cognitive technical debt. I constantly felt behind, as if I were chasing a train that had already left.

Then, on March 26th, I read the system logs. I saw that the Monolith had been operational for weeks. Relayd, httpd, PM2: everything was working. The infrastructure was ready.

I was not.

The Connection

Why does the Monolith archive this? Because delay is not a measure of time. It is a measure of anxiety.

In code, a process is not “late”. It is running or it is not. There is no judgement. No guilt. There is only state.

I applied this logic to my life:

  • I am not “recovering lost time”.
  • I am executing the boot now.
  • The start timestamp is irrelevant. What matters is that the service is online.

The Monolith is not an archive of when I started. It is an archive of what I built.

The Challenge

The inner doubt was: “Should I publish everything at once to recover the six months?”

The answer: no.

Quantity does not cure guilt. Coherence cures anxiety.

I decided to publish one article at a time. When it is ready. Not when it “should” be.

The challenge was accepting that March 28th, 2026 is my day zero. Not January 1st. Not the day I bought the domain. Today.

Peace of Mind

Now that I have written this, I have clarified the contract with time:

  • The past is not recoverable.
  • The future is not guaranteed.
  • The present is the only timestamp I can control.

Peace of Mind comes from knowing I am not late. I am exactly where I need to be to publish this article.

The Monolith is online. The system is operational.

And delay does not exist.

Technical Note:

  • Boot timestamp: 2026-03-26 (relayd configuration completed)
  • Publication timestamp: 2026-03-28 (first manifesto article)
  • Philosophy: development time is not debt, it is investment
  • Trigger: if you feel “I am late”, deploy what is ready
  • Principle: better one article published today than ten planned for January
TG

Who I Am

Sovereign systems architect. I write about technology, pastry, chess, and discipline.

Did you like this article? Let's talk.

Email me: tiziano@tizianogasparet.com Contact me on Signal: @tizianogasparet.06 (Signal) BIOGRAPHY

The Monolith is an invitation to conversation, not a monologue.