Matt Hinkley (@matthinkley9) header
Matt Hinkley (@matthinkley9) profile picture

It’s time to build! I enjoy using AI to simplify life and use my imagination in ways I haven't before. AI Solutions and Sys. Implementation by day!

Joined July 2012
Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)Photo by Matt Hinkley (@matthinkley9)
Everyone says keep your AI bots to 15–20 max or you'll drown managing them. I run 36. I talk to one. One front door, a crew with clear charters, and the count stops being the problem. And the token cost? Right now it's cheap to dream. Full write-up 👇
1
27
AI agents write code fast. They leave mess fast too. A good fix: a nightly cleanup pass. At 3am a routine checks what merged since last night. Nothing new? It closes out quietly. New merges? It hands just that range to the engineering bot to tidy. Small daily sweeps beat the big cleanup sprint nobody ever schedules.
17
Most AI "QA" is a bot that says the code looks fine. Mine does three things: 1. Keeps a checklist of bugs we've actually hit, each with a repro 2. Sweeps production after every merge at real phone sizes 3. Stays silent unless something regressed The checklist grows every time something breaks. That's the whole trick.
1
21
The only question that matters in an AI consulting intake: "Are you comfortable with AI working directly on your own laptop and files?" Yes → Claude is probably your best bet. No → Grok. Either way, you've got a client. The rest is just requirements.
27
I signed on a bot whose only job is to take notes on every project I'm running at once.
1
37
The endgame isn't another dashboard. It's one in-depth piece about how you can pursue anything you want all at the same time, written from real scenes as the work happens.
1
7
Deep draft only when I ask. Until then it just keeps the beat. The board stays glanceable; the notes get denser.
2
I've been designing memory for my bot crew like a brain with a cheap archive, not one giant always-on pile.
1
1
115
Perpendicular to that: a core memory that cuts across every tier and never ages out. Small, ID-keyed, day-to-day facts: people, accounts, projects, repos, locked decisions, standing rules. Always loaded. Instant lookup by ID.
1
7
Archived notes point back to those IDs. Reopen something and it promotes back to Hot. One fast spine of facts + horizontal tiers that cool with age. That's the structure I'm building toward.
10
How I took a vibe-coded product into production. CreditNova is AI credit analysis for lenders. Every number on the deal has to be checkable. I didn’t write most of the code. Here’s the path that made that safe. 🧵
2
91
Eight agents · three sections · parallel where they can. 1 — extract ×4: financials, bank statements, corporate search, credit bureau. 2 — adverse media + cross-document check. 3 — report generation + findings commentary. One job each. A headline can’t move a number.
1
17
Workflow section 3 — report and commentary. 20+ ratios in code. Every figure back to a page. The agent explains and flags. The analyst decides. Deterministic where it can be. Agentic where it has to be. TAO Solutions · app.creditnova.ca — lenders: DM.
13