Every project starts with a problem you’re tired of solving manually.

For me, it’s the mental load of tracking things that should track themselves. The weekly reviews that become monthly (then quarterly, then forgotten). The decisions that get delayed because the information isn’t ready.

So I’m building systems to handle it. Not the flashy kind that make good demos. The boring kind that just work.

This blog is part of that system. Instead of waiting until something is “ready” to share, I’m documenting as I go. Raw progress. Real timelines.

The Plan

Over the next few months, I’m building:

  1. An automated content pipeline - This blog publishes itself (mostly)
  2. A personal decision engine - AI-powered analysis that tells me what to do, not what to think about
  3. A notification system - Proactive nudges instead of reactive scrambling

Each piece connects. The blog documents the progress. The engine analyzes the data. The notifications keep me on track.

Why Public?

Building in public keeps me honest. If I say I’m going to ship something, it’s on record. If I fail, that’s on record too.

Plus, maybe someone finds this useful. Or at least entertaining.

What’s Next

First: get this blog live. A simple pipeline: write, validate, publish. No manual deployment.

Then: start on the harder stuff.

Let’s see how it goes.