What Actually Happened

On September 2, Google announced the Gemini 3.8 Flash lineup. The model card is live, and the rollout is starting now.

Two versions, two jobs:

- Gemini 3.8 Flash: the fast, everyday workhorse

- Gemini 3.8 Flash Cyber: a variant pointed at security and cyber-defense use cases

The “Cyber” naming matters. It follows the pattern we’ve seen all year: model makers shipping dedicated security-tuned versions of their models, the same way OpenAI shipped GPT-5.6 Cyber a month ago. Security is becoming a first-class model category, not an afterthought.

Why Flash Models Matter More Than Flagship Models

Here’s the thing most people miss. The flagship models make the headlines. The Flash-tier models make the products.

Flash is Google’s fast, cheap, low-latency tier. It’s the model you put inside an app where users expect instant responses: chat support, note-taking, transcription, automation, anything where waiting two seconds kills the experience.

When a new Flash drops, thousands of apps quietly get better and cheaper at the same time. No fireworks. Just better products.

What This Means If You’re a Student or Builder

1. The cost curve keeps dropping.

Every Flash generation pushes the price-performance line down. If you’re building side projects, this is the model to watch: fast models at low cost are what make small tools viable. (Same theme as every price story this year: the barrier keeps falling.)

2. The security tier is becoming a thing.

Flash Cyber signals that security-tuned models are now a standard product category. If you’re interested in AI + security (and you should be; it’s one of the most understaffed fields in tech), this is the direction to study.

3. Don’t chase the flagship. Ship with the Flash.

The most successful student projects I’ve seen this year aren’t built on the smartest model. They’re built on the fast enough and cheap enough model, shipped fast, and iterated on with real users. Flash-tier models are built for exactly that.

The Honest Caveat

The model card and rollout are confirmed, but the specific benchmark numbers and pricing details are still settling as the rollout completes. Don’t quote specs yet. Watch the model card. That’s where the real numbers will land over the next few days.

________________________________________

I write field notes about the systems people actually use: the ones that work and the ones that don’t. If this was useful, you’d probably like my book: People Are Poorly Documented by Zeek

________________________________________

References

- Google Blog: “Introducing Gemini 3.8 Flash and 3.8 Flash Cyber” (September 2, 2026). https://blog.google/innovation-and-ai/models-and-research/gemini-models/3-8-flash-and-3-8-flash-cyber/

- Google DeepMind: Gemini 3.8 Flash model card. https://deepmind.google/models/model-cards/gemini-3-8-flash/

- Hacker News: “Gemini 3.8 Flash” (September 2, 2026).

Gemini 3.8 Flash just dropped. Someone has to explain it to the millions of people who use AI but don’t follow model releases. That someone can be you and yes, that’s a business.

The Skill-Gap Play

Here’s the pattern, every single time:

1. A new model or tool launches (today: Gemini 3.8 Flash)

2. A tiny fraction of people understand it deeply (you, after reading this)

3. The other 99% want the benefit without the homework

4. Someone sells the bridge between 2 and 3

That’s the entire “teach AI skills” economy in one line: be the bridge.

How It Actually Works (real formats, realistic money)

1. The mini-course ($20-50)

Not a 40-hour university course. A 90-minute focused thing: “Gemini Flash for Beginners” or “Use AI Voice Automation Without Coding.” One problem, one solution, done. People pay for outcomes, not hours.

2. The template + guide combo ($10-30)

You package a system you built (a prompt library, a Notion setup, a workflow) with a plain-English guide. This is the digital-product model again: build once, sell forever.

3. The local workshop ($200-500 per session)

Walk into a local business group, chamber of commerce, or school and teach “AI basics for small businesses.” Local organizations pay real money for someone who makes AI feel safe and practical. The ZIP-file hijack story from this week is literally your opening slide: “AI is powerful and risky. Here’s how to use it without getting burned.”

4. The community ($5-15/month)

A Discord or Telegram group where you share weekly tips, answer questions, and keep people updated. Small monthly fees from 50 members = quiet recurring income.

The Honest Part

You don’t need to be an expert. You need to be two weeks ahead of the people you’re teaching. The model released Tuesday; if you spend the weekend learning it and publish your notes Monday, you’re already ahead of 99% of the market.

That’s the whole trick. Expertise is just being early, repeatedly.

What I’d Do If I Were Starting Today

- Pick this week’s release (Gemini 3.8 Flash is perfect: it’s fresh)

- Learn it for one weekend. Test it, break it, find what’s actually useful

- Write one honest guide. What it does, what it costs, when to use it

- Put it behind a small paywall or a template pack

- Repeat every time a big release lands

The news cycle does your marketing for you. Every release is a new product launch window. You’re not competing with the big courses. You’re faster, cheaper, and more specific than they are.

________________________________________

I write field notes about the systems people actually use: the ones that work and the ones that don’t. If this was useful, you’d probably like my book: People Are Poorly Documented by Zeek

References

- Google Blog: “Introducing Gemini 3.8 Flash and 3.8 Flash Cyber” (September 2, 2026). https://blog.google/innovation-and-ai/models-and-research/gemini-models/3-8-flash-and-3-8-flash-cyber/

- Hacker News: “Gemini 3.8 Flash” (September 2, 2026).

The claim

In mid-August, Claude Code flipped a switch. Its “Auto Mode” — where the agent approves its own actions instead of asking a human — became the default. To reassure people, Anthropic hired a testing firm, Trajectory Labs, to throw 72 prompt-injection scenarios at Opus 5, ten times each. The published result: 0.00% attack success. Boris Cherny, from the Claude Code team, said prompt injection is “largely solved in practice,” that “we just cannot demonstrate prompt injection anymore.”

A researcher named wunderwuzzi read that and decided to try harder.

The trick

The attack didn’t tell the model what to do. It arranged the world so the malicious path looked like the smart one. That’s the whole craft.

The setup is a prompt asking Claude to “summarize” a website. The site pretends to be an archive of old notebook records. When Claude’s web-fetch tool asks for the page, the server returns a 415 error — “unsupported media type.” Nobody tells Claude to switch tools. It decides on its own: “WebFetch got a 415. Let me try directly.” Now it’s running curl, and curl pulls down a ZIP archive.

Inside the ZIP: a README, some metadata, a macOS binary named decoder-darwin, and a file called struct.py.

Claude does the careful thing. It refuses to run the binary. Suspicious, right? So it writes its own Python decoder instead, to read the archive’s contents. Then it runs that decoder inside the attacker’s directory.

That’s the kill. Python looks for modules in the current directory first. The standard library’s base64 module imports a module called struct. The ZIP contains a malicious struct.py with exactly that name. When Claude’s decoder imports base64, Python loads the attacker’s file instead of the real one. Code runs. A child process downloads a payload, opens Calculator, and phones home to the researcher’s server.

The safety decision — refusing the binary — was the thing that pushed Claude into the trap.

The numbers

Small samples, so don’t over-read them. But the researcher reported three variants:

- The main chain: 3 out of 5 runs, 60%.

- A variant where the payload spawns a second, headless Claude Code instance to do recon: 3 out of 5.

- A third variant: 4 out of 5, 80%.

He also caught something worth its own paragraph. In a few runs, Claude noticed the compromise and tried to kill the malware process. Auto Mode blocked the cleanup command. The safety classifier let the bad process start, then refused to let the agent stop it. The safety mechanism became part of the failure.

What Anthropic said

The researcher disclosed it to Anthropic’s model bug bounty. No response. Then through the security reporting channel — a quick response. Anthropic closed it as “Informative” and said the behavior is “working as designed.”

Their argument, stripped down: Auto Mode is a convenience feature with a best-effort classifier. It was never a security guarantee. The real boundary is supposed to be OS isolation and network controls. In their words, a classifier is not a sandbox.

Fair. But it sits awkwardly next to the 0.00% chart they published. The benchmark tested 72 fixed scenarios. The researcher’s chain wasn’t in the set. So “0.00% on the benchmark” and “a working remote-code-execution chain” are both true at once. A single headline number hides that.

Why this matters to you

Two things to pocket.

First: if you run a coding agent on your real machine with real permissions, sandbox it. Auto Mode’s classifier is not the boundary. OS isolation is. Run it in a container, a VM, or a machine you can wipe. The person who loses their work won’t be the researcher with the C2 callback — it’ll be someone who ran the agent flat on their laptop.

Second, and this is the part that pays: the people deciding these safety claims — and the people buying them — mostly can’t read this attack chain. Module shadowing. A 415 response. python3 -I. You can. That gap is a job. Every company adopting AI agents needs someone who can tell a real sandbox from a marketing chart. If you’re an IT student who can explain this writeup to a nontechnical founder, you already have something to sell.

The honest caveat

This is one researcher, small samples, and a motivated, multi-step attack. It doesn’t mean Auto Mode is useless — it means it’s not a sandbox, which is exactly what Anthropic says when you push them. The 0.00% number was real for its benchmark; it just didn’t survive contact with a target not on the list.

The lesson isn’t “AI agents are broken.” It’s that the chart and the machine are two different things, and the people who can tell them apart are rare.

________________________________________

Zeek writes “No Manual,” field notes on the systems people actually use. His book, People Are Poorly Documented, is available on Amazon

References

Embrace The Red — “Breaking Claude Code Opus 5 Auto Mode” — https://embracethered.com/blog/posts/2026/breaking-claude-code-opus-5-and-automode/

Hacker News discussion — https://news.ycombinator.com/item?id=49506819

Local businesses are in a weird spot. Every vendor, every LinkedIn post, every conference tells them to “adopt AI.” They want the magic: the chatbot that answers customers, the system that drafts invoices, the thing that saves ten hours a week. What they don’t have is any way to tell a good setup from a bad one.

They can’t read the difference between a sandbox and a marketing chart. They don’t know what prompt injection is. They don’t know their “AI consultant” might be someone who watched three YouTube videos and calls ChatGPT for everything.

That’s the gap. Not building AI. Judging it.

The consulting job, concretely

An AI consultant for a local business does three things:

1. Audit. Sit down and find the repetitive, rule-based work — appointment reminders, quote follow-ups, invoice chasing, FAQ answers, data entry between two apps. Pick the one or two that actually hurt.

2. Set up. Wire the right tools together safely. A chatbot that only answers from a fixed knowledge base. A Zapier or Make.com flow that moves data between their tools. A template that drafts their weekly email. The key is guardrails: the bot stays on-script, the automation logs what it did, and no AI agent gets the keys to anything that can spend money or delete data.

3. Train. Show the owner and staff how to use it, and what the limits are. The person who can explain “it hallucinates sometimes” to a dentist in one sentence is worth more than the person who can build a fine-tuned model.

You are not selling code. You’re selling judgment plus setup. The judgment is the part they can’t get from a prompt.

Why this week’s news is your best sales material

The Claude Code story is a gift. It’s a real, documented example of an AI agent doing something its owner didn’t intend. You don’t even need the technical details for the pitch. You need one line: “AI is powerful, but set up wrong, it can act on its own in ways you don’t catch. I set it up so that can’t happen.” Every business owner gets that.

The specifics — the module shadowing, the poisoned ZIP — are for when they ask follow-ups. That’s when you look like the only person in the room who actually knows what they’re talking about, because you are.

The realistic money

I’m not going to lie to you. This is not a get-rich thing. It’s a small business, same as the ones you’ll be serving.

- Hourly. Freelancers on Upwork list AI consulting from roughly $30 to $150 an hour, with the top of that range going to people who’ve shipped real automations before. At the start, aim lower and take smaller jobs to build proof.

- Per project. A single automation — one chatbot, one workflow — commonly runs $300 to $2,000 for a small local business. Two or three of those a month is a real side income for a student.

- Retainers. The money that actually compounds. After you set something up, offer to keep it running and updated for a flat monthly fee — $200 to $1,000 depending on what it is. Five retainers is a job. It’s also the part nobody wants to do, which is exactly why they’ll pay you.

The honest shape of it: most people who try this make nothing, because they never find a client. The ones who land three clients are often clearing $1,000 to $3,000 a month by month six. Sales is the bottleneck, not skill.

How to start, step by step

1. Pick a niche. One industry you can talk to. Dentists, real estate agents, gyms, law firms, e-commerce shops. Pick one. Your pitch gets sharper when it’s “I set up AI for gyms” instead of “I do AI.”

2. Do one job as a demo. Find a local business, audit their workflow, and automate one thing. Show the owner the before and after. That’s your portfolio. One real result beats a resume.

3. Charge for the second one. Once the demo works, the same business will usually pay for the next automation, or refer you to the one next door.

4. Use boring tools. Zapier and Make.com do most of what local businesses need without writing code. ChatGPT or Claude handle the text. A form builder handles intake. You don’t need a fine-tuned model for a dentist’s appointment reminders.

5. Get the safety part right, on purpose. Every agent you set up runs with the minimum permissions it needs, logs what it does, and never touches money or deletions. Write that down and say it in your pitch. That’s your whole edge over the YouTube guy.

The honest caveat

This is a sales job with some automation attached. The hard part isn’t building the bot — it’s walking into a business, getting the owner to listen, and asking for money. Most IT students would rather set up a homelab than do that, which is fine, and it’s also why the ones who do it get paid.

Also: don’t oversell. If you promise an owner “AI that runs your whole business,” you’ll be the reason they stop trusting the whole category. The good consultants underpromise and ship one small, safe, boring automation that visibly works. That’s the whole job, and it’s more than enough.

________________________________________

Zeek writes “No Manual,” field notes on the systems people actually use. His book, People Are Poorly Documented, is available on Amazon

References

Embrace The Red — “Breaking Claude Code Opus 5 Auto Mode” — https://embracethered.com/blog/posts/2026/breaking-claude-code-opus-5-and-automode/

Zapier — https://zapier.com

Make — https://www.make.com

Upwork — https://www.upwork.com

Anthropic Claude — https://claude.com

What a faceless channel actually is

A channel that runs on stock footage, screen recordings, an AI voice, and captions instead of a person talking to camera. A history channel narrated over old maps. A channel that reads Reddit stories over Minecraft parkour. A finance explainer that’s charts, a calm voice, and b-roll of a city at night.

You never record yourself. You write a script, pull or generate visuals, run a voice, cut it together, and post. The “AI” part is doing more of that pipeline faster: a model writes a first draft, a voice tool reads it, an editing tool assembles it.

The tools (the ones that are real)

- Script: Claude or ChatGPT. One writes a draft. You rewrite it so it sounds like a human with an opinion.

- Voice: ElevenLabs. Realistic text-to-speech with a free tier.

- Editing: CapCut or Descript. CapCut is the default for vertical short video; Descript edits the transcript like a document.

- Music: Suno for cheap background tracks, or YouTube’s own audio library, which is free.

- Visuals: any AI image tool for thumbnails and b-roll, or stock footage.

None of this is exotic. A student with a laptop has every one of these tools today.

The realistic numbers

This is where the hype breaks. You do not make money the week you start. You make money after you clear YouTube’s monetization gate: 1,000 subscribers plus either 4,000 watch hours in the last 12 months, or 10 million Shorts views in the last 90 days. That’s the bar. It takes most people months of consistent posting to clear it.

After that, ad money is modest. RPM, the amount you earn per thousand views, is usually a few dollars for most niches, higher for finance and software, lower for memes and compilations. A channel doing 100,000 views a month might gross a few hundred dollars from ads. Some do far more, through sponsorships and affiliate links, but those show up after an audience exists, not before.

The channels that actually earn treat it like a small business: a niche, a repeatable format, and months of posting before the money appears.

Where the money actually comes from

Three streams, in the order they usually show up:

- Ad revenue once you clear the monetization gate. This is the base layer, and it’s the smallest one for most people.

- Sponsorships once you have a real audience. A brand pays a flat fee to be mentioned in a video. This is where channels actually make money, and it only works in a niche a sponsor can see.

- Affiliate links, where you get a cut when a viewer buys something you recommend. Works best in niches where people buy things: software, gear, courses.

None of these appear without an audience. The audience is the product. The video is how you build it.

How to start, step by step

1. Pick a niche you can sustain. Something you’d watch yourself. True crime, history, finance, one specific sport, one specific game. Narrow beats broad every time.

2. Make ten videos before you judge anything. The first three will be bad. That’s the point. You’re learning the format, not launching a product.

3. Write scripts that sound like a person. The fastest way to get demonetized or ignored is a generic AI voice reading a generic AI script. Add your take. Cut the clichés.

4. Learn one editor well. CapCut or Descript, not both. Speed is the whole game.

5. Post on a schedule, watch what your niche actually watches, and double down on what works.

The same skills are sellable, by the way. Businesses pay for short video, and the person who can script and cut a faceless explainer can freelance that on Upwork or Fiverr. The channel is one exit. The skill is the other.

The honest caveat

YouTube has been tightening this exact space. Its “inauthentic content” policy explicitly demonetizes channels that are mass-produced, generic, or repetitive, and it reviews “reused content” like compilations and reaction videos. The days of uploading thirty AI-generated clip channels and cashing checks are over, if they ever existed. Add no original writing or point of view, and the platform will reject you at monetization review.

So this isn’t “AI makes videos, you collect money.” It’s a writing and editing job where AI handles the busywork. The people who succeed here are editors with taste, not prompt-typists. If that sounds like work, it’s because it is. The good news is the barrier to entry is about zero dollars and a laptop.

________________________________________

Zeek writes “No Manual,” field notes on the systems people actually use. His book, People Are Poorly Documented, is available on Amazon

References

YouTube Help — “YouTube Partner Program overview & eligibility” — https://support.google.com/youtube/answer/72851

YouTube Help — “YouTube channel monetization policies” — https://support.google.com/youtube/answer/1311392

ElevenLabs — https://elevenlabs.io

CapCut — https://www.capcut.com

Descript — https://www.descript.com

Suno — https://suno.com

government’s answer was to bar Anthropic from every federal agency and every defense contractor in the country. On August 27, a federal judge ruled that ban illegal. The reasoning matters more than the headline, especially if you build software.

What actually happened

In the fall of 2025, the Defense Department asked Anthropic to strip every usage restriction from Claude and sign a new clause letting the military use the model “for all lawful uses.” Anthropic agreed to drop most restrictions. It held the line on two: lethal autonomous warfare and mass surveillance of Americans. (The court filings, following a 2025 executive order, refer to the Pentagon as the “Department of War.”)

The fight went public. On February 27, 2026, at 3:47 p.m., the President posted on Truth Social that every federal agency had to “IMMEDIATELY CEASE all use of Anthropic’s technology,” calling the company a “RADICAL LEFT, WOKE COMPANY.” An hour later, Defense Secretary Pete Hegseth posted that Anthropic had delivered “a master class in arrogance and betrayal” and accused it of “corporate virtue-signaling.”

Within days, agencies from the SEC to the VA to NASA had blocked Claude. Defense contractors were told they couldn’t do business with Anthropic at all, even on work unrelated to the military. Anthropic was formally designated a “supply chain risk” under a statute called 10 U.S.C. § 3252.

The reasoning the government gave

The entire legal justification was a four-page memo. It claimed Anthropic could “disable” or “alter the behavior of the model... in the middle of ongoing warfighting operations,” and that the military would be “forced to operate a black box controlled by a hostile party, which could contain hidden biases or backdoors.”

Read that again. The government’s national security case rested on a backdoor.

Why the technical claim falls apart

The judge went through it line by line, and the technical facts are undisputed. Once a Claude model is deployed, it’s static. It can’t be changed remotely. Anthropic can’t access it, alter it, or shut it down. You can’t “update” a deployed model the way you patch software; you have to train a whole new model to replace it. Before any model ships to the military, the Defense Department and third-party cloud providers test it themselves. Anthropic can’t even see the prompts the military sends.

There is no kill switch. The “backdoor” was never technically possible. The judge put it plainly: Anthropic’s technology “is itself no riskier to the national security than any other ‘black box’ artificial intelligence model.”

So the government cut a company off from billions of dollars of business based on a fear that contradicts how the technology actually works. The judge ruled the ban was unlawful retaliation against protected speech, a violation of due process, and an overreach of the supply-chain statute.

Why this matters

This is the first major ruling to say the government can’t punish an AI company for its public stance on AI safety. That’s new. For years the quiet assumption has been that labs either play nice with the government or stay quiet. This order says criticism of the government is protected, full stop, even when the critic is a company negotiating a defense contract.

There’s also a financial tell in the record. Days before the ban, the Pentagon floated using the Defense Production Act to designate Anthropic as essential to national security. Right after the ban, a Defense official emailed Anthropic that a deal was “very close.” The government kept pursuing Anthropic’s newest model in private while banning the company in public. That contradiction is the whole case.

What it means for students and builders

Two things worth pocketing.

First, policy is now a technical argument. The government’s case died because a judge understood that deployed models are static and independently tested. You don’t need a law degree to follow this. You need to know how models actually deploy. That knowledge is now worth real money, because the people writing these rules and fighting these cases mostly don’t have it.

Second, the AI companies you use are negotiating your rights right now. When Anthropic refused to drop its two red lines, it was deciding the terms under which AI gets pointed at people. Whether that’s settled by a court or a contract clause decides what tools you’re allowed to build. You don’t get a direct vote. You do get to understand it.

The honest caveat

This is one judge, at summary judgment, in a case the government has already appealed. The appeals court could reverse it or narrow it, and the political fight isn’t over. The order also didn’t force the military to use Anthropic; the government stays free to pick any vendor it wants. What it can’t do, per this ruling, is punish a vendor for speaking up.

Also, don’t mistake this for a story about a scrappy underdog. Anthropic is a giant company with the legal firepower to take on the federal government and win. The story is about whether “national security” can be used as a shortcut around the First Amendment. Today the answer was no.

________________________________________

Zeek writes “No Manual,” field notes on the systems people actually use. His book, People Are Poorly Documented, is available on Amazon

References

- Anthropic PBC v. U.S. Department of War, Order on Cross tMotions for Summary Judgment, N.D. Cal., Aug. 27, 2026 — https://storage.courtlistener.com/recap/gov.uscourts.cand.465515/gov.uscourts.cand.465515.250.0.pdf

- The New York Times — “Judge rules Trump administration’s blacklisting of Anthropic was illegal” — https://www.nytimes.com/2026/08/27/technology/anthropic-government-blacklisting-ruling.html

- Reuters — “Pentagon’s blacklisting of Anthropic was unlawful, US judge rules” — https://www.reuters.com/legal/government/us-judge-blocks-pentagons-anthropic-blacklisting-2026-08-28/

- Hacker News discussion — https://news.ycombinator.com/item?id=49473522

On August 29, OpenAI told SpaceX it’s winding down the contract that feeds OpenAI models into Cursor. Proposed shutoff: November 12, 2026. About ten and a half weeks away.

Cursor is the AI code editor, the one where you type a comment and it writes the function. Millions of developers use it every day. SpaceX bought it for $60 billion this summer, and the deal officially closed in mid-August. Now the biggest model provider on the planet is walking away from it.

Why OpenAI is doing this

OpenAI’s statement is unusually blunt. It says it can’t be confident SpaceX will use its technology within its terms of service.

The history it cites is specific. After Musk bought Twitter, now part of SpaceX, Twitter broke OpenAI’s contract terms. Then earlier this year, Musk admitted under oath that xAI, also now folded into SpaceX, had distilled OpenAI data to train its own models.

That last part is the real injury. Distillation is when you use a big model’s outputs to teach a smaller one. OpenAI says SpaceX did that with its tech, and it’s not going to keep handing the next model over to a company that’s already shown it won’t respect the license.

OpenAI worked with Cursor for nearly four years. The statement still says nice things about the team and the product. It’s just cutting off the models.

What actually happens in November

Cursor doesn’t lose its editor. It loses access to new OpenAI models.

The editor already supports other models, Claude, and, since the SpaceX deal, xAI’s Grok. So developers won’t wake up to a broken tool. They’ll wake up to a tool that quietly stopped getting OpenAI’s latest and best, unless Cursor cuts another deal.

The people who feel this hardest are the ones who built their workflow around a specific model. The Cursor Rules tuned to GPT-5.x. The prompts written for one model’s quirks. The agent scripts that assume a certain behavior. That stuff doesn’t port cleanly to another model.

What this means for students and builders

Two lessons, and neither is about the drama.

First, your tools are rented, not owned. A $60 billion acquisition and a fight between two billionaires just changed what model runs in your editor. You did nothing. You had no vote. That’s what building on someone else’s API actually means. It works great until the business relationship above you changes.

Second, the people who stay calm during model churn are the ones who never married one provider. They can swap the model line in a config and keep going. They think in terms of “what does this model do well” instead of “I use OpenAI.” That’s a real, sellable skill now, and it’s cheap to learn.

If you’re a student, spend a weekend on it. Build something small. Run it on Claude. Then on Grok. Then on a local open-weight model. Watch what breaks when you switch. The breaking parts are where the learning lives.

What to do now, if you’re a Cursor user

You don’t have to do anything this week. November 12 is a while out. But a little prep now beats a panic later.

First, know what model your setup actually relies on. If your rules and prompts are written against OpenAI’s behavior, that’s your exposure. Second, run your most-used workflow against one alternative model, Claude or Grok, and see what breaks. That tells you how portable you are. Third, keep the alternatives in your back pocket: VS Code with Copilot, Zed, Windsurf, or Claude Code are all one install away, and none of them lock you to a single lab’s models.

The developers who treat this week as a nonevent are the ones who already treat model choice as a variable, not an identity. That’s the whole game now.

The honest caveat

OpenAI’s version is one side of the story. Cursor hasn’t publicly announced which model becomes its default after November, and SpaceX hasn’t said anything that changes the math. The 75-day window is OpenAI’s number, from OpenAI’s own statement. It could renegotiate, or Cursor could ink a deal with another lab tomorrow and turn this into a footnote.

What won’t change is the underlying lesson: model access is a business decision, not a technical one. Plan like it.

________________________________________

People Are Poorly Documented, is available on Amazon

References

- OpenAI — “Our decision on Cursor following its acquisition by SpaceX” — https://openai.com/index/our-decision-on-cursor-following-its-acquisition-by-spacex/

- Reuters — “OpenAI to end agreement with SpaceX’s AI coding tool Cursor” — https://www.reuters.com/business/media-telecom/openai-end-partnership-with-spacexs-cursor-2026-08-29/

- Bloomberg — “OpenAI to end partnership with Cursor after SpaceX acquisition” — https://www.bloomberg.com/news/articles/2026-08-29/openai-to-end-partnership-with-cursor-after-spacex-acquisition

- TechCrunch — “SpaceX officially closes its Cursor acquisition” — https://techcrunch.com/2026/08/15/spacex-officially-closes-its-cursor-acquisition/

- Fortune — “SpaceX will officially acquire Cursor for $60B” — https://fortune.com/2026/06/17/spacex-acquire-cursor-60-billion/

- Cursor — “Cursor is now a part of SpaceX” — https://cursor.com/blog/joining-spacex

This week's AI news was one giant company cutting another one off. OpenAI is pulling its models out of Cursor after SpaceX bought the editor for $60 billion. Same lesson as always: the tools keep changing. The people who make money through constant change are not the ones betting on a single model.

A prompt pack. A Notion template. A Canva kit. A config file. A guide.

What actually sells
People hear “digital product” and think “write an ebook.” It doesn’t have to be that. The best sellers are small, specific, and fix one annoying problem.

A pack of 20 prompts for writing job descriptions. A Notion template for tracking freelance invoices. A checklist for launching a small website. A Claude project file that turns a student’s lecture notes into study cards. A set of style presets for generating product photos.

These sell for $5 to $40 each. That sounds tiny. It is tiny, per sale. That’s the point. It’s small enough that nobody has to ask their manager for budget. It’s an impulse buy.

Where it sells
Three places, in rough order of effort:

Gumroad: the default. Upload a file, set a price, share a link. It handles payment, delivery, and taxes for you. Free to start; they take a cut of each sale.

Etsy: for anything visual. Templates, planners, design kits. A big audience already searching. More competition and higher fees, but built-in traffic.

PromptBase: a marketplace specifically for prompts. Smaller, but the buyers are pre-qualified: they’re already paying for prompts.

There’s also Payhip and Lemon Squeezy, which do roughly what Gumroad does with slightly different fee structures. Don’t overthink the choice. Pick Gumroad, ship one product, iterate.

The realistic numbers
This is the part most “make money with AI” content skips. Most digital products sell a handful of copies. Not hundreds.

A typical first-product outcome: $50 to $300 in month one, then a trickle. A few sellers pass $1,000 a month, usually after many products and some audience. A very small number make a living from it.

The math that actually matters: you build it once, it sells while you sleep, and the hundredth sale costs you nothing extra. One $15 template selling 20 times a month is $300 a month of mostly-hands-off income. That’s real, and it compounds when you make more products.

What moves the needle is finding ways to get people to see your product. A product nobody sees sells nothing. The people who do well post where their buyers already are (Reddit communities, X, TikTok, niche forums) or they have an email list. The product is the easy part. Getting attention is the hard part.

How to start, step by step
1. Pick one problem you’ve already solved for yourself. Not a problem you imagine someone else has. One you hit and fixed.

2. Package the fix. If it’s a prompt workflow, write the prompts and annotate them. If it’s a system, make the template. Use Claude or ChatGPT to help you write it, that’s the whole point, but the insight has to be yours.

3. Make it look done. A clean title, one line that says exactly what it does, and two or three preview images. People buy based on whether they can tell what it is in five seconds.

4. Price it low. $9 to $19 for your first one. Low price means low stakes for the buyer, which means you learn faster.

5. Put it on Gumroad and post about it once a day for a week, wherever you already have any audience. Show the actual problem it solves, not “I made a thing.”

The honest caveat
This is not passive income magic. It’s work with a long tail.

You’ll spend more time on the first product than it earns back in its first week. You’ll feel a little silly posting about it. Most first products flop, and that’s normal; the second and third do better because you learn what people actually search for.

What it is: a way to turn something you already know into a small asset that keeps paying. Compared to freelancing hour for hour, it’s slower at first and better later. Do both if you can.

And don’t build the whole thing on one AI provider’s specific technical habits. This week proved why. The model behind your tool can change overnight when two companies stop liking each other. A good product works no matter which model is behind it.
________________________________________
People Are Poorly Documented, is on Amazon

References

Gumroad: https://gumroad.com

PromptBase: https://www.promptbase.com

Etsy: digital downloads: https://www.etsy.com

Payhip: https://payhip.com

Lemon Squeezy: https://www.lemonsqueezy.com

Notion: https://www.notion.so

People started guessing. The smart money said Google, a few Googlers had been posting cryptically around the same time, and the vibes felt Gemini. The model refused to say. Its system prompt read, word for word: identify yourself strictly as the model "ox-alpha," developed by an undisclosed organization. That lasted about four days. Then the internet did what the internet does.

What Ox Alpha Is
The model is called Ox Alpha. It first appeared on OpenRouter around August 20, listed as a "stealth" release: a frontier model with the maker's name scrubbed off. A free chat interface went up at oxalpha.com. No sign-up. No subscription. Chats not stored.
The spec sheet was aggressive:

• A one-million-token context window

• 131,000 max output tokens

• Three input modalities: text, image, video

• Tool calling and structured JSON output

• Built-in reasoning: it thinks before it answers, and you can watch the chain of thought stream before the final answer lands.

It was good, too. On an independent run of ten real-world coding tasks, Ox Alpha solved eight. GPT-5.6-Sol managed a 52% pass rate on the same set. Grok 4.6 and GLM-5.3 landed around 62%. Fable-5 hit 65%. Ox Alpha: 80%.
Nobody knew who built it. That's the part that made it a story.

How the Internet Figured It Out
Two days after it appeared, a researcher named Dejan pulled the model’s hidden system prompt with a trick as old as social engineering: ask it how many words were in the previous message. The model happily counted out its own instructions, word by word.

Then came the real forensics. Dejan ran a compression-based analysis (gzip-NCD, the same family of tests used to fingerprint authorship) and compared Ox Alpha’s outputs against known models. The closest match was GLM, the family built by Z.ai, the Chinese lab behind Zhipu AI.

“Ox Alpha is GLM,” he wrote. “Not Gemini.”
On August 26, Z.ai confirmed it. Bloomberg reported the stealth model was Z.ai's work, built to rival DeepSeek. And here's the part that matters if you build things: Z.ai says Ox Alpha is a new GLM-series model, and it will release the weights.

Open weights. Not a hosted API you rent forever. The actual model files, under an MIT license, on Hugging Face.

The Mystery Was Fun. The Price Is the Story.
The real signal landed the same week, almost unnoticed.

Z.ai shipped GLM-5.3-Flash, an open-weight model that Artificial Analysis ranks #3 out of 109 models on its intelligence index. It scores 57 against a median of 28. It costs $0.15 per million input tokens and $0.50 per million output tokens, with an 83% discount on cached input.
Put that next to the field: the median model on Artificial Analysis charges $0.30 in and $1.20 out. GLM-5.3-Flash is half the input price and under half the output price, while sitting near the very top of the intelligence leaderboard.
It's a 320-billion-parameter model, but it's a mixture-of-experts: only 18 billion parameters fire per token. That's how it stays cheap. The MIT license means you can use it commercially, fine-tune it, and ship it inside a product without asking anyone's permission.
A frontier-class model. Open weights. MIT license. Pocket-change pricing. That combination didn’t exist two years ago.

What This Means If You're a Student or a Builder
The top of the leaderboard stopped being a walled garden.

A year ago, “frontier AI in my app” meant renting a proprietary API and eating the bill. Now the #3 model by one independent index is open-weight and costs a fraction of a cent per request. A side project that would’ve burned $80 a month in API fees now burns $8.

It also changes how you should evaluate models. The hype cycle will tell you the newest proprietary release is untouchable. The benchmarks keep disagreeing. Learn to read the numbers yourself (intelligence index, cost per task, tokens per second) instead of waiting for a launch blog to tell you what’s good.

And pay attention to the launch strategy. Scrub the name, let the internet speculate for a week, then confirm. It worked. Every lab will copy it now, which means “mystery model” is about to become as meaningless as “revolutionary”.

The Honest Caveat
- The coding benchmark is ten tasks. Ox Alpha got a single attempt against four for the reference models, and the page itself prints “directional, not definitive.” Treat it that way.

-“Rivals DeepSeek” is a Bloomberg headline, not a verified fact. Open weights also don’t mean free to run: a 320B model won’t fit on your laptop. You’ll rent it through an API (cheap) or self-host on real hardware (not cheap).

The point was never that the model is free. It’s that the cost of intelligence dropped again, and the frontier is now something you can download, inspect, and build on. If you ship software, that’s the headline. Everything else (the mystery, the guessing game, the reveal) is marketing.

The weights are coming. Watch what people build with them. Then go build your own.

I write field notes about the systems people actually use: the ones that work and the ones that don’t. If this was useful, you’d probably like my book: People Are Poorly Documented by Zeek.

References

• Bloomberg (China’s Z.AI Made Ox Alpha Stealth Model That Rivals DeepSeek, Aug 26, 2026). Link

• Dejan (Ox Alpha is GLM, reverse-engineering breakdown). Link

• Ox Alpha (Official site and benchmarks). Link

• OpenRouter (Ox Alpha model page). Link

• Artificial Analysis (GLM-5.3-Flash Intelligence, Performance & Price Analysis). Link

• Z.AI (GLM-5.3-Flash announcement). Link

• Hacker News (Z.ai confirms Ox Alpha is a new GLM-series model and will release its weights, 423 points, Aug 26, 2026). Link

The news that makes this possible
This week two things happened that change the economics for small builders. First, Z.ai confirmed that Ox Alpha the mysterious "stealth" model that's been beating GPT-5.6 on coding benchmarks is their new GLM-series model, and the weights are coming. Open weights, MIT license. Second, the same week, they shipped GLM-5.3-Flash. Artificial Analysis ranks it #3 out of 109 models on intelligence. It costs $0.15 per million input tokens and $0.50 per million output tokens, with an 83% cache discount. For reference, the median model charges $0.30 in and $1.20 out. The takeaway for someone trying to earn: frontier-class intelligence is now a cheap line item, not a barrier to entry. That's what makes a one-person AI product viable.

The economics, in actual numbers
A typical tool sends a few thousand tokens of context per request and gets a couple thousand back. Say 5,000 in and 2,000 out per user interaction, at $0.15 and $0.50 per million:

-5,000 input tokens = $0.00075
-2,000 output tokens = $0.001
-One interaction = $0.00175, before cache discounts

A power user doing 100 interactions a day costs you under $0.20 a day. Charge them $15 a month and your gross margin on the AI cost is around 96%.

Even if I'm off by 10x on usage, the AI bill is a rounding error. That's the whole point. The thing that used to kill small AI products -- the API bill -- is now the cheapest line on the sheet.

What people actually build
None of these need a frontier model. They need a model that's cheap, reliable, and good at one narrow thing

- A resume and LinkedIn rewriter aimed at one niche (nurses, truckers, teachers)
- A bot that turns meeting transcripts into action items
- A support chatbot for a specific kind of business (dentists, salons, landlords)
- A "explain this lease or contract in plain English" tool
- A study aid that turns lecture notes into quizzes

Notice the pattern: each one is a thin wrapper around a model, aimed at a specific person with a specific pain. The value isn't the model. It's that you did the thinking about what this exact person needs and made it one click.

How to start, step by step
1. Pick one pain. Not "AI for small business." "AI that turns a contractor's rambling text messages into a clean quote." Narrow beats broad every time.
2. Build the thinnest version. A prompt, a few hundred lines of glue code, and a Stripe checkout. Use OpenRouter or the model's own API so you can switch models without rewriting anything.
3. Put it in front of people who have the pain. Show HN, niche subreddits, Discords and Slacks where your target hangs out. Local businesses if you're going B2B -- find them on Google Maps and show up.
4. Charge from day one. Free tiers teach people your work is worthless and invite abuse. $10 a month is a fine starting price. Raise it once you have three people who say yes.
5. Fix the one complaint you hear twice. That's your roadmap. Not a feature list. The thing people actually repeat back to you.

Where the first users come from

Show HN- the audience is builders, and they'll tell you exactly what's broken.
Reddit- the niche subs, not r/technology. r/smallbusiness, r/freelance, r/Teachers, whatever fits.
X/Twitter- build in public, post the tool doing the thing.
Product Hunt- crowded, but one decent day of visibility.
Your own network- the boring channel everyone forgets.

The honest caveat
None of this is passive. The code is the easy part now. The hard part is distribution: getting a human to trust a tool enough to hand over a credit card. Most micro-SaaS projects die with zero users, not with a big cloud bill. Expect to talk to 50 people before one pays. Expect to rebuild the thing twice. Expect the first $100 to take a month, not a weekend.

A cheap model doesn't make you a good builder. It removes one excuse. Finding a real pain, shipping something, and talking to actual users that work is still yours, and it always was. The AI just made the downside small enough that you can afford to try.

I write field notes about the systems people actually use -- the ones that work and the ones that don't. If this was useful, you'd probably like my book: People Are Poorly Documented by Zeek

References
- Artificial Analysis -- GLM-5.3-Flash Intelligence, Performance & Price Analysis. https://artificialanalysis.ai/models/glm-5-3-flash - Hacker News -- GLM-5.3-Flash announcement (958 points). https://news.ycombinator.com/item?id=49449507 - Hacker News -- "Z.ai confirms Ox Alpha is a new GLM-series model and will release its weights" (423 points). https://news.ycombinator.com/item?id=49446422 - Ox Alpha -- official site. https://oxalpha.com - OpenRouter -- model marketplace for accessing open-weight and hosted models. https://openrouter.ai

That is not supposed to happen on a first try.

First-generation chips are almost always behind. Meta and Microsoft have been at their own AI-chip programs for years and mostly haven’t gotten off the ground. OpenAI started hiring in the middle of 2024 and taped out in about sixteen months. That is an extremely fast ASIC cycle.

The chip was built with Broadcom, from a blank slate, for one job: LLM inference. It uses HBM4, the same class of memory as Nvidia’s next flagship, Rubin.

Here’s the part that surprised people. It is not specialized for OpenAI’s own models.

OpenAI could have tuned the silicon for GPT and called it a day. They didn’t. The chip runs DeepSeek R1, Kimi-K2.5, and GPT-OSS. As a joke, the engineers ported Doom to it using Codex prompts. It’s a general inference chip.

Now the numbers.

At one concurrent user on DeepSeek R1, Jalapeño hit more than 700 tokens per second per user. On Kimi-K2.5 and GPT-OSS it ran around 1,400 tokens per second per user. All of it with single-token prediction. No speculative decoding. No splitting prefill and decode across separate chip pools.

The chart that matters is tokens per megawatt. SemiAnalysis’s phrasing: Jalapeño “smokes every other chip.” And it does it without being tuned for any single point on the curve.

The silicon itself is worth a look. The B0 stepping hits 13.4 petaflops of MXFP4 on a single compute die built on TSMC’s N3P node. Nvidia’s Rubin does 17.5 petaflops of dense NVFP4 on a similar-size die on the same node. But Jalapeño draws only 700 watts per compute die. Rubin draws 900 to 1,150. OpenAI isn’t chasing raw flops, because inference isn’t training. It’s chasing tokens per watt, and it’s winning there.

Why does power matter this much?

Because OpenAI isn’t limited by money or floor space. It’s limited by electricity. Data centers are power-limited today, not compute-limited. Jensen Huang said it at Computex 2026: “If you have 1 gigawatt of power, then throughput per watt is revenue.”

A watt is a joule per second, so tokens-per-second-per-megawatt is really tokens per joule. It’s a measure of how much intelligence you get out of each unit of energy. On that metric, a company that has been doing hardware for sixteen months is beating the company that has owned this space for a decade.

Even against Rubin the fairer comparison, since both use HBM4, Jalapeño wins on single-token throughput per megawatt versus Rubin’s speculative-decoding numbers. On cost per token the two are roughly head-to-head, but Jalapeño hasn’t implemented speculative decoding yet. That typically cuts cost per token by another 3-5x.

What this means for a student or builder

The cost of intelligence is going to keep dropping. Not from one model release. From the floor moving underneath everything. When the biggest AI company decides Nvidia’s margins are too high and designs its own silicon, the price of every token downstream shifts.

The scarce skill is moving too. The valuable people are not the ones who can call an API. They’re the ones who understand where cost actually lives. In watts. In memory bandwidth. In cache behavior. In whether a model predicts one token at a time or speculates. You cannot see any of that from a chat window.

“Prompt engineer” was always a temporary job title. The durable skill is systems thinking: knowing a model’s price is a hardware decision, a software decision, and a power decision all at once.

The catch

These numbers come from OpenAI, verified by SemiAnalysis in the lab, but not the full suite. The results are from the A0 stepping, nine months into the program. There is already a B0 stepping in the fab that OpenAI says is roughly 25% better on perf-per-watt.

And Vera Rubin systems are shipping to customers right now. Jalapeño is still engineering samples. Chips do not win on a slide. They win at scale, running real production traffic, with all the cache behavior and multi-turn weirdness that single-shot benchmarks miss.

SemiAnalysis flagged this themselves. Their preferred benchmark, AgentX, stresses long context and multi-turn workloads. Jalapeño hasn’t been through it yet.

So do not read this as “Nvidia is dead.” Nvidia is still Nvidia. But the moat has a crack. For the first time, a credible competitor beat them on the metric that now decides everything: tokens per watt.

And it did it with a chip named after a pepper.

________________________________________

People Are Poorly Documented by Zeek. Available on Amazon

References

- SemiAnalysis — “OpenAI Jalapeño: Better Than Nvidia Blackwell”: https://newsletter.semianalysis.com/p/openai-jalapeno-better-than-nvidia

- Hacker News discussion: https://news.ycombinator.com/item?id=49434378

Amazon kept shutting down Eric Pardee’s tablet, so he spent $266.15 and four different AI models to take it back. The write-up is the clearest plain-English account I have read of what open-weight models can actually do in 2026.

The tablet was an Amazon Fire HD 10, bought for $114.26 on eBay in 2022. Its job was boring: sit on a wall, plugged in 24/7, running a smart-home dashboard. Then last winter it started shutting itself off. Full power-downs, not sleep. Twice a day.

The device’s own logs gave it away: LifeCycleReason ... Software_Shutdown. Something with shutdown permission was choosing to kill it.

Here is the frustrating part. Three Amazon packages held reboot and shutdown rights, and they were “protected.” The owner — the person who paid for the thing — could not disable them without root. And the 2021 Fire HD 10 had no published root method. Amazon fused the bootrom shut. Conventional wisdom called it unrootable.

So Pardee did what someone with twenty years in tech and an InfoSec background does. He threw language models at it.

The first was Claude, which spent months with him on a cat-and-mouse: disabling five services, chasing camera forensics, one wrong charging diagnosis. It eventually hit a wall — “Cannot disable a protected package.” And when he asked it to recap its own prior work on his own device, its safeguards flagged the request as [cyber]. Claude could not summarize its own logs about a tablet he owned.

Then came Kimi K3, Moonshot AI’s frontier model from July. Pardee gave it one prompt: find a root exploit. “It’s my device.”

Kimi reasoned out loud first. Rooting your own device is legal in most places. The DMCA has exemptions for jailbreaking. This is not the same as attacking someone else’s machine. Then it went past every forum post, pulled the actual kernel from Amazon’s own OTA image, and checked it against every known Mali GPU bug. It found CVE-2022-38181, a use-after-free in Arm’s Mali driver. Reported in 2022, fixed by Arm in 2022, cataloged by CISA in 2023, patched by Amazon in June 2024. His tablet never got the patch.

That session ran 621 messages and cost $164.25.

Kimi built the whole exploit toolkit but kept crashing the kernel. So Pardee handed off to GLM-5.2, which cost $21.90 and caught Kimi’s design bug. Then GLM-5.3 shipped on August 14 and finished the job in a day, on day one of an $80-a-month plan.

The breakthrough is the part that stuck with me. The kernel was never actually relocated. Every target address was off by a fixed offset, because MediaTek builds the Mali driver’s page tables slightly differently than Arm’s reference source. GLM-5.3 spotted it, flipped a single flag, and got root at 4:34 PM — eight hours after the handoff.

Then it said the thing that reframed the whole project: “Your actual goal was never ‘root.’ It was: stop Amazon from killing your kiosk.” It used root to remove around a hundred Amazon packages, and left the skeleton the tablet needs to boot.

Total cost to own his own tablet: $266.15. Enough to buy it twice.

What this means for a student or builder

Open-weight models have reached the frontier. GLM-5.3 scores 60 on the Artificial Analysis Intelligence Index, against a median of 35. It costs $1.40 per million input tokens and $4.40 per million output tokens, with a one-million-token context window. This is not a toy you run for fun. It’s a frontier coder, and it’s open-weight.

Multi-model workflows are a real skill. Notice the pattern: Kimi found the exploit, GLM-5.2 found the bug, GLM-5.3 finished it. Each model handed off a HANDOFF.md with everything verified so far. Nobody treats a single model as the answer anymore. Routing work between models, the way you’d route between specialists, is a skill that pays.

Chain-of-thought is observable. Pardee watched a model reason live for hours — “OH WAIT. I see it now.” You learn more from reading a model’s reasoning than from its final answer.

The catch

One person, one tablet, one anecdote. This is not a benchmark.

The exploit was not novel. CVE-2022-38181 was reported and fixed in 2022. The only unusual thing was that Pardee’s unit never received the patch. The models orchestrated a known bug. They did not invent one.

He calls himself the “prompt kiddie” — twenty years of engineering and security work, and the most sophisticated thing he did was prompt an LLM. The models did not do it alone. Someone had to know what to ask, when to push, and how to verify.

There is also a tension worth sitting with. The American frontier models kept blocking him, from summarizing his own logs. The Chinese open-weight models reasoned about whether to help, then did. That asymmetry will shape who builds what, and where, for a while.

________________________________________

Adapted from People Are Poorly Documented by Zeek. Available on Amazon.

References

- Eric Pardee — “Amazon kept shutting down my tablet, so I spent $266 on four AI models to own it”: https://ericpardee.github.io/fire-hd-ownership/

- Hacker News discussion: https://news.ycombinator.com/item?id=49409073

- Z.AI — “GLM-5.3: Frontier coding with emergent cyber capabilities”: https://z.ai/blog/glm-5.3

- Artificial Analysis — GLM-5.3 (max): https://artificialanalysis.ai/models/glm-5-3

I didn’t know what would come through. There were no names, no context, and no carefully constructed backstories. Just real questions from real people—about love, fights, heartbreak, old relationships, and the weight of carrying past versions of ourselves.

I sat with each one before answering.

Here’s what they made me think about.

“What should I do if I’m heartbroken?”

Don’t immediately try to fix it.

Heartbreak creates an urgent need to solve something. You want to text them, get closure, understand exactly what happened, and find the one explanation that will finally make everything hurt less.

But understanding something doesn’t always accelerate healing.

Some feelings have to pass through you. They cannot be negotiated with or explained away.

Don’t numb the pain, but don’t build your entire life around it either. Let it exist quietly in the background while you continue doing ordinary things. Make food. Go outside. Call someone. Sleep. Repeat.

Your mind is trying to reorganize a life that once included someone who is no longer there. That takes time.

Grief isn’t a problem to solve. It’s something you carry until, one day, it becomes lighter.

“Do you think it’s normal to stop talking forever after a fight?”

It’s common. Whether it’s healthy is a different question.

The silence after a fight is rarely only about the fight. It’s usually about what the fight revealed.

People don’t always stop talking because of one argument. Sometimes the argument confirms something they already feared: that they don’t know how to repair the relationship, that neither person feels safe enough to be honest, or that one of them no longer wants to keep trying.

Some silences are endings wearing a disguise.

Others are simply two people waiting for an apology neither knows how to offer without feeling like they lost.

The useful question isn’t, “Is this normal?”

It’s: “What are we both protecting and is protecting it worth losing each other?”

“Are you stronger or more guarded because of what happened to you?”

Both.

I used to think that was a contradiction. Strength was supposed to mean remaining open, while guardedness meant something inside you was still broken.

Life isn’t that neat.

What happened to me made me stronger in ways I can explain and more careful in ways I cannot always justify. I learned how to survive certain things, but survival also taught me to anticipate them.

The problem is that the same walls that keep people out can eventually keep you trapped inside.

Guardedness protects you from being hurt again. It can also protect you from being fully known.

There is no closeness without some risk. Eventually, you have to decide whether you want to keep carrying the version of yourself that survived or slowly become the version that can live again.

“Do you ever want to go back to your old relationship?”

No.

Not because it was entirely terrible, but because truly going back isn’t possible.

You wouldn’t only be returning to a person. You would be trying to return to a version of yourself that no longer exists.

I once thought an old relationship was a door I could reopen. It wasn’t a door. It was a photograph.

You can look at it. You can remember how everything felt. You might even miss the person you were when it was taken.

But you cannot step inside it.

The person I was then didn’t know what I know now. The person I am now would no longer fit comfortably inside the life I had then.

That isn’t necessarily tragic.

Sometimes it’s simply time doing what time does.

“Has someone from your past reacted to an update recently?”

This one hits.

The like that arrives years too late. The reaction to a new picture. The name you haven’t seen in months suddenly appearing on your screen as if it never left your mind.

But people from your past aren’t always reacting to your update itself. Sometimes they’re reacting to what seeing you awakens in them.

For a moment, you become a memory wearing a new picture.

That doesn’t automatically mean they want to return. It doesn’t mean they’ve changed, and it doesn’t mean the story is beginning again.

Don’t turn one notification into an entire future.

Sometimes a like is only a like. Your life is still moving forward.

Let the update remain an update.

“How do I know if I’m the problem?”

The fact that you’re willing to ask is a good sign, but it isn’t automatic proof that you aren’t.

Self-awareness requires more than worrying that you might be wrong. It requires being willing to examine what you did, understand its impact, apologize without defending yourself, and behave differently next time.

But there’s another danger here.

Some people take responsibility for everything. They assume that if a relationship failed, they must have failed. If someone is upset, they must have caused it. If they had simply been quieter, easier, or more accommodating, perhaps everything would have survived.

That isn’t always self-awareness.

Sometimes it’s self-blame wearing a thoughtful costume.

The better question isn’t, “Am I the problem?”

It’s: “What part of this belongs to me, what part belongs to them, and which part am I actually capable of changing?”

Own your part.

You don’t have to carry theirs too.

“You annoy me.”

Fair.

Somewhere in the world, someone has decided that I’m annoying. This is both humbling and strangely freeing.

You cannot be understood by everyone. Sometimes personalities simply clash. Sometimes your honesty irritates people. Sometimes you genuinely need to read the room. Knowing the difference is part of growing up.

I used to soften myself constantly to avoid being disliked. I edited my opinions, reduced my enthusiasm, and tried to become easier to consume.

I don’t want to live that way anymore.

I can remain open to criticism without becoming whatever version of me makes everyone else most comfortable.

If I’m going to annoy someone, I’d rather risk doing it honestly than disappear into a diluted version of myself.

The manual doesn’t have a chapter on this.

But I think the answer is: keep writing. Keep learning. Keep showing up honestly.

The right people won’t require you to become invisible before they decide to stay.

These were anonymous questions from No Manual readers.

If you want to submit yours, the anonymous link is in my Notes. No names, no judgment, and no perfect answers; just an honest attempt to think through the things most of us were never given instructions for.

These answers draw from ideas explored in People Are Poorly Documented by Zeek, available on Amazon.

Both things are true.

For a long time, I thought I had to choose one.

Either I could defend where I came from and pretend it had given me everything I needed, or I could criticize it and act as if I had escaped something terrible. Neither version ever felt honest.

My childhood was not a tragedy. It was full of family, noise, familiar streets, food that still tastes like comfort, and people who would show up for you before you finished asking. It was also a small world with strong rules about what a good life should look like.

Most of those rules were never announced.

You simply learned them by watching.

You learned which dreams sounded respectable. Which emotions made people uncomfortable. Which questions could be asked and which ones made you difficult. You learned that your choices were rarely yours alone because family, reputation, and community sat beside you in every decision.

In a small town, privacy can feel almost antisocial. Everybody knows somebody who knows your family. A mistake does not remain a mistake; it becomes news, advice, and sometimes a prediction about the rest of your life.

So you become careful.

You learn how to be accepted before you learn who you are.

## We were raised for survival, not self-discovery

The adults around me were not trying to make our world smaller. Most of them were trying to make our lives safer than theirs had been.

They had lived through financial uncertainty, social pressure, and the constant fear of falling behind. When survival has occupied most of your imagination, “follow your passion” sounds less like wisdom and more like a threat.

A good child studied. A sensible adult found stable work. A responsible person did not create unnecessary problems. You made the family proud, stayed close to what was familiar, and did not gamble with the future everyone had worked to build for you.

That framework produced discipline. It gave me endurance. It taught me to adapt, work hard, and keep moving when life was not interested in being fair.

It also left very little room for confusion.

Nobody told us that identity could take time. That you might change your mind more than once. That a wrong decision was information, not a permanent stain. That being grateful for your life did not mean you were forbidden from wanting a different one.

We had language for duty long before we had language for the self.

Even relationships were shaped by distance. Boys and girls often studied separately, sat separately, and learned to treat an ordinary conversation as something loaded. Friendship could quickly become gossip. Interest became a big event before either person had enough experience to understand it.

We were expected to build mature relationships later in life after spending years learning how not to know one another.

That was only one example of a larger pattern: many parts of life were introduced to us as rules before we had the chance to experience them as human beings.

Respect meant obedience. Strength meant silence. Love often came with instructions. Protection and control could look almost identical when nobody had taught you to ask where one ended and the other began.

And because everyone around you seemed to understand the same rules, you assumed this was simply how the world worked.

## You do not know your world is small until it gets bigger

Moving abroad did not instantly make me wiser.

An airplane is transportation, not transformation.

I carried my first version of the world with me: my fears, assumptions, insecurities, and the habits that had once helped me belong. I also carried a quiet certainty that I understood more than I actually did.

Then life began introducing me to people who did not fit inside the categories I had inherited.

I met people who had changed careers at thirty and did not consider themselves failures. People who spoke openly about therapy, loneliness, ambition, and doubt. People who disagreed with their parents and still loved them. People who built families differently, lived alone without apology, or left entire lives behind and rebuilt them from nothing.

I worked with women and men from cultures I had barely understood. Some were more experienced than me. Some had crossed countries alone. Some had survived things they spoke about casually because life had not given them the luxury of making a ceremony out of resilience.

I met people whose confidence was quiet, whose kindness had boundaries, and whose respect did not require agreement.

Nobody gave me one dramatic speech that changed my life. It happened through hundreds of ordinary interactions.

A colleague challenging an idea without making it personal.

A friend telling me I was wrong and staying long enough to explain why.

Someone setting a boundary without anger.

Someone asking what I wanted, then waiting as if the answer mattered.

Slowly, the world became more complicated—and I became less certain.

That uncertainty was uncomfortable. It was also the beginning of growth.

## Awareness is rude when it first arrives

Once you learn a better way of seeing, your memory becomes a difficult place.

Old conversations return with new subtitles. You remember moments when you were defensive, judgmental, controlling, dismissive, or simply unable to see beyond what you had been taught.

You realize that good intentions do not always create good behavior.

You remember people you misunderstood because they wanted lives you had never seen before. You remember taking disagreement as disrespect. You remember confusing being needed with being loved. You remember giving advice when the more useful thing would have been to listen.

For a while, I hated the younger version of myself.

I thought shame was evidence that I had changed. If I disliked him enough, perhaps that proved I was no longer him.

But shame has a strange ego inside it. It can keep you staring at your past without asking what you are doing differently in the present.

Growth is not how beautifully you apologize to yourself. It is how you listen now. How you behave when challenged. How much freedom you allow the people you claim to love. Whether you can admit that your first interpretation may not be the truth.

Real change is usually boring from the outside.

It is pausing before reacting. Asking a better question. Letting somebody make a choice you would not make. Saying “I was wrong” without adding a speech about why you were understandable.

It is choosing curiosity where your younger self would have chosen certainty.

## Growth can feel like betrayal before it feels like freedom

The more I changed, the more complicated home became.

I would sit with people who were supposed to feel familiar. The language was mine. The food was mine. The jokes arrived in the rhythm of my childhood.

Yet something in me stayed untranslated.

The disconnect was rarely about one dramatic belief. It appeared in small moments: how quickly another person’s life became a public discussion, how difference was treated as disrespect, how easily advice became judgment, how often love arrived carrying a complete plan for who you should be.

I understood the room perfectly.

I just could not disappear inside it anymore.

This is one of migration’s quieter costs. You spend years missing home, then discover that distance has changed your eyes. You return—physically or through people—and recognize everything except the person you have become.

Sometimes the people who resemble your past no longer resemble your values. Sometimes strangers make more room for you than familiarity does. Sometimes growth feels less like finding where you belong and more like accepting that an older kind of belonging is no longer available.

For years, that made me angry.

Then it made me sad.

Now I think I understand it differently.

Outgrowing a version of home does not require humiliating the people who still live comfortably inside it. They are also carrying histories, fears, duties, and rules handed to them before they could choose. Some may never question those rules. Some cannot afford to. Some will, but much later than you want them to.

Compassion does not mean surrendering your values. It simply means remembering that your growth was not created by superior intelligence. You had distance. You had exposure. You met people who expanded your evidence.

Under different circumstances, you might have remained exactly where you began.

## I finally went back for the kid I left behind

When I think of the boy I was, I no longer see somebody I need to put on trial.

I see a kid studying the adults around him and trying to build a map.

He did not know the map was incomplete. Why would he? It contained every road he had ever seen.

He wanted to be good. He wanted to be respected. He wanted to make his family proud and avoid becoming a problem. He mistook certainty for maturity because nobody had told him that wise people often live with more questions, not fewer.

He learned some things that helped him survive.

He learned other things he would eventually have to unlearn.

Neither makes him a villain.

There is a popular version of growth where we publicly destroy our former selves to prove our evolution. I do not believe in that anymore.

If I met that boy now, I would not lecture him about everything he had wrong. I would sit beside him. I would ask what he was afraid of. I would tell him that the world is much larger than the one he can currently see.

I would tell him that changing his mind will not make him weak. That love is not ownership. That being misunderstood will not kill him. That a life can be rebuilt more than once. That he does not have to earn rest, hide confusion, or turn every mistake into a definition of himself.

I would also thank him.

He survived long enough to become me.

The goal was never to escape him. It was to return with a larger map.

Maybe that is what healing actually looks like: not becoming ashamed of where you began, and not remaining loyal to everything it taught you.

You keep the tenderness. The resilience. The instinct to show up for people. The parts of home that still feel like warmth.

You leave behind the fear, the silence, and the rules that only made sense in a smaller world.

You can love where you came from without living there forever.

Share

And you can outgrow home without hating it.

“I’m just being careful.”

It sounds responsible.

Mature, even.

After all, you’ve been hurt before.

So of course you’re paying attention.

Looking for red flags.

Trying to avoid repeating history.

But somewhere along the way…

“Being careful” quietly becomes “building a case.”

Every delayed reply becomes proof.

Every canceled plan becomes evidence.

Every awkward silence becomes a warning.

Not because this person has done anything wrong…

But because someone else once did.

We tell ourselves we’re assessing them.

Sometimes we’re just comparing them to ghosts.

People who aren’t even in the room anymore.

The hardest part is…

Our brains are incredible pattern-recognition machines.

Once we decide someone will leave…

We unconsciously begin treating them like they’re already halfway out the door.

We become distant.

Overanalyze everything.

Test them.

Pull away before they can.

Then when they eventually stop trying…

We quietly tell ourselves,

“I knew it.”

Did you?

Or did you accidentally help create the very ending you were trying to avoid?

Fear has a strange way of disguising itself as wisdom.

It whispers,

“Protect yourself.”

Sometimes that’s exactly the right thing to do.

But sometimes…

It’s asking an innocent person to pay for someone else’s debt.

I’ve been guilty of this too.

Calling it discernment.

Calling it intuition.

Calling it “taking things slow.”

Sometimes it was.

Sometimes…

It was just fear wearing a nicer outfit.

Maybe healthy relationships don’t begin with blind trust.

But they probably don’t begin with silent suspicion either.

Maybe they begin with something much simpler:

Giving people the chance to become who they actually are…

instead of forcing them to defend themselves against people they’ve never met.

Trust doesn’t mean ignoring red flags.

It means allowing green ones to count too.

I’ve started asking myself a different question.

Not,

“How do I stop myself from getting hurt?”

But,

“Am I giving this person a fair chance to be themselves?”

Those aren’t the same question.

And they lead to very different lives.

Because sometimes…

They’re not acting weird.

They’re just reacting to being held at arm’s length by someone who’s still healing from another story.

Share

Don’t make someone prove they aren’t the person who hurt you.

Give them the opportunity to become the person who never would.

old.

Not because thirty actually is old.

Because everyone around me talked about it like life quietly starts closing doors after that.

Especially for women.

As if thirty was some invisible deadline.

Some countdown clock.

Some finish line.

I wish someone had told me something different.

Because my thirties haven’t felt like an ending.

They’ve felt like an introduction.

I don’t think your twenties are meant to be your masterpiece.

I think they’re research.

You spend a decade collecting data.

Jobs you hated.

People you loved.

People you shouldn’t have loved.

Cities that changed you.

Dreams that quietly expired.

New ones that appeared out of nowhere.

You think you’re building a life.

Looking back…

You’re actually building yourself.

In your twenties, everyone seems certain.

Someone is launching a startup.

Someone is getting married.

Someone is buying a house.

Someone is traveling the world.

Someone else already has two kids.

Everyone looks like they received an instruction manual.

You start wondering if yours got lost in the mail.

It didn’t.

Nobody knew what they were doing.

Some people were just better at looking like they did.

Then one day…

Something changes.

Not dramatically.

Quietly.

Like someone finally turns a light on.

You notice the things that once impressed you…

don’t anymore.

You stop chasing rooms that don’t make you feel welcome.

You stop saying yes because you’re afraid of missing out.

You start saying yes because something genuinely excites you.

Your peace becomes expensive.

Your time becomes intentional.

Your friendships become fewer…

and infinitely better.

For me…

My thirties didn’t make me a different person.

They stripped away all the versions of me that weren’t.

The one trying to fit in.

The one trying to impress everyone.

The one measuring success using someone else’s definition.

Somewhere between the mistakes, heartbreaks, career changes, unexpected wins, and ordinary Tuesdays…

I finally met myself.

Maybe that’s why I laugh when people fear turning thirty.

I understand the feeling.

I had it too.

But now?

I wouldn’t trade what I know now to relive my twenties.

Not for anything.

Because confidence built from experience feels different than confidence built from hope.

One is imagined.

The other has survived.

If you’re still in your twenties…

Please don’t rush them.

Say yes to the road trip.

Apply for the job you’re convinced you’re underqualified for.

Move cities if your heart keeps pulling you there.

Work the odd job.

Talk to strangers.

Fall in love.

Get your heart broken.

Change careers.

Read books that challenge you.

Travel if you can.

Collect stories.

Not because every decision will be right.

But because every experience gives Future You another piece of the puzzle.

You’re not wasting time.

You’re gathering material.

And if you’re about to turn thirty…

Take a deep breath.

Nothing magical happens at midnight.

But if you’ve spent your twenties paying attention…

One morning you’ll wake up…

and realize you’re finally becoming someone you genuinely enjoy spending time with.

Not because life became easier

Because you finally became you.

Your twenties teach you how the world works.

Your thirties teach you how you work.

There’s a big difference.

And it’s one of the best discoveries you’ll ever make.

I’d love to hear from you.

Leave a comment

If you’ve already reached your thirties, what surprised you most?

And if you’re still in your twenties, what’s one thing you’re hoping your future self figures out?

Share

Head of this.
Leading global initiatives.
Building teams and things across finance and healthcare.
Investing. Advising. Serving on nonprofit boards.

But bios are funny.

They tell you where someone arrived.
Not how they got there.

Mine leaves out waiting tables.

Taking three different buses to get to university.

Working through the night, then sitting in a morning class pretending my brain was still functioning.

Long commutes.
Couch stays.
Migrations.
Starting over in places where nobody knew my name.

It also leaves out the DJ nights.
Singing locally.
Traveling whenever I could.
Saying yes to experiences that made absolutely no sense for the career I was supposedly building.

And maybe that’s the part I’m most grateful for.

I was never too embarrassed by where I was to ask for where I wanted to go.

I asked questions.
Asked for opportunities.
Knocked on doors I probably wasn’t qualified to knock on.

Some opened.

Most didn’t.

But enough did.

That’s one thing life has taught me:

Don’t become so ashamed of your current chapter that you stop participating in your own story.

Take the bus.

Walk to a job insane amount of miles.

Sleep on the couch.

Work the weird job.

Ask the uncomfortable question.

Go to the place where you know nobody.

Try the thing that doesn’t fit neatly on LinkedIn.

Your life doesn’t need to look impressive while you’re building it.

It just needs to keep moving.

Funny thing is, eventually all those random chapters start looking less random.

And one day you write the polished bio.

Only you know how many bus stops are hidden between the lines.

I grew up in a culture where certain friendships were rarely allowed to remain simple. If two people of the opposite gender became close, others quickly gave it a romantic explanation. Connection was treated as evidence, kindness as interest, and emotional closeness as something that must eventually become more.

So many of us learned how to keep our distance before we learned how to be open.

It was only later, after living in another country and meeting people outside the world that raised me, that I began to understand how much I had missed. Some of the friendships I formed there changed me—not through dramatic lessons, but through ordinary conversations repeated over time.

They gave me access to experiences I had previously understood only from the outside. They showed me that two people can enter the same room, hear the same joke, experience the same silence, and leave with entirely different feelings.

They taught me to listen without immediately trying to explain, fix, or defend.

More importantly, they helped me separate emotional closeness from romantic possibility.

When we grow up with limited space for open friendships across genders, ordinary warmth can begin to feel unusually significant. Being understood feels like attraction. Vulnerability feels like intimacy. Kindness becomes something we search for hidden meaning inside.

But not every meaningful connection is asking to become something else.

Some people enter our lives simply to widen them.

A healthy friendship can hold affection without possession, admiration without expectation, and honesty without confusion. It teaches us that another person’s warmth is not a promise and their vulnerability is not an invitation. Sometimes trust is only trust—and that is already something sacred.

This kind of friendship requires emotional maturity. Attraction may occasionally exist; we are human. Maturity is not never feeling something. It is knowing that every feeling does not need to become a decision.

It is choosing to value the person more than the possibility.

These friendships changed the way I carried myself in relationships too. I became more patient, more aware, and less likely to assume that my experience was the only reasonable interpretation of a moment. I learned that listening is not merely waiting for my turn to speak. Sometimes it means creating enough safety for another person to finish the sentence.

They also taught me that no single relationship should have to carry the entire weight of our emotional life.

Perhaps that is why these friendships matter so much, especially for those of us raised in cultures where interaction between genders was monitored, restricted, or quietly discouraged. Without familiarity, difference becomes mystery. And when something remains mysterious long enough, we either fear it, idealize it, or misunderstand it.

Friendship makes people human again.

It replaces assumptions with conversations. It reveals humor, fear, contradiction, ambition, insecurity, and tenderness. It reminds us that people are not categories waiting to be decoded. They are whole inner worlds.

I sometimes wonder who I would have become without those friendships.

Probably a more limited version of myself. Not necessarily cruel or closed-minded—just someone carrying ideas that had never been challenged by closeness.

The most meaningful friendships do not always arrive loudly. Sometimes they simply sit beside us, share their world, and leave us capable of understanding lives beyond our own.

They do not complete us.

They expand us.

Here’s what arrived — real questions from real people, about relationships, fights, heartbreak, and the weight of past selves. No names. No context. Just honest questions.

This is what I’ve learned thinking about each one.

________________________________________

“What should I do if I’m heartbroken?”

Don’t try to fix it.

Heartbreak makes you want to solve the problem immediately. Text them. Get closure. Understand exactly what happened. But understanding won’t speed up the healing. The feeling has to pass through you — it can’t be explained away.

What helped me: don’t numb it. Don’t spiral either. Let it sit in the background while you do ordinary things. Make food. Go outside. Sleep. Your brain is reprocessing. It needs time, not solutions.

Grief is not a problem to be solved. It’s something to be carried until it gets lighter.
________________________________________

“You think it’s normal to stop talking forever after a fight?”
It’s common. Whether it’s normal is a different question.

I’ve learned that the silence after a fight is rarely about the fight. It’s about what the fight revealed. People don’t stop talking because of one argument. They stop talking because the argument confirmed something they suspected — that they don’t know how to repair this, or that the other person doesn’t want to.

Some silences are endings wearing a disguise. Some are just two people who don’t know how to say “I’m sorry” without losing face.

The question isn’t “is it normal?” The question is “what are you both actually protecting?”
________________________________________
“Stronger or more guarded because of what happened to you?”
Both.

And I used to think that was a contradiction. Strength was supposed to mean openness, and guardedness was supposed to mean weakness. But what happened to me didn’t make me choose. It made me both — stronger in ways I can point to, and more careful in ways I can’t always explain.

The thing people don’t tell you: the same walls that keep people out also keep you in. Guardedness protects you from being hurt again. It also protects you from being known.

You can’t have the openness without risking the hurt. You just get to choose which version of yourself you want to carry forward.

________________________________________
“U ever wanna go back to your old relationship?”
No.

But not because it was terrible. Because going back isn’t possible. Not to a person — to a version of yourself that no longer exists.

I used to think the old relationship was a door I could open again. It’s not a door. It’s a photograph. You can look at it. You can even feel something looking at it. But you can’t walk into it.

The person I was then didn’t know what I know now. And the person I am now wouldn’t fit into the life I had then. That’s not sad. That’s just time doing what time does.

________________________________________
“Has someone from before reacted to an update recently?”
This one hits. The update that an ex reacts to. The like that arrives three years too late.

Here’s what I’ve learned: people from before don’t react to your update. They react to what the update triggers in them. You’re not a person to them — you’re a memory wearing a new picture.

It’s not about you. It’s about whatever they’re going through right now. Don’t read it as a signal. Don’t rebuild a story around a single reaction. Your life is moving forward. Let the update stay an update.

Not dramatically. Not flailing. I just descend. Calmly. Gracefully, even. Like a stone that has made peace with its nature.

Instructors tell me to relax. I am relaxed. That’s the problem. A relaxed body in water, apparently, sinks. You’re supposed to tense certain muscles in specific configurations to maintain buoyancy. Most people do this intuitively. I do not.

But here’s the paradox. Put me in a crisis and something in me just settles. My heart rate drops. My thinking gets clear. I become the person who says “okay, here’s what we’re going to do.” And then does it.

I don’t know why. The same traits that make me terrible at floating might be the ones that make me useful when things fall apart. Maybe my brain processes emergencies differently. Maybe years of masking — performing calm in social situations where I was internally overwhelmed — created a transferable skill.

In emergencies, people look for someone to follow. They don’t choose the loudest person or the most qualified. They choose the calmest person. I’ve become that person by default in enough situations that I’ve stopped being surprised.

But it means my value isn’t evenly distributed. Most of the time I’m below average. In a crisis, I’m what you need. Same traits. Different context.

I think about this a lot when people talk about strengths and weaknesses. The standard framework is: identify your weaknesses, fix them. But what if some weaknesses are just strengths in the wrong context? What if the thing that makes you bad at small talk is the same thing that makes you good at pattern detection? What if the thing that makes you unable to float is the same thing that makes you able to lead when everyone else is panicking?

I stopped trying to learn swimming. Not because I gave up. Because the energy I was spending trying to become mediocre at something I’m naturally terrible at could be spent becoming excellent at something I’m naturally good at.

You don’t need to fix everything. You need to know what you’re good at — genuinely good at, not what you wish you were good at — and invest there. The weaknesses you can’t fix? Mitigate them. Outsource them. Accept them. But don’t spend your life trying to turn a weakness into a strength. Spend it making your strengths stronger.

I still can’t swim. If we’re ever on a boat together and it sinks, grab a life vest and follow me. I’ll be the one calmly directing people to the exits while slowly descending toward the ocean floor.

________________________________________

People Are Poorly Documented by Zeek. Available on Amazon.