GEEKWORK

The Handover Test

If your AI tool vanished tomorrow, how long before you're stuck?

It's Monday. Claude Code, Cursor, Lovable or Replit has gone, and a good developer who has never seen your app walks in. Eight questions about what they'd find. Two minutes. Find out how long they'd last, and what to fix first.

01Where's the code?
02Could they run it on their own machine?
03How would they find out what it's supposed to do?
04How does a change get to the live site?
05Hosting, domain, database, payments: who holds the logins?
06What does the code look like inside?
07If they changed the login page, how would they know they hadn't broken checkout?
08Could they tell what data is stored, and why?
0 of 8 answered

Automated tools can tell you how code looks. They can't tell you whether a person can live with it.

So we run the Handover Test for real. An engineer who has never seen your app takes two of its features and tries to understand them, fix something and add something, as a new hire would. You get a written account of how far they got and what stopped them. It's part of every Geekwork review. How the Maintainability Test works

Three more, while the kettle's on: The Vibe Check, is your AI-built app ready for real customers, Spot the Bug, six pieces of AI-written code with real problems to find, and Launch Day, a three-minute battle in the style of the console role-playing games of the early 2000s, where the AI says the bug is fixed and you decide whether to check.