Hi, I’m mike.

We once had a service outage that quietly lasted for several days. Not because we had no monitoring. Not because QA did not test. But because one part of the system was not covered by any alert or test - and we were not aware soon enough. The first reaction was obvious: “Let’s add one more test.” The second question was scary: “How many other blind spots like this exist?” ...

Imagine you have an existing product and you want to find real product gaps: what customers asked for but you don’t have, what they expected to work differently than it works today, where reality doesn’t match the promise. The problem isn’t that the answers don’t exist. The problem is that they’re scattered. They’re buried across internal communication (often the most honest and valuable source), Confluence meeting notes, customer interview write-ups, old Jira / Productboard / Trello cards created by different people at different times. Some are in Google Docs and spreadsheets. Some are in older tickets that aren’t linked to your long-term roadmap or insights anymore. ...

You open your AI chat, type: “Write me a blog post about X”… and 12 seconds later you’ve got 900 words that look polished, structured, and confident. And somehow… it is also flat. Generic. Slightly wrong. Like it was written by someone who has read about the topic, but never actually lived it. The fix is order of operations. AI cannot replace your thinking. But it can massively upgrade it—if you use it in the right order. ...

The moment my tiny soldier stopped responding to clicks, I felt a very specific kind of fear. Not “bug in production” fear. Not “API returning 500s” fear. Worse. Because I did not know what was broken - and I did not even have the vocabulary to describe it properly. Today I vibe-coded a simple browser strategy game inspired by Polytopia: a stylized, turn-based island prototype with a random map, villages, terrain types (desert, ocean, mountains), one controllable unit, smooth movement, and a minimal HUD - all built in Three.js as an MVP foundation for future expansion. ...

I thought AI would struggle with hard engineering problems. Instead, the biggest surprise was how quickly the whole build loop collapsed into something almost absurd: idea -> code -> deploy -> feedback -> repeat. In the past 6 days, I built 4 apps. Each app took roughly ~30 commits until I was happy. And each commit was basically one verification loop. One loop to rule them all My workflow became: ...

I built a simple status page for a test tenant with test resolvers so I can see real-time health and a lightweight history of degradation events. It’s not a customer-facing product. It’s an incident tool for me: one place to answer “what’s broken, where, since when?” before anyone else reports it. It’s private and access-controlled, but it lives on a real server. I treat it like production anyway. ...

This is the first post on the new site.