Skip to content
Lubo Bali

ActiveShipped yesterday

What I'm building, right now.

Real numbers from my own servers, counted by code every morning. No screenshots, no claims.

Updated Oct 25, 5:00 AM CT

Every day since March

2,752 updates shipped in 2026.

One square per day, across all my projects. Work from my laptop counts once it is pushed.

days building
174
days in a row, my longest
30
projects
20

Building now

Two builds at once, this week.

  • Public project

    lubobali.com

    Describe a business problem and get a first AI plan in about 30 seconds, on this site

    73updates this week

    Last 8 weeks
  • Client project

    Client · AI search

    Private AI search built for a client

    85updates this week

    Last 8 weeks

    The client stays private. Ask me on a call.

Built to be trusted

Nothing ships until the tests pass.

I build test-first (TDD). Here is what that adds up to across my projects.

19,132automated tests0 failing

  • LuBot.ai16,119
  • Lubo AI Publisher958
  • Client · AI search896
  • MarketMind AI310
  • lubobali.com280
  • GraphGuard-AI201
  • Sentinel-AI126
  • Other projects242
full test runs on my own CI server since March
2,132
times a red run stopped a change from shipping
221
LuBot's test run, cut from 24.5 to 4.4 minutes, so I can ship more often
82% faster

Counted from each project's latest green run, every morning.

Real example · Oct 24A visitor saw “Park” where their job post said “Spark”. I wrote the test that catches it first, then the fix. Live the same day, and it can't come back.

  1. Test firstWrite the check for one small feature. It fails, because the feature isn't built yet.
  2. BuildWrite just enough code to make that check pass. Nothing extra.
  3. CheckEvery push runs all the checks on my own CI server. One red check stops the release.
  4. RepeatNext small step. The checks keep adding up, so old features stay protected.

Why it matters to you: I can move fast without breaking what already works. Bugs get caught by a test, not by your customers.

Automated checks, last 30 days

199of 216 passed

My last 60 test runs. Each red one stopped a change before it shipped.

Live

LuBot.ai in production

99.92%up, last 15 days

Checked every 10 seconds from the server. A missed check counts as down.

Shipped lately

The milestones, not the noise.

  1. LuBot.aiNew release with 1 update
  2. Client · AI searchStarted a new build
  3. lubobali.com23 new features in one week
  4. LuBot.aiNew release with 2 updates
  5. lubobali.comNew public project on GitHub
  6. LuBot.ai10 new features in one week

Written by code from real events. No AI writes this page.

In my hands this quarter

What I actually build with.

Counted from the code I changed in the last 90 days, not a list of logos.

  • Next.js 16new
  • React 19
  • Tailwind 4
  • FastAPI
  • PostgreSQL
  • MCP servers
  • RAG
  • Playwrightnew
  • Claude Code
  • NVIDIA Nemotron

Every number here is read each morning from git, my CI server and LuBot's monitor. Client work counts in the totals and stays private.

Tell me your problem. I'll find a way to build the solution.

Available now

Book a free 30-min call (opens Calendly in a new tab)

No obligation. Pick a time that suits you.

Prefer email?data@lubobali.com