No Code: write nothing, deploy nowhere
No Code is a one-page joke repo, not a framework — its entire README is a deadpan tutorial for shipping software by doing nothing. The bit works because it nails the tone of real DevOps docs: numbered steps, code blocks, a 'Contributing' section. It's worth a two-minute read if you enjoy dev humor, worthless as anything else, and that's exactly the point.
No Code: write nothing, deploy nowhere
No Code is kelseyhightower's satirical GitHub repo built as a parody of the 'no-code' movement: the whole thing is a README that walks through 'writing' an app by writing nothing, 'building' it with an empty code block, and 'deploying' it nowhere. It's a joke, not a framework — there's no source code to install or run, just a README styled exactly like a real project's getting-started guide.
Why a project that does nothing went viral
No Code went viral purely on execution: the README mimics a real project's structure — Getting Started, Building the Application, Deploying, Contributing — closely enough that it reads like a legitimate tutorial for the first few lines before the joke lands. The whole bit is four sections. Every 'command' is an empty code block, and the payoff scales with how deadpan you keep reading it. It's a repo built entirely to be shared, not used — the kind of thing one developer sends another with no caption needed.
What the documentation claims to offer
- ✓A 'Getting Started' section whose only instruction is to not write any code
- ✓A 'Building the Application' step that runs an empty code block and calls it done
- ✓A 'Deploying' section that walks through deploying the app 'absolutely nowhere'
- ✓A scaling step for when 'it comes time to scale the application' — also an empty code block
- ✓A 'Contributing' section that answers its own question ('You don't.') in two words
- ✓The repo's license is set to Apache-2.0, as if it were a real piece of licensed software
Strengths
- ✓Short — the whole joke is readable in under two minutes
- ✓The README structure (Getting Started, Building, Deploying, Contributing) is genuinely well-organized, which is what sells the joke
- ✓Licensed under Apache-2.0 like a real project, a small extra touch of commitment to the bit
- ✓Doesn't overstay its welcome with extra sections or forced jokes
The one limitation that makes it unusable
- △There's no actual application, script, or Dockerfile logic to run — despite the repo listing Dockerfile as its primary language, the README never shows a real Dockerfile, so there's nothing to clone and execute
- △The joke is the entire content — once you've read the four sections, there's no deeper functionality, docs, or examples to explore
- △It teaches nothing practical about real no-code tools or platforms; anyone searching for an actual no-code solution will find nothing usable here
Other legendary satirical GitHub projects
Common questions about No Code
No Code is not a real programming tool — it's a satirical GitHub repo whose README walks through 'writing,' 'building,' and 'deploying' an application by doing nothing at every step, ending with instructions to deploy 'absolutely nowhere.'
No Code lives under the GitHub account kelseyhightower, at github.com/kelseyhightower/nocode. The README doesn't name any other author or contributor beyond that repository ownership.
No Code is released under the Apache-2.0 license, the same license shown in the repository's GitHub metadata. It applies to the README content itself, since there's no actual application code in the repo to license.
No Code earned its following through timing and execution rather than utility: the README mimics a real project's structure (Getting Started, Building, Deploying, Contributing) closely enough that developers share it as an inside joke about software complexity and no-code hype.
No Code does not deploy anywhere — the README's 'Deploying' section is explicit that running its command deploys the application 'absolutely nowhere.' There's no deploy target, cloud config, or infrastructure behind it; that line is the entire joke.
The Contributing section in No Code consists of one line answering how to contribute: 'You don't.' It's the shortest section in the README and doubles as the repo's closing punchline.
Best use cases
- •Sending it to a teammate mid-standup when a 'no-code' pitch comes up as a joke
- •Reading it as a two-minute palate cleanser between real documentation
- •Using it as a reference for how deadpan a fake README can be when writing your own joke project
- •Showing new hires what a minimal, well-structured README skeleton looks like, minus the content
Who should try it — and who should skip
Developers who enjoy dry, format-accurate parody — the kind of person who'll appreciate a fake 'Contributing' section more than a real one — should read No Code once and move on. Anyone actually evaluating no-code platforms, looking for a Dockerfile-based starter, or expecting runnable code should skip it entirely; there's nothing here to install, and treating it as a real tool is the one way to misuse it.
Want a second opinion on nocode?
Ask an AI that can read this page — one click and you get its take on nocode.
