· 8 min
A senior's checklist for reviewing AI-generated code, ordered by cost of error — the bugs that read perfectly and pass a normal eyeball review.
All tags
Available
Iurii Uses: #Code Review
1 article · 4 reviews
Code review posts cover techniques for giving and receiving useful feedback on pull requests — how to catch real bugs, write actionable comments, and make reviews a learning experience rather than a gate.
Articles
Reviews
“
Before we closed on a seed-stage SaaS we asked Iurii to look under the hood. He gave us a written report in five days: what was solid, what was held together with tape, and roughly what it would cost to fix the worst of it. He flagged a scaling bottleneck in their database layer that the founders hadn't mentioned, and rated the rest realistically instead of either rubber-stamping it or scaring us off. That report changed how we structured the deal.
Florian Berg 🇨🇭
Investment Principal
Databases
Service: technical due diligence
“
We were about to hand a project off to a new development team and I wanted someone to look at the code first. Iurii reviewed it and found a few things that would have caused real problems down the line. The new team thanked us for the cleanup.
Pierre Moreau 🇫🇷
Service: technical consultation
“
I'd built most of our MVP with Cursor and it looked finished — it compiled, the tests were green, the demo worked. It just wouldn't survive real users. Iurii took it over and found what I couldn't see: authentication handled four different ways, tests that only asserted what the code already did, and a dependency list half of which was unused. He didn't rewrite it from scratch — he told me honestly what was salvageable, ripped out the dead code, and got it to something a real team could build on. Two weeks and it went from 'looks done' to actually shippable.
Sebastian Falk 🇸🇪
Founder
Service: rescue projects
“
We had an acquisition offer on the table and I needed to know whether our own codebase would survive the buyer's technical review before I walked into that room. Iurii did a five-day independent audit and gave me a written report I could actually act on — what was solid, the two things that would raise flags in a data room, and what it would take to fix them first. He caught an undocumented dependency on one ex-contractor's private package that would have been a red flag the moment their team looked. We cleaned it up before diligence started, and the deal closed without a single technical concession. Best money I spent on the whole process.
Wouter Claes 🇧🇪
Founder & CEO
Service: technical due diligence
AvailableGot a project in mind?
Whether it's a new product, an integration, or scaling an existing system — let's talk about how I can help.