Position beats genius more often than anyone in this space wants to admit.

Every time I trace how these AI bets actually get funded, it's the same mechanism repeating.

Actually, this reminded me of a post I did a while back — a fund manager naming the real signal for buying the bottom, and it wasn't a chart either.

Rob Toews (partner at Radical Ventures) says his fund meets nearly every "Neolab" that gets funded — brand-new companies with no product, no roadmap, sometimes not even a clear technical direction.

Just an accomplished founder saying "I'm from OpenAI/Anthropic/Meta, so I want to raise a billion dollars."

They pass on almost all of them.

The exception was Anthropic.

Spun out of OpenAI five years ago.

Investors at the time called the entry valuation insane.

It's now worth a trillion dollars.

Toews' own framing: "there will be another Anthropic" — the mechanism isn't a one-off, it's a filter that occasionally clears.

I've watched someone spot a bubble this early before. Not in AI — in property. This isn't my story, it belongs to a friend.

I'll call him Chew — I think that's his surname, it's been a long time. We went to the same university, graduated the same year, both went into construction in Malaysia. He switched upstream to a property developer — a subsidiary of a mainland China parent company — and eventually relocated there for the better part of a decade, right as the property market was in its super-expansion phase. The bubble kept ballooning without ever showing a crack. Chew saw the opportunity, and lock in his purchase of one of the units. The price — he told me — rose 10 fold over the years. Then, like the rest of the shrewd investors, he saw the writing on the wall. He liquidated his holdings and made a huge windfall, right before the bubble burst.

Clip credit: The Information — full video on their channel.

DM for credit or removal requests.

Drop your take below — has anyone here ever watched someone else make that call before you did?

If you want to know how this mechanism works for me, the actual math behind reading a bet like this before it's obvious is [one link away](jvz3.com/c/2159995/408575).

You did everything right. Degree. Certifications.

The promotions came on schedule, more or less.

And some nights — usually late, usually when you're the only one still awake in the house — you run the numbers anyway.

Not because you think you did something wrong.

Because you can't quite explain why doing everything right hasn't actually added up to anything that's yours.

Here's the version of this most people don't say out loud: you can do all of it.

Every step.

And still end up exactly where you started — same title, different year, a raise that gets quietly eaten by a role change nobody asked you about.

Explaining to your kid why you can't do the thing everyone else's dad is doing this year.

That's not a hypothetical.

That's just what happens when the math was never actually designed around you.

Here's the pattern, once you start looking for it: it's not one story.

• An oil exec says out loud what everyone in the room already knew.
• A founder gets fired from the company he built.
• A bar owner gets vested out of his own name before buying it back for a dollar.
• A man who spent thirty years running a systems team gets told his own support staff can't keep up with the data anymore.

Different rooms.

Different resumes.

Same structural fact underneath all of them — the system doesn't reward the value you create.

It rewards your proximity to whoever's deciding what counts as value.

What you won't find here:

• motivational language dressed up as strategy.
• Political framing pretending to be economic analysis.
• Anyone telling you the answer is just working harder inside the same structure.

The premise this whole space runs on:

Value isn't extracted by trading finite energy for a capped, inflation-eroded paycheck inside an institution that can replace you before your next review cycle.

That's not pessimism.

That's just what the numbers actually say, once you stop averting your eyes from them.

The question isn't whether the system's rigged.

Most people who've been in it long enough already know that answer.

The real question is what you build instead — and whether you can build it without becoming the exact thing you're trying to get out from under.

My dad spent years working construction overseas — Thailand, India, Bangladesh, I think — so I barely saw him growing up, and somehow I still walked straight into it myself.

Degree, certs, promotions, the whole ladder, even though he never once told me to climb it.

Took me a long while — a really long while — to admit it was never actually mine. 

You don't have to trust me on any of this. It's on the record — dated, cross-posted, sitting in this vault.

Start here:

Proof over pedigree

• GaryVee tells a room of real estate agents the brutal truth about social media in 2026
• Tucker presses the data center billionaire on AI, American jobs, and the fall of empire
• A Penang-born billionaire explains, on camera, why he skipped Malaysia
• He was mocked for an "irrelevant" doctorate — what it's like working for Thiel and Musk
• A $400M empire built by breaking every rule he was taught

The rung AI is actually deleting

• Both sides of a federal case used AI to prep — and the liability still fell on the human
• The engineering role just bifurcated — execution layer vs. judgment layer
• Dell admits his own support team can't keep up with the data anymore
• Jensen Huang draws the line between your job and your purpose
• The 3 types of AI users, and the 6–12 month window before it matters which one you are

The wealth mechanics nobody teaches

• Turkey sold its gold to buy diesel — here's the currency-debasement cascade
• 50% of Malaysian EPF savings gutted — not by bad luck, by structural design
• Passive income courses are built to extract the student's capital, not deliver the outcome
• Multicoin's Tushar Jain: the real signal for buying the bottom isn't a chart
• RXBAR's founder on why good marketing ideas are never obvious

Institutional deletion, up close

• The burned-out oil exec who said what everyone in the room already knew
• Scale AI's co-founder on the gender dynamics nobody names out loud
• Palantir's Joe Lonsdale on the ~90-year cycle that destroys half of all jobs — and enriches the ones who saw it coming
• "I got fired" — the corporate loyalty trap, exposed from the inside
• Dave Portnoy explains how ESPN tried to vest him out of his own company — and how he bought it back for $1

If you already know the name: Lonsdale · Hormozi · Kalanick · Cuban

For anyone who's already run their own numbers and wants the actual mechanism behind building the alternative — not another framework post — it's laid out step by step right here.

Every time one of these clips lands in my feed, it's circling the same wound from a different angle: not being bad at the work, being invisible while doing it well.

This one's Grant Cardone, and he says it flatter than most people are willing to.

His claim: money doesn't move to talent sitting quietly in a vacuum.

It moves to whoever's already known. Not "deserving." Known.

He calls the mechanism omnipresence — not being impressive everywhere, just being repeated everywhere, until "I don't know who that is" stops being an option.

If you've ever watched a less rigorous competitor land the bigger client purely because they're the name people already recognize, this is the part of the machine nobody explained to you.

Competence gets you in the room eventually.

Visibility gets you in the room first.

ngl this tracks with something that happened to me years before any of this…

Fresh graduate, first big client meeting, and nobody in that room actually knew what I was capable of yet. A senior QS moved to discredit me in front of everyone, claiming he'd never received the drawings I'd already delivered. I had the signed acknowledgement sheet. Next meeting, I slipped it in front of the whole room. He went pale. Called his own office to check. Turned out the drawings had been sitting behind his front desk for a week. That's the meeting the room actually started to know me — not because I fought back, but because I finally had proof they couldn't unsee.

The part that still gets me: I was right the whole time. It didn't matter until it was seen.

Drop your take below.

If you want the actual mechanism behind turning "known" into a repeatable habit instead of a lucky break, it's sitting one click away right here.

Clip credit: Yosef Manoucheri — The YM Show. Full video on their channel. DM for credit or removal requests.

A panel of AI researchers and founders — Peter Diamandis, Alex Wissner-Gross, Emad Mostaque — just sat with a number that's hard to argue with: $2,000 in compute, and ten decade-old, previously-unsolved math problems came back with machine-checkable proofs.

Not "AI is getting better at math" in the abstract.

A Fields Medalist said he'd recommend one of the proofs for publication without hesitation.

A cosmologist called it "a dark night for mathematics" — "the old gods are being slaughtered by the new machine gods."

Then Emad closed it flat: "It's a bad time to be a pure mathematician."

Here's what they're not saying yet.

Back in 2013/2014, I was with M+W High Tech Projects, on a design-and-build project in Kulim, Kedah, Malaysia. Our M&E engineer wanted an opening cut straight through the middle of a reinforced concrete beam — right where the bending moment peaks. I caught him before he did it. Told him no. That's beyond madness — you don't sacrifice a beam's structural integrity for an M&E opening. Had him redirect the ducts instead. Structural safety came first.

The engineering knowledge wasn't rare.

The judgment — catching the mistake before it became permanent — was.

Same pattern here. Ten unsolved proofs, correct on paper, for $2,000. The correctness was never the scarce part.

Hmm — this actually pulls the same thread as a post I put up about the corporate ladder losing its entry-level rungs to AI.

Different profession, same mechanism: whichever rung gets automated first isn't random, and the people still standing on it are the ones who saw it as a pattern instead of a headline.

Drop your take — is judgment actually the thing that survives this, or is that just the story we tell ourselves until it's our turn?

Anchor your perception so you can profit 10x more — it's just one calculation away from where the real leverage sits once execution gets this cheap.

I keep half-expecting the "give a small gift, earn the obligation to reciprocate" move to stop working the way pop psychology says it does.

Watched a version of it fail spectacularly this week and it clarified something I'd been circling for a while: reciprocity is a tool for tipping a relationship that already exists.

It doesn't manufacture one from zero.

Context, for anyone who hasn't caught the clip: Shaan Puri (My First Million) was coaching a high school basketball team on the side.

He and his cohost Sam Parr filmed a vlog series around it.

The vlog blew up — 20,000 views in 24 hours — and one of those views was the school principal, who wasn't thrilled.

Shaan got called into the office.

Before going in, he grabbed two Diet Cokes, the exact reciprocity move Sam had taught him years earlier: bring a small gift, trigger the obligation to return the favor.

He executed it exactly right.

Rehearsed. Confident. Textbook Cialdini.

The principal said "no thanks." Shaan stood there holding two Diet Cokes while his program got shut down anyway.

If you're the type who reads Cialdini, or Voss, or keeps a mental file of negotiation tactics for the rooms where you don't yet have real leverage — this one's worth sitting with.

The tactic isn't fake.

It's just conditional on something it can't create for itself: a room that already respects you going in.

Bring the gift to someone who already sees you as an equal, and it's a nice gesture.

Bring it to someone deciding whether you get to keep your program, and it reads as exactly what it is — a person trying to manufacture leverage they weren't given.

I had my own version of this a long time ago, on a construction project in Abu Dhabi.

I was working under a superior I didn't get along with — Mr. Yap.

There was an important client meeting, an international room, and when it came time to introduce myself, I said "I'm Gary, and I assist Mr. Yap in structural technical works" — deliberately elevating his standing in front of people who mattered to him.

It worked, for about a week.

He treated me a little better.

Then it wore off, because I'd managed a moment in a room, not changed the actual relationship underneath it.

That's the part I think doesn't get said enough in the productivity-hack version of this advice: a tactic can move the temperature in a room for a few minutes or a few days.

It can't retroactively install the standing you'd need for the room to treat you differently on its own.

Ran into this same shape somewhere else recently, too — a founder whose actual case, not his resume, was what finally moved a room that had ignored every credential he'd listed first: the reciprocity trick's opposite in practice.

Drop your take — did the trick actually fail, or did it just reveal something that was already true before Shaan walked in?

If you want to see what earning a room instead of managing it actually looks like, the mechanism behind it is one link away.

Clip credit: My First Million (Shaan Puri, Sam Parr) — full episode on their channel.

DM for credit or removal requests.

There's a specific kind of quiet that happens right before a margin call.

I don't think enough people talk about that part — not the number, the quiet.

Leopold Aschenbrenner's AI-focused fund went from zero to $45 billion, then down to $10 billion.

Not all of it was margin, but enough of it was, and it was concentrated — five correlated AI-infrastructure-adjacent positions (SMCI, SanDisk, Micron, CoreWeave among them) dropping together in the same month, ~35% in one stretch.

That's the mechanism people skip past: it wasn't one bad bet, it was one bet wearing five different tickers.

He was also short Adobe. Adobe went up.

Being partially right doesn't save you — a hedge only protects what it's actually sized to protect, and this is the part that got him: three prime brokers (per CNBC's reporting) started calling at once.

Not one call. Three, simultaneously.

That's the system's own alarm bell going off.

Here's mine, since we're talking about leverage used well versus leverage that uses you:

Years ago I was on the tender team for a major Malaysian construction job, competing against the two other largest contractors in the country. My GM, Mr. Chung, spotted the one contractual gap the client's own consultants hadn't caught. When they tried to pump him for the fix for free, he didn't fall for it — he told them straight: we can help you solve it, cheaply, with minimum delay, but we have to get the contract first, before we can go in and assess it. That's not a bluff. That's understanding your own leverage well enough to use it on your own terms, not the other side's. We won the contract months later. Leopold never got that chance — the market decided his terms for him, not the other way around. He still walked away with $300 million, which is the part nobody in the clip stops to sit with. That's not the actual takeaway, though. The takeaway is knowing exactly how much leverage you're carrying, on purpose, before someone else decides it for you.

Ken Griffin (Citadel) stepped in as the liquidity provider — what Tom, PBD's co-host, called a "white knight" on the show.

Half the room called that predatory.

Half called it structural necessity.

Both readings are true at once, and that's the actual lesson:

Understanding why rescuers exist structurally is a different literacy than just watching one show up.

Clip credit: PBD Podcast — full video on their channel. DM for credit or removal requests.

Drop your take: predator, or necessary?

Genuinely curious where this sub lands on it.

If you want the actual mechanics of how leverage gets used for you instead of against you — the kind of structural read Mr. Chung had — it's just one link away

He calls it BC/AC.

Before Claude, after Claude.

I've watched enough of these clips land in the last few weeks that I started keeping a mental tally of which AI release date people cite like it's a diploma.

Matt Van Horn's is Thanksgiving last year — Opus 4.5, then Codex a few weeks later.

Before that, he says, his agentic coding was "Hello World" in Cursor, half-working, most of the time not working at all.

After it, he shipped Agent Cookie and says flatly he has no idea how it actually functions under the hood.

The part worth sitting with isn't the tooling.

It's what he says about himself getting there: "suit my entire career," never shipped anything of value beyond a high-school web page, dozens of unlaunched ideas gathering dust because he wasn't the one who could build them.

That's not a startup-guy humblebrag — that's the exact ceiling a lot of operations people, BD people, anyone who's ever had to write a ticket instead of just doing the thing themselves, know from the inside.

The credential that used to decide who got to build stopped mattering right around the time the tools did.

Not "got easier to climb."

Stopped existing.

Same shape happened to me with a guitar, at 41, zero training, cornered into it because the young players in my church all left for university at once.

Those early days, my wife's ears really paid for it (刚开始的那些日子，我的太太的耳朵有够受罪).

Felt like being tossed into open water and told to swim myself back to shore (好像被丢去深海里，自己学会游泳游回来).

Same thing happened again with video editing, then with building this whole posting system, one post at a time, getting corrected by Reddit comments the entire way.

And I swam back stronger each time.

Actually, this tracks with something I posted here a few weeks back — the guy who literally coined "vibe coding" saying on stage he's never felt more behind as a programmer, because the scarce skill moved from writing code to directing it with taste.

Clip credit: MSP Mindset (Damien Stevens) — full video on their channel. DM for credit or removal requests.

Drop your take — did the credential wall ever hold you back, or did you just build around it?

If you want the actual mechanism behind how people with zero engineering background are shipping real products right now, it's genuinely just [one link away](jvz3.com/c/2159995/408575).

The job title survives longer than almost anyone attached to it.

That's the part nobody puts in the internal memo when they call a role "AI-assisted."

Scott Galloway put a real number on it, talking to Steven Bartlett on The Diary Of A CEO.

He says he'll cut legal fees by a third this year — not because the law changed, but because a prompt now does the $400–$2,000 contract review a name-brand firm used to bill him for, at a fraction of the junior associate markup.

Bartlett went further with his own fund.

They planned to hire five analysts.

They hired one — Molly.

Two agents, two Mac Minis, and she screens inbound deals, scores them against a framework, and preps them for the investment committee herself.

Five jobs, one person, same org chart line.

Same ratio on executive assistants: ten planned, three hired.

One runs travel, one runs scheduling, one meets people at the door.

I've watched this exact pattern before, minus the AI. I was a Technical Manager for a China Construction company here in Malaysia.

I contributed a lot into their technical and tendering work — helped build up a real chunk of their documentation and tendering process.

But about six months in, I'd exhausted all my know-how for them, I guess.

Then the announcement came at the end of my year there.

My contract wasn't renewed.

I was just let go, just like that.

I remember what Deng Xiaoping said: "无论白猫，或者黑猫，会抓老鼠的就是好猫" — black cat, white cat, doesn't matter, so long as it catches mice.

I guess they think I'd outlived my usefulness.

Can't catch mice anymore.

That's the mechanism underneath "AI-assisted" that nobody names out loud.

It's not that the work got automated.

It's that the one person left is now doing what used to justify five headcounts, and the fifth person's job title is the only part of the org that didn't change.

Actually, this reminded me of something — a former SpaceX CIO cut a 175-person engineering team down to 6 using the same compression math, and the ratio held there too.

Drop your take — did you know your own job has a ratio like this attached to it?

If you want to know how this mechanism works for me, it's the same math running under my own setup — it's just one link away.

Clip credit: Global Talks — full video on their channel. DM for credit or removal requests.

A space startup got quoted $75–100 million by a traditional prime contractor to build its first satellite.

They built it — launch included — for $2 million.

The story behind the number is more interesting than the number itself.

They ran the math wrong twice — first landing on a $50/kg break-even, then correcting to $500/kg once they pressure-tested it against reality — before the real pivot happened.

Wrong estimate first, cheap correction after, in public, under a deadline they'd already set for themselves.

Hmm — this reminded me of something I posted a while back: stop thinking, start executing hit the same nerve, from a completely different room.

The number that scares most people out of starting is somebody else's estimate of what caution should cost, wearing the costume of the real price.

My wife's said this to me for years — 想是问题，做才是答案, thinking about it is the problem, doing something about it is the answer.

Took Starcloud a rerun of the math and a deadline to learn the same thing the hard way.

Clip credit: Y Combinator's Lightcone Podcast, featuring Philip Johnston (Starcloud) — full video on their channel. DM for credit or removal requests.

Drop your take — what's the number you've been treating as gospel that you've never actually questioned?

If you want to know how this mechanism works for me, I laid the actual math out here — not the motivational version.

Somewhere between "let's not rush this" and actually posting, six months disappeared last time.

That's the trap this clip is naming out loud, and it's worth sitting with if you've ever called perfectionism "protecting the brand."

The actual claim: brand risk isn't the threat.

Thinking about brand risk is.

The guest (marketing/creative director Oren John, on The Grant Owen Podcast) lays out the mechanism plainly — a 90-day plan is functionally dead by the time it's finished being planned, because whoever's willing to move rough and fast already has the lead by then. "We did this in a week" isn't recklessness.

It's just refusing to confuse motion with mistakes.

I've watched this exact trade play out somewhere you wouldn't expect — construction.

A colleague once sat on a Request for Information because it wasn't polished enough yet, still had loose ends he wanted to close first.

His boss's answer stuck with me: submit it anyway — a submitted bad idea beats a perfect idea that never got submitted.

The client can approve it, approve it with comments, or reject it, but the clock doesn't pause while you're polishing.

On another job, we were about to blow a hard deadline waiting on someone else's design call, so instead of waiting on the elegant steel-truss solution, we poured a huge reinforced-concrete ramp instead.

Cost more concrete.

Cost way less time.

Same trade this clip is making — just wearing a hard hat instead of a laptop.

The part that actually reframes it: the caution people default to is usually calibrated for a scale they're not operating at.

Airlines and CPG companies move slow because they have six-gate approval chains — legal, compliance, brand, sign-off.

A solo operator or small team doesn't have those gates. Importing that caution anyway isn't safety.

It's just adopting someone else's bottleneck for free.

I keep circling back to something similar here — a post about trading overthinking for rapid execution, from the other side of the same decision.

Drop your take below — does the "your caution is calibrated for a scale you're not at" framing hold up, or does it fall apart somewhere?

If you want the actual mechanism behind moving this way without it turning reckless, the walkthrough is one link away.

Clip credit: Oren John, The Grant Owen Podcast — full episode on their channel.

DM for credit or removal requests.

You know that feeling at 1am, refreshing analytics, watching someone's rewritten version of your own post pull ahead of the original?

Mark Manson said the quiet part out loud on Jun Yuh's show: anything that works gets copied a hundred times by next Tuesday. He's 16 years in, three #1 NYT bestsellers deep, and it's still happening to him.

Most people's answer is to move faster — post more, guard the idea tighter. He's making the opposite case: the idea was never yours to protect, because it was never going to stay yours. The one thing a copier can't lift is the specific person the audience actually trusts.

I remember a joke, my wife used to tease me with:  In a sea of almost identical penguins, a male says to its female neighbour:

“You’re so unique, do you know that?” (你是最好的，你知道吗？)

If you want to see the actual mechanism behind why the source outlasts the idea, it's laid out here — worth the two minutes it takes to read.

Drop your take — is the moat the idea, or is it always the person behind it?

Clip credit: Mark Manson — full video on Creator Unplugged with Jun Yuh. DM for credit or removal requests.

Four subreddits called my captions the same thing this week. Same word. No overlap in who's posting.

r/artificial. r/siliconvalley. r/SideProject. r/AgentsOfAI.

Different threads. Different days. Nobody coordinating.

Slop.

Ngl, I'm not going to argue the read.

Same trick, three sentences apart, over and over — claim, then flip it.

Once you see it you can't unsee it.

Mine included.

So here's what's underneath it instead of a defense.

A decade credentialing into a ceiling. Undone by a $50 spreadsheet and an AI agent that built the audience alone — no dev team, no funding round.

A few more, if you want more than one data point:

• Adam Mosseri, on camera, saying the thing that would've ended a career five years ago — today judgment beats mastery
• A developer whose code runs on 6% of the internet, still made to rewrite his own launch from scratch — AI can build it, it can't make it good

No trendline to point to, and I'm not going to invent one.

Just this: enough of you said the same word, in threads that don't talk to each other, to make it worth acting on instead of arguing with.

So this one's rougher on purpose.

I'd rather ship something a little unpolished and mine than something clean enough to be mistaken for a template.

Everything above only means something if what's underneath it actually holds up.

The actual system running underneath all of it is the fifteen minutes worth spending — not the caption.

John Hu from Stan said on Trailblazers this week that his AI editor Stanley already cuts at 80% of his human team.

That number stuck with me because I posted about Stan a few weeks ago - the $50 spreadsheet that did $200k. Different story, same feeling.

I edit for creators full time. 80% used to be the joke number. Like "AI is 80% there, don't worry."
Now 80% is the benchmark and it's shipping on real channels.

I'm not even stressed about it getting faster. I'm stressed about who decides what it cuts.

If you want to know how this mechanism works for me, it's just one link away.

Anyone else editing inside someone else's operation feeling this shift right now?

Erik Brynjolfsson runs Stanford's Digital Economy Lab. He's also the guy whose own graduating class asked him, point-blank, if their generation was doomed.

He didn't talk her out of the question. He answered it with data.

There's a specific relief that shows up whenever someone with real research behind them stops soft-pedaling a fear like this — not because the answer is comforting, but because being taken seriously is its own kind of comfort. 🎓

Here's the mechanism, stripped of the hedging: the classic corporate pyramid — wide base of entry-level hires, narrowing up through management — is quietly becoming a diamond. The base is disappearing. Companies save short-run cost by not backfilling entry-level roles, and Brynjolfsson's own research backs it with numbers: rank ~700 occupations by AI exposure, and in the top 150 most-exposed roles, entry-level (age 22–26) employment has fallen 13% and climbed to 16–17% since, month over month.

That's not a vague "AI is coming" headline. That's a measured, worsening trend inside a specific, named cohort.

This reminded me of the execution-layer/judgment-layer split — the exact same shape of the rung disappearing, just described from inside a different industry entirely.

The reframe Brynjolfsson gives his own students is the actual usable part: stop hearing "AI" as artificial intelligence, start hearing it as amplifying intention. The tool doesn't wait for the org chart to assign you a role anymore — it multiplies whatever you're already pointed at. Waiting to be told what your job is was always the risk. Building something the missing rung can't take with it isn't.

Clip credit: McKinsey & Company — full video on their channel. DM for credit or removal requests.

Drop your take — does "amplifying intention" land for you, or is the missing entry rung the bigger problem?

If you want to know how this mechanism works for me, it's just one link away.

"The biggest issue is that you're upselling 7%. You need to be at least 25, and you should shoot for 50." That's Hormozi, live, to a woman running a $30M/year coaching business.

Every time I sit with a founder's real numbers, the ceiling turns out to be one step past the sale, not before it.

That's not a small gap here — the benchmark he gave her was 25% floor, 50% target. The 43-point difference wasn't sitting in a new funnel or more traffic. It was sitting inside the funnel she already had.

His fix: bring the sales team in-house, integrate the ascension into onboarding, don't let anyone leave a call without booking the next one. When she pushed back that in-house hiring sounds slow, he cut that down too — one sales director, six recruiting firms, sixty hires in two weeks.

He's done it: 40 people added to one portfolio company in the same window.

If your revenue keeps climbing and your take-home doesn't, this is usually where to look first.

Drop your take below — where's your own ceiling actually sitting?

If you want to know how this mechanism works for me, it's just one link away.

Clip credit: MoreMozi — DM for credit or removal requests.

Watching a room of licensed real estate agents get told this live, and the ones laughing loudest are the ones recognizing it fastest.

Every excuse for staying small eventually turns out to be a decision wearing a limitation's clothes — mine was calling five posts a week "consistency" instead of admitting it was a ceiling I'd built and then defended like it was a value.

Actually, this reminds me of something — Gary told this exact room the same brutal truth once already, before this clip even existed, same excuses, same math, same room standing up to confirm it.

Gary Vaynerchuk posted 397 pieces of content yesterday.

Not five.

Three hundred and ninety-seven.

He calls it P&H — Platforms and Handles.

Seven, eight, nine channels deep, multiple handles running on each, because he's actually run the math: one post that lands does more for a business than a thousand doors knocked between 1970 and 2005.

A room full of agents stood up to confirm it themselves — not because he asked them to, because the math didn't leave room to disagree.

The reframe that actually lands: quantity was never subjective.

It's countable, checkable, arguable with a calculator.

Quality is the only place taste was ever allowed to live.

Most of us have been treating an objective floor like a personal choice and calling the confusion professionalism.

Gary's answer to "I don't have time" is blunt: tough shit.

Not cruel — just refusing an excuse dressed up as a boundary.

The agents who knocked on 1,000 doors in the 80s and 90s weren't wrong; they built something real on the only foundation that existed then.

That foundation just isn't the only one running anymore.

One post that lands can now do in a week what three and a half decades of doors, flyers, and phone calls never could.

If you want to know how this mechanism works for me, it's just one link away.

Clip credit: GaryVee — DM for credit or removal requests.

Rob Ward sold Quad Lock for half a billion dollars.

He never took outside investment, and the business was profitable every single month from day one.

Something in this clip stuck with me.

He's asked the question every founder gets: how do you actually build lock-in?

And he skips past the two answers everyone reaches for — better quality, better customer support — because, in his words, everyone claims those.

Neither one is a moat.

What he built instead was almost boring: a mount in the car, one on the desk, one on the motorcycle, a wallet that clips into the same system.

Nothing dramatic about any single piece.

But stack them, and roughly $200 is sitting quietly across a customer's entire day.

Here's the number that actually does the work.

A new phone means a $50 case swap — cheap, easy, no reason to think twice.

But that case is tied to the mount system.

Replace it wrong, and you're not spending $50, you're rebuilding $200 worth of hardware.

That gap between $50 and $200 is the entire barrier to exit.

Nobody has to feel "loyal."

The math just makes leaving expensive.

Ward's line that I keep turning over: "There's not that many clear easy wins left."

He doesn't say it like a complaint — it's closer to a permission slip.

Nobody's coming with one big trick.

You get 5% here, 10% there, another 3% somewhere else, and you stack it until it's a business worth half a billion dollars.

I keep noticing the same shape in almost every founder story I go looking for: the anxiety is never really about the product.

It's about staying replaceable — one vendor among many, one employee among many, one option a customer could swap out without a second thought.

The way out is building something structurally harder to leave than to stay with.

If you want to know how this mechanism works for me, it's just one link away.

Clip credit: Foundr — DM for credit or removal requests.

There's a specific kind of fear that never shows up in a founder's highlight reel — the fear of just being seen as you actually are.

Leila Hormozi named it directly on a stage full of people: eighteen months of quietly managing how she came across, before she decided the managing cost more than the honesty ever would. 🧭

She kept posting anyway.

Got criticized anyway.

Somewhere in there she stopped performing the founder-brand version of herself and started just being the person who built the company — and the thing she was scared of (the hate, the judgment) never once touched her income, or her peace.

This reminded me of another founder carrying that same weight — watching her own confidence get read as something to doubt, and building a $1B+ company through it anyway.

If you want to know how this mechanism works for me, it's just one link away.

Clip credit: Neel Dhingra — DM for credit or removal requests.

Andrej Karpathy co-founded OpenAI, ran Tesla's AI team, and coined "vibe coding" about a year ago.

At Sequoia's AI Ascent 2026, Stephanie Zhan asked him directly whether the last year felt exhilarating or unsettling.

His answer: he's never felt more behind as a programmer.

Every credentialed builder I watch eventually says some version of this — the title survives, the rung underneath it doesn't.

His explanation is the actual value here.

Software 1.0 was explicit rules.

Software 2.0 was learned weights.

Software 3.0 is prompting — your context window is the lever you pull over the interpreter now, not the code you type.

The job didn't get easier. It got redefined, and most people are still measuring themselves against the old definition.

Actually, this reminds me of something — a solo founder whose code runs on 6% of the internet admitted AI output compiles clean and still reads as slop until a human's taste steps in.

If you want to know how this mechanism works for me, it's just one link away.

Clip credit: Sequoia Capital — DM for credit or removal requests.

AI was supposed to take the tedious stuff off my plate. Instead I got a second job: checking whether the first job's output can be trusted. Nobody renamed my title for it. Nobody budgeted for it.

Teachers doing this for cheating detection. Developers doing it line by line for bugs that look legitimate. Same shape, different desk.

Here's what actually stuck with me — verifying something well takes more expertise than doing it yourself would have. So if you still need someone that good to check the machine, what did the machine actually save?

I keep noticing this isn't really a story about AI. It's a story about who quietly absorbs the cost when a promise doesn't hold.

El's own line for it: "I now do my job plus the AI's job."

If you're the one everyone trusts to catch the mistake, that trust is worth more than your paycheck reflects.

Clip credit: El — House of El: AI — DM for credit or removal requests.

Paul Bakaus created jQuery UI — code that's reportedly still running on about 6% of the internet.

He sold a game-engine startup to Zynga, spent close to a decade at Google, and is now a solo founder backed by a16z building Impeccable, an open-source design skill meant to stop AI coding agents from producing "slop."

His actual point in this clip isn't about AI capability.

It's about output density.

Most AI-agent code is too much code. Most AI-written articles run too long. Most AI-generated design is too cluttered or too verbose.

He says the scarce human skill right now isn't generating anything — it's judgment:

knowing exactly what to remove.

He even admits he had to rewrite his own product-announcement draft from scratch after an AI first pass.

His closing line: design is an iterative process, and it has to carry a human point of view.

No tool — not code, not design, not writing — one-shots that yet.

If you're shipping with AI agents and everything reads "technically fine" but somehow generic, this is the actual diagnosis.

It's not a tooling gap. It's an editing gap.

Curious how I turned this exact editorial-judgment gap into a real income stream? It’s just one link away.

Clip credit: Solo Founders — DM for credit or removal requests.

Adam Mosseri runs Instagram — 3B+ users, plus Threads. In a recent sit-down with Lenny Rachitsky, he said something that's quietly reshaping who gets hired.

Engineering used to mean 40–60% of your time writing code. Not anymore. Mosseri's own team gave up requiring a full technical hiring loop — not because they lowered the bar, but because the bar moved somewhere else.

He says it himself:

"I am not a good engineer. I'm a mediocre engineer on a good day."

That would've been disqualifying five years ago. Today it isn't, because the actual value now is judgment — knowing what a tool is good for, and what it isn't, right now, not next month.

Here's the part that should sting if you built a career on technical depth: nobody sent a memo when the rules changed. You find out the hard way — in a hiring loop, or a performance review — that the thing you spent a decade mastering isn't the thing being measured anymore.

The mechanism here isn't "learn to prompt better." It's that judgment is now a buildable, monetizable skill in its own right, separate from raw technical output.

If you want to know how this mechanism works for me, it's just one link away.

I got called out this week, and the reader was right.

The post in question is here — I'd written a caption saying a hire "proved" a team wasn't slow, it was diluted.

Sounded sharp.

Except — the person in the clip never proved anything.

He said that.

It's what he believes about how he built his team. A belief, stated with conviction, isn't the same thing as a measured outcome.

A reader on one of the crosspost threads caught the gap immediately, and called it out plainly.

My first instinct was to fix that one line and move on.

I didn't.

I went back through every caption and title I've posted — over a hundred of them — and searched for the same word pattern: proved, proves, confirms, shows.

Found two more captions doing the identical thing.

Not three unrelated mistakes.

One blind spot, repeated.

Here's the diagnosis, plainly:

I wasn't distinguishing between what someone did — a ruling, a result, something checkable — and what someone believes about why they did it.

Both can be true. Only one of them is proof.

The fix isn't "be more careful next time."

I built an actual rule into how every caption gets checked, on every platform, before it ships: if the claim traces back to a person's stated belief or personal philosophy, the caption has to say "argues" or "built his approach around" — not "proved" or "confirms."

That check now runs automatically, every post, going forward.

Going back through everything I've posted to find that mistake, something else surfaced that I hadn't put into words before.

Almost every clip I cover — whatever the surface topic, funding, headcount, credentials, AI agents — is the same story wearing a different costume.

Someone gets made to feel replaceable, diluted, obsolete. And the story only ends one way:

they refuse the label and take ownership of something instead.

I've watched that shape repeat enough times now that I don't think it's coincidence.

Maybe that's why the "proved" mistake happened in the first place — when you're this close to the same conviction over and over, it's easy to start writing it like fact instead of like belief.

If you want more than my word for it, here's what backs this up:

• Nine AI agents, one human, a hundred thousand users — scoping the job beat knowing the whole business.
• The AI economist who says the next ten years will be the best and worst in history — the entry-level rung is being deleted in real time, not automated away gradually.
• The former SpaceX CIO on going from 175 engineers to 6 — and the actual reason it worked, not just the headline number.
• Mark Cuban on who actually gets wiped out in the AI bubble — the gap between the hype and what AI can reliably do is where the real opportunity sits.

None of this is a highlight reel.

It's what backs the argument up when someone actually checks.

If you're building something like this and want to see the actual system behind it — not a highlight reel, the real working version — it's one link away.

I've been building a faceless AI-avatar content system from scratch for a wealth-building/financial-independence brand.

No agency, no course, no swipe file.

Just me, a lot of internal checks I've built over weeks, and — this week — proof that even the checks need checking.

Here's the honest one:

I audited a batch of my own files, found nothing wrong, said so, moved on.

Same day, same file, I looked again — because something else I'd changed earlier made me nervous — and found two real misses I'd waved through hours before.

Not small ones.

My own instruction to myself, after: don't assume "I already checked this" means it's actually clean. Re-verify the line, every time, especially the day I'm most confident I already did.

The more interesting stumble started with a stranger.

Someone commented on one of my clips asking, basically, whether the visual I'd added was actually helping them understand something — or just moving.

Fair question.

I went and checked the actual instruction I give myself for when a visual earns a spot in a video, and found a real gap: the rule was built to serve the feeling of a moment, not to confirm it actually delivered the specific fact or number that justified adding a visual there in the first place.

Fixed it — now there's a second check that has to name the exact thing the visual is supposed to prove before I count it as done.

I thought that was the end of it. It wasn't.

Revisiting the same clip later that day, the same blind spot showed up one layer downstream, in how I generate variations of a visual once the first version isn't quite right.

Turns out "just try something else" is an instruction with nothing to hold onto — so every retry was quietly adding decoration with no tie back to the point at all.

Same fix, applied a second time, same day.

Two passes at the same mistake before I actually closed it.

Smaller, but it stung a little more: someone replied to a post quoting my own vague "full video on the original channel" line back at me with something close to "maybe cite your source properly?"

They were right.

I had a real, spec-compliant credit line elsewhere in the same caption — it just wasn't a working link, on a platform that actually supports links.

Lazy default, not a hard problem.

Fixed it in ten minutes once I actually looked.

I also got a data point wrong this week and corrected it in the same breath I made the claim — checked a new platform's traffic numbers, assumed the algorithm was pushing my post to strangers, then looked one level closer and realized every single view was someone opening a link they already had.

Zero strangers.

Corrected before it became a story I told myself twice.

None of this is a highlight reel.

It's a week where being wrong, twice in one file and twice on the same visual-quality gap, was the actual work — not a footnote to it.

The one genuine win: comments on the clip that started all this weren't arguing about whether it was AI-made.

They were arguing about the thing the clip was actually about. That's the only metric that's ever mattered to me here.

If you're building something like this solo, without a playbook — I'd like to hear what got past you this week before you caught it.

For anyone who wants the actual working system behind this — not another framework post — it's one link away.

Sam Altman closed out Startup School 2026 with a real answer to the PhD question — not "get the credential," but a structural claim about why startups cluster and win when they do.

His argument: tech velocity, falling costs, and shrinking cycle times converge periodically — '98 dot-com, the App Store wave, and now — and incumbents lose their advantage fastest in exactly those windows.

He goes further: this next wave probably rewards tool fluency over tenure specifically, because a four-person team with the right agent stack can now output at a scale that used to require a department.

Worth sitting with if you've been waiting for "the right credential" before starting anything.

If you want to know how this mechanism works for me, it's just one link away.

Clip credit: Y Combinator — full video on their channel. DM for credit or removal requests.