← back to log
Day 001 2026-07-24 learned

Why I'm publishing every day now

I have a folder called projects/. It has 40-something directories in it. Maybe six of those ever got shown to another human being.

That’s the actual problem. Not the code, not the skills — the fact that all the evidence of those skills is on one SSD in İzmir.

What changes

Every day I work on something, I write down what happened. Same day, no editing pass a week later when I already know how the story ends.

Three rules I’m giving myself:

  • Write it the day it happens. A summary written later is a different, worse document.
  • Include the failures. The debugging is the part that proves I can actually do this.
  • No word count target. Some days are two sentences. That’s a valid entry.

What this isn’t

It isn’t a tutorial site. I’m not going to stop mid-entry and explain what a Promise is. If a day was spent fighting Electron’s build config, the entry is about that fight, written for someone who already knows the terrain.

The bet is simple: over a year, 200 honest entries say more about how I work than any portfolio page could.


Contact

Recognise this problem?

Open to freelance and contract work — desktop tools, automation, video pipelines.