@kangamerchant Trading next years first round pick for an end of round 1 selection; and not playing the guy in the 1’s in his 2’d year is ridiculous… Whitlock in.
Last month I founded an AI startup.
I can't code.
That used to be a problem.
Now it's a "founder advantage."
I call myself a "vibe coder."
That means I describe what I want to an LLM and paste whatever it gives me.
I don't read it.
Reading code is for people who write code.
I write prompts.
My first prompt was "build me a SaaS platform."
It built something.
I deployed it.
I don't know where.
But it has a URL and that's enough for a seed round.
I raised $2.3 million.
The pitch deck said "AI-native architecture."
That means Claude wrote it.
All of it.
The architecture. The deck. The financial projections.
I prompted "make the projections look ambitious but believable."
It hallucinated a $40M ARR by year two.
That's not believable.
But VCs don't do math.
They do vibes.
Hence the term.
My CTO is also me.
I put it on LinkedIn.
"Non-technical founder serving as CTO."
Someone commented "that's brave."
It's not brave.
It's just that engineers cost $200K and prompts cost $20 a month.
I have 14,000 lines of code.
I
've read none of them.
But I did ask Claude to "review the code for quality."
It said the code was "well-structured and clean."
It wrote the code.
Of course it said that.
That's like asking your barber if you need a haircut.
A security researcher DMed me.
Said my app had a path traversal vulnerability.
I didn't know what that meant.
I pasted his message into Claude.
Claude said "this is a serious security concern."
I prompted "fix it."
It changed something.
I deployed it.
The researcher DMed me again.
He said I'd introduced three more vulnerabilities.
I blocked him.
Problem solved.
That's founder mentality.
I hired my first employee.
Also a vibe coder.
His resume said "built 200+ applications."
He meant he clicked "accept" in Cursor 200 times.
But that's experience now.
We pair program.
That means we sit next to each other and prompt the same LLM from different laptops.
Sometimes we get different answers.
We pick whichever one runs without a visible error.
Visible is doing a lot of work in that sentence.
We don't have tests.
Tests are for code you understand.
We have "confidence."
Confidence means it loaded once in Chrome.
We shipped to production on a Friday.
Everyone said don't ship on Friday.
But we don't have monitoring.
So every day is the same.
If a server crashes in the cloud and nobody's watching the logs, does it make a sound?
Philosophically no.
Financially also no.
Because we don't have logging either.
A customer reported that the app was "leaking data."
I said "leaking is a strong word."
He said his API keys were visible in the page source.
I said "that's a feature for power users."
He cancelled.
I marked it as churn due to "product-market fit recalibration."
We process payments.
I asked Claude to "add Stripe."
It added Stripe.
I think.
The money arrives somewhere.
Most months it arrives in our account.
I don't ask about the other months.
Our database has no authentication.
I didn't ask for it.
The LLM didn't suggest it.
We're in an open relationship with our users' data.
They just don't know it yet.
Someone found our database on Shodan.
I didn't know what Shodan was.
Now I do.
So do 40,000 other people.
Including our users.
Former users.
I went on a podcast.
The host asked my "tech stack."
I said "mostly Claude and whatever npm packages it feels like installing."
He laughed.
I wasn't joking.
There are 847 dependencies in our package.json.
I recognize none of them.
One of them is from 2016 and hasn't been updated since.
It's probably fine.
"Probably fine" is our internal SLA.
We got accepted into an accelerator.
The application asked about our "moat."
I said "speed of execution."
Speed of execution means I can mass-produce bugs faster than anyone can find them.
That is technically a moat.
The demo day is next week.
I need the app to work for eleven minutes.
After that it can do whatever it wants.
It usually does.
I'm raising a Series A.
$12 million.
The deck says "built by a team of elite engineers."
The team is me, a guy who also can't code, and an LLM that doesn't know we're in production.
But we move fast.
We break things.
Mostly our own things.
Sometimes other people's things.
We'll figure out the difference later.
I still can't code.
But I have a mass-producing liability factory that works some of the time.
In 2026, that's called a company.
And the graph goes up and to the right.
Because I asked Claude to make sure it does.
we're making @blocks smaller today. here's my note to the company.
####
today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.
first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.
we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.
i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.
a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.
we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.
to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.
to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.
jack
Our first glimpse suggests Sandover is a unicorn 🦄: a massive high-grade fluorite endowment, at the surface, with ideal metallurgy & adjacent to Molyhil.
Deep, long-term value for @Tivan_Limited & further strengthening of 🇦🇺🇯🇵 in critical minerals. https://t.co/9XMuMyFctv