(art/white-rabbit-v1.png)  (_next/static/css/index.Dkf7_0Bs.css)  (_next/static/chunks/index-BcvVkZKl.js)  (https://www.vibecoding-motherfucker.com/_next/static/chunks/layout-segment-context-CzUQ8SQ8.js)  (https://www.vibecoding-motherfucker.com/_next/static/chunks/table-Mv4XgFwE.js)  (https://www.vibecoding-motherfucker.com/_next/static/chunks/engineering-marquee-bxC-ChV2.js)  Vibecoding, motherfucker?        (favicon.svg@v=rabbit-v1)  (_next/static/chunks/index-BcvVkZKl.js)  (_next/static/_vinext_fonts/anton-51cfbbdeed62/anton-75f46c51.woff2)  (_next/static/_vinext_fonts/geist-8ac0455e797f/geist-98bbbccb.woff2)  (_next/static/_vinext_fonts/ibm-plex-mono-fb0034d93db3/ibm-plex-mono-d7731959.woff2)  (_next/static/_vinext_fonts/ibm-plex-mono-fb0034d93db3/ibm-plex-mono-8d0aead6.woff2)  (_next/static/_vinext_fonts/ibm-plex-mono-fb0034d93db3/ibm-plex-mono-8864f199.woff2)   (index.html#manifesto) Skip to the manifesto (index.html#top) ()  VIBECODING, MOTHERFUCKER?  (index.html#manifesto) The manifesto ↘    VIBECODING, MOTHERFUCKER?  (Neo from The Matrix aiming a pistol toward the viewer, in flat black-and-white stencil art.)   We use AI to build faster. Use the time it saves to study, investigate and solve harder problems. Don’t stop at the first answer that looks right. Do the fucking work. Know why the system works. Read the docs. Trace the data. Compare designs. Explain the tradeoffs and reproduce the failures. When a result surprises you, find out why. A model can repeat the same wrong assumption in code and tests. Work out expected results from the requirements, separately from the implementation. Try to disprove your explanation. Investigate the gaps that matter. Build something useful. Check that it solves the user’s problem. Measure behaviour under load. Go deepest where failure costs most. Own the decision to ship and the work of fixing it. Learn from the machine. Change your mind when the evidence demands it. KEEP FUCKING THINKING.      OUR VALUES  What we value Where it goes wrong What we fucking do   Learning Reading the answer and skipping the subject.  Study the underlying concepts. Build a small example. Change it and explain what happens.   Design Accepting a design without checking its assumptions.  Compare alternatives against requirements. Explain what you gain, what you give up and why.   Evidence Looking for tests that confirm your answer.  Choose a case that could prove you wrong. Investigate results that don’t fit.   Scale Calling it scalable because it runs locally.  Load-test realistic traffic. Profile the bottleneck. Measure latency, throughput and cost.   Usefulness Adding features without checking who needs them.  Watch users complete the task. Change the design when their behaviour contradicts your assumptions.   Ownership Treating deployment as the end of the job.  Track outcomes after release. Investigate failures, verify recovery and follow through on fixes.         Engineering, Motherfucker Engineering, Motherfucker Engineering, Motherfucker Engineering, Motherfucker  Engineering, Motherfucker Engineering, Motherfucker Engineering, Motherfucker Engineering, Motherfucker   Inspired by(https://programming-motherfucker.com/) Programming, Motherfucker