PRE-LAUNCH · BUILD 0.0.1

OBITUARY EDITION · MMXXVI

THE IDE IS DEAD.
CURSOR WAS LIFE SUPPORT
- A FOSSIL WITH A CHAT PANEL .

LET RIP.

Thousands of engineers are burying their IDEs

Surfboard-shaped tombstone for the IDE — died of nostalgia

THE IDE.RIP DAILY — VOL. I, NO. 1 — A WAKE

EST. 2026 OBITUARY EDITION PRICE: FREE

A MANIFESTO
FOR THE POST-EDITOR ERA.

Read aloud. Slowly. Then close your IDE.

Syntax was never the genius.

Learning syntax, like learning a language, means you can communicate. You can speak. Nothing more.

Every good developer, CTO, seasoned product manager knows that great software is in planning, database design, software architecture and user experience. if(you can only write the code) { you were crap anyway }. The genius was elsewhere.

If AI is exceptional at speaking syntax — in a post-AI world, IDEs are dead. The genius you can bring is product direction.

LET RIP.


AI is not new.

“I've been using AI for 20 years. It just used to cost £180k a year and need a 1:1 every fortnight.”

Chief product officers have been using “AI” for years. It just used to be a team of engineers and designers that needed prompting.

The new team is Claude, Codex, et al. Faster. Still screws up. Still needs management. But when you LET RIP, a production-ready product can now be achieved in days.

LET RIP.


The cockpit was the problem.

Cursor. Copilot. Windsurf. Brave attempts. They put an AI co-pilot next to the human pilot and called the cockpit modern.

But the cockpit was the problem. The plane didn't need two pilots. It needed a flight plan and a destination.

Lovable and its cousins went the other way. They removed the cockpit and handed you a paper aeroplane. Beautiful for a demo. Useless for a business.

Neither side admitted the obvious: the editor itself was the bottleneck.

“Cursor kept the IDE on life support and called it the future.”
It was a fossil with a chat panel.

The unit of work has changed.

It used to be the keystroke. Then the line. Then the file.

Now it's the phase. Discovery. Schema. Spec. Ship.

You don't write code. You carefully direct it. You don't open files. You open plans. You don't debug for an hour. You reject a PR in ten seconds.

The AI writes. You curate. You own the vision, what's kept and what's killed.

That's not vibe coding. That's the new job.


This is not for everyone. It's for the survivors.

It's 2028. There are two types of survivor:

The engineer who skilled up in product. They've upskilled in delivery end-to-end. They prevent tech debt before it lands. They push back on every poor technical decision the AI tries to make.

The product person who skilled up in tech. They've upskilled in the stack. They apply their creative and delivery instincts to end-to-end shipping. They guard quality the way they used to guard the roadmap.

LET RIP is for the ones who can give clinical, specific, opinionated direction, and want a system that turns it into a product that doesn't fall over on day one.

It's 2028. Everyone who didn't Let Rip is catching up, or left behind.

“Vibe coding got you a prototype.”
Let rip and you get a product.

The text editor is dead.

You are the curator.

LET RIP.

SIGNED — THE Let.Rip CONSPIRACY Let.Rip

§ 04 — THE SYSTEM

A BRAIN FOR THE WHOLE BUILD. Vision. Roadmap. Specs. Stack. Code. Tests. Docs — one living model. Always coherent. Always current. YOU READ THE WAVES AND CURATE THE RIDE.

01
IMAGINE
You imagine and describe the product.
Let.Rip creates a roadmap with releases, epics, dev phases, acceptance criteria, test plans, risk flags. You're ready to ride.
02
CURATE
Direct every phase. Curate production.
Every phase is planned, you curate options on product direction, technology decisions, UX flows, UI. You're in control. Let.Rip pedals.
03
CODE
Using your Claude/Codex subscription.
No more expensive API calls and Cursor subscriptions. Let.Rip uses the CLI tools compliantly. Let.Rip fast, hard and cost efficiently.
04
DOCUMENT
Perfect docs you'll never read, but need.
Every phase has a spec. Decisions are logged. Implementation is documented. Let.Rip keeps everything current. You may never read the docs, BUT, context for AI is now perfect.
05
TEST
Full testing suite, plus manual tests.
TDD is back. Full testing suite. Browser tests automated by the AI, and manual tests documented and tracked against every phase.
06
SHIP, LEARN, IMPROVE
Let.Rip learns, fixes & suggests.
Let.Rip fixes bugs automatically, analyses feedback and requests and makes roadmap suggestions. … coding is dead.

§ 05 — THE NEXT GENERATION

BUILT FOR PEOPLE WHO REFUSE
TO OPEN ANOTHER .tsx FILE.

If you can give a sharp instruction, you can ship a real product. If you can't, no editor in the world will save you.

FOR THE LEAD ENGINEER
You stopped writing code last quarter. You just hadn't admitted it to your team. Let.Rip is where you admit it — and start out-shipping the rest of engineering.
FOR THE PRODUCT MANAGER
You can finally ship the thing in your head without booking three engineers' calendars. Acceptance criteria become acceptance tests. The Jira ticket is the merge.
FOR THE FOUNDER
Your AI subscription is already paid for. This is what lets it actually finish something. Demo to revenue without hiring two engineers to clean up after the agent.
FOR THE BUSINESS ARCHITECT
Oi hi there unsung hero 👋.

You who knows how to take needs and pain and turn them into requirements. This is your time. Take the spotlight. We have everything else covered. Let.Rip.

§ 06 — CODE BY VIBE

THE TOY WAY vs. Let.Rip

Lovable, Bolt and the rest got you to a screenshot. We get you to a system of record.

METRIC
THE TOY WAY
Let.Rip
The unit of work
A line of code
A phase
What you open
A file
A roadmap and worklog
When the AI loses the plot
It invents another one
Let.Rip forces focus.
Delivery
Vibes-as-a-service
Planned. Executed. Tested.
QA
Manual, eventually
Documented. Automated. Tracked.
Source of truth
Git history
Roadmap, decisions, documentation, always up to date.
What you get
A repo you inherited
50x productivity. Less stress. More shipped. Better docs.
When you ship
When it compiles
Constantly.

CLAIM YOUR BOARD

BE FIRST TO
LET.RIP

Private beta opens Q3 2026. The first 1,000 operators get lifetime founding access and pricing, a real headstone in the digital cemetery for their old tools, and free listings in the Let.Rip product directory.

Your role

no spam. one email per phase ship. unsubscribe = your IDE comes back.

§ 08 — LAST WORDS

QUESTIONS FROM THE MOURNERS.

Wait — is this actually replacing my IDE?+

Yes - and your project management system, and JIRA, and your testing platform, and your Notion documentation ... and probably more. You can always open it if you're feeling nostalgic.

What if I want to look at the code?+

You always can. Let.Rip is not a black box. Every phase produces a reviewable diff, a self-written PR description, and a passing test suite. The difference is you’re reviewing outcomes, not authoring inputs. Your IDE becomes what cat and less became when IDEs arrived: a viewing tool, not a working tool. It doesn’t die. It gets demoted.

How is this different from Cursor / Copilot / agent mode?+

Cursor and friends are editors with an agent in the sidebar. The human is still expected to live in the file. Let.Rip is an agent with a foreman on top. The human lives in the plan. The file is an artifact, not a workspace. The other difference: scope. Cursor helps you write a function. Let.Rip ships a product — roadmap, schema, auth, billing, QA, release notes, roadmap update, all phases of one running job.

How is this different from Lovable / Bolt / v0?+

If you're qualified to use Let.Rip and you've used these tools, you know the frustrations. They're landing-page generators with a database bolted on. They are wonderful for a weekend. They collapse the first time you need a migration, a real auth model, a third-party integration, or someone to call when production breaks at 2 AM. Let.Rip is for professionals.

Will this work for my real, complicated, legacy codebase?+

Yes — that’s the whole point. Let.Rip plans against the codebase you have, or starts from scratch. Let.Rip reads the repo, builds a model of what’s there. We build the roadmap on top.

What does it cost?+

Pricing announced during Private Beta (Q3 2026). Huge discount for first 1,000 users.

Are you serious about the tombstones?+

Deadly.