[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"term-t\u002Fthe-squint-test":3,"related-t\u002Fthe-squint-test":60},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":54,"sitemap":55,"stem":58,"subcategory":6,"__hash__":59},"terms\u002Fterms\u002Ft\u002Fthe-squint-test.md","The Squint Test",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 - The Vibe Check",[16,17,18],"p",{},"You don't read every line, you squint at the shape of the diff. Consistent indentation, no obviously screaming variable names, nothing that looks like it's reaching outside its lane, good enough, ship it. The squint test is judging AI-generated code by its silhouette instead of its substance, on the theory that bad code usually looks wrong even from a distance.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"The squint test is an informal, low-effort review heuristic where a developer evaluates AI-generated code based on overall visual pattern and structure rather than detailed logical verification. It catches gross anomalies quickly but is unreliable for subtle bugs, incorrect edge-case handling, or security issues that look syntactically identical to correct code.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"It passes the squint test, that's about as much review as I have time for right now.\" \u002F \"The squint test missed it because the bug looked exactly like every other line around it.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"vibecoding","You don't read every line, you squint at the shape of the diff.","beginner","md","t",{},true,"\u002Fterms\u002Ft\u002Fthe-squint-test",[49,50,51,52,53],"The Skim","Code Review","Vibe Check","Code Smell","Rubber Stamping",{"title":5,"description":41},{"changefreq":56,"priority":57},"weekly",0.7,"terms\u002Ft\u002Fthe-squint-test","E7pOUoHMUbErkZKXUZQ3STl2e2FaE7uOOCs_ZDPYPCY",[61,65,69,72,75],{"title":50,"path":62,"acronym":6,"category":63,"difficulty":42,"description":64},"\u002Fterms\u002Fc\u002Fcode-review","general","A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.",{"title":52,"path":66,"acronym":6,"category":67,"difficulty":42,"description":68},"\u002Fterms\u002Fc\u002Fcode-smell","architecture","Code that works but feels... wrong. Like when food smells slightly off — it might be fine, but something isn't right.",{"title":53,"path":70,"acronym":6,"category":63,"difficulty":42,"description":71},"\u002Fterms\u002Fr\u002Frubber-stamping","Approving a pull request without actually reading the code. Just clicking 'LGTM' and moving on. We've all done it. We've all been burned by it.",{"title":49,"path":73,"acronym":6,"category":40,"difficulty":42,"description":74},"\u002Fterms\u002Ft\u002Fthe-skim","The agent hands you a 600-line diff. You have eleven minutes before your next meeting.",{"title":51,"path":76,"acronym":6,"category":40,"difficulty":42,"description":77},"\u002Fterms\u002Fv\u002Fvibe-check","A vibe check in dev culture is when you step back and ask 'does this feel right?' before shipping.",1792528130749]