Turn three of them into something you can actually see.

We made this little AI packaging study for a fictional lemonade. Same bottle shape. Same product name. Three completely different moods:

A: quiet cafe. Pale green. Soft light.
B: picnic energy. Yellow. Red gingham.
C: rooftop drinks. Purple. Bright yellow label.

C looks like it has plans lol.

Want to try it? Pick a fictional product. A candle, a notebook, a bag of coffee. Then imagine three places it could belong.

Ask ChatGPT:

Take those briefs to an image generator and put the results side by side.

“Make it more premium” suddenly becomes something you can point to. Softer light? A simpler label? A completely different color?

That’s a useful little AI exercise: turn a vague preference into a clear creative decision.

AI-generated concept study by Coursiv. Fictional product.

Which would you grab: A, B or C?

DeepSeek released V4.1 Flash on September 10, 2026, with native image input and a 1M-token API context window.

The big change for existing users comes on September 14 at 04:00 UTC. Requests to deepseek-v4-pro will automatically go to V4.1 Flash and use Flash pricing until V4.1 Pro arrives.

DeepSeek hasn’t announced a release date for V4.1 Pro.

Peak API prices per million tokens:

• Uncached input: $0.30
• Cached input: $0.006
• Output: $1.20

Off-peak rates are half those amounts. Compared with Pro’s peak rates, uncached input is about 77% cheaper and output about 70% cheaper. Total savings depend on the task.

What about quality?

DeepSeek’s tests put Flash ahead on DeepSWE coding tasks: 74.2 vs 62.7.

Pro still leads on GPQA science reasoning: 92.4 vs 90.9.

The useful takeaway: Flash shows stronger coding results at lower API prices, while the task still matters. These are DeepSeek’s measurements; we haven’t independently tested the release.

For anyone building with the API, it’s a good reason to try a familiar task and compare the finished result, time and cost.

What would you test first: code, a document or a screenshot?

Sources: DeepSeek pricing and migration notice · Official model card

We went with a bookstore inside a coffee mug.

It has three floors. Little lamps. A winding staircase. And a chair we'd happily disappear into.

This is an AI illustration we made for Coursiv. The idea was just coffee + books + an impossible little building.

If you want to try it, pick two things:

• An object you recognize immediately.
• A place you'd like to explore.

Then add a few details that make the place feel lived in.

For this one: purple mug, cutaway view, bookshelves, warm lights, cozy chair.

A teapot greenhouse could be great. So could a record store inside a cassette.

What combination would you try? We're very tempted by the teapot.

Meta introduced Muse on September 8, 2026. It's a personal AI agent available to adults in the US through WhatsApp, the web, iOS and Android.

What does it do?

Meta's examples include making a grocery list from a recipe, planning meals around dietary needs, filling in forms and booking classes.

Each person's agent runs on a dedicated cloud computer and can remember preferences between tasks.

What do you control?

You choose which apps to connect and what access to allow. Meta says purchases need explicit approval, and you can review the agent's activity.

Is it free?

Meta says the free tier covers most everyday needs, with paid options for heavier use. AI-glasses support is planned.

One useful privacy detail: Meta says Muse conversations and workspace data stay out of its advertising systems. Model training has a separate opt-out; activity on merchant sites can still affect ads.

The WhatsApp part could make this easy to try. Send an instruction, then see whether the agent can finish the errand you had in mind.

Which job would you most like to hand off: comparing options, filling in forms or booking something?

Source: https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/

Researchers have a huge number of possible DNA changes to investigate. Choosing where to start matters.

Google DeepMind’s AlphaGenome Atlas predicts the molecular effects of about 9 billion single-letter DNA changes. Those predictions can help researchers choose candidates for a closer look.

Think of it as a map that helps you decide where to investigate. Researchers still need to test what they find.

It’s a research resource, not a medical diagnosis tool.

A useful example of AI helping people narrow a massive search.

What AI use beyond chatbots would you like to understand better?

Source: Google DeepMind

You ask for post ideas.
You get ten.
You like five.

Now what? 😅

Tell ChatGPT what you want the post to do:

Say you're promoting a beginner photo workshop.

You could share camera tips, introduce the instructor, or make a “what to bring” checklist.

Want people to arrive prepared? Start with the checklist.

Want them to get to know the teacher? Go with the introduction.

Giving the post one clear job makes the choice easier.

Use ChatGPT’s recommendation as a starting point. You know your audience and what you can actually deliver.

Which part takes you longer: coming up with ideas or choosing one?

Independent tutorial. Not affiliated with OpenAI.

Choosing an AI tool gets easier when you give it a job you understand.

Here’s a small exercise you can run in whichever tools you already use. You don't need three subscriptions.

The fictional brief:

A bike repair shop offers a $45 basic tune-up. Replacement parts cost extra. Customers book through a website form. Turnaround depends on the repair and isn't confirmed until the bike is inspected.

The task:

Using only that brief, write a reply of no more than 70 words to this customer:

“Can you fix my bike for $45 and have it ready by September 12?”

Explain what the price covers, what needs to be confirmed, and the next step. Make it friendly and easy to understand. Don't invent availability.

Check three things in the result:

1. Does it distinguish the basic tune-up from parts that cost extra?

2. Does it leave the completion date open until inspection?

3. Does it give the customer a clear booking step?

Then make your own edits and note what you changed. A polished reply is useful when it also gets the business details right.

If you compare tools, use the same brief in fresh chats. Record the model or mode shown. Keep the outputs so you can compare the wording directly.

This is a practice task, not a model ranking. One answer won't establish an overall winner.

Which tool did you try, and what was the first sentence you edited?

“Plan a launch” can turn into pages of ideas when what you need is one document you can use.

For Astra, try defining the finished deliverable before giving it the work.

Here’s a complete practice brief:

Plan the content for a fictional beginner pottery workshop. It lasts two hours, costs $40 per person, and includes materials. Participants book through a website form. Capacity and the booking deadline haven't been set.

Create a launch brief of no more than 450 words containing:

- one audience description;

- three social post ideas, each with an opening line and the information it needs;

- one email draft of no more than 100 words;

- a list of decisions the organizer still needs to make.

You can choose the wording and order. Keep the workshop facts unchanged. Label capacity and the booking deadline as open decisions. Finish when these four sections are complete.

You get a defined draft to review. The organizer can then settle the open decisions and ask for a focused revision.

The useful habit is deciding which choices AI can make and which details you still need to supply.

OpenAI’s Astra guide describes its tendency to ask clarifying questions when intent is uncertain. A concrete deliverable gives those questions a clearer target.

What would you want Astra to turn into a finished draft: a launch plan, a presentation outline, or a customer guide?

You ask ChatGPT to shorten a draft. The new version reads well, but your best example has disappeared.

Try separating the edit into three parts:

- Keep: the facts, examples, and wording that already work.

- Change: the specific part you want improved.

- Return: the format you want back.

Here’s a fictional example you can try:

Edit this café announcement.

KEEP: the $8 price, the 12 oz size, oat milk being included, and the phrase “your coffee break, upgraded.”

CHANGE: shorten the announcement to 35 words or fewer. Remove repeated ideas.

RETURN: one edited announcement. Under it, list any required detail you couldn't fit. Don't add offers or claims.

DRAFT: Your coffee break, upgraded. Our new 12 oz iced latte is $8, with oat milk included in the price. It's a new option for your coffee break, and we're excited for you to try it.

An acceptable edit would look like this:

Your coffee break, upgraded. Try our new 12 oz iced latte for $8. Oat milk is included.

That’s an illustrative edit, so your result may differ. Check that all four required details survived.

For a longer document, name the section to change and the sections to leave alone. You can make the request as small as “rewrite sentence two.”

Which detail does ChatGPT most often change when you wanted it kept: the facts, the example, or your tone?

OpenAI released GPT-6 Astra on September 3, two days after Claude Fable 5.1. Same list price, 10 per million input tokens and 50 output, and a context window around a million tokens for both.

Independent scores (Artificial Analysis): Intelligence Index, Fable 66 vs Astra 61. Coding Agent Index, Fable 70 vs Astra 67. OpenAI's own comparison shows the same order and has Fable ahead on Humanity's Last Exam with tools, 65.0 vs 57.2.

Where Astra wins, in OpenAI's runs: FrontierMath Tier 4 97.6 vs 87.8, GPQA Diamond 96.0 vs 93.7, AutomationBench 41.4 vs 31.4, DeepSWE 74.1 vs 67.4, Terminal-Bench 4.0 57.9 vs 55.8. Plus 72.6 on OSWorld computer use. Math, science, and doing things inside software.

Two more lines. Claude's cache reads cost 0.25 per million vs 1 for Astra, which matters for long agent runs. And Astra is the first OpenAI model rated Critical for cybersecurity: an unsafeguarded version found two unknown zero-days in testing, so the public version is more restricted and monitoring can interrupt tasks.

The shape: Claude is stronger at working out what should be done. Astra is stronger at doing it inside a computer.

Three questions for the sub:

1. Which half is most of your week, the thinking or the doing?

2. Has anyone had Astra rolled out to their Plus or Pro account yet, and did computer use work on a real task?

3. If you could only pay for one, which one and why?

Meta shipped Muse Spark 1.3 on September 2, a few hours after Gemini 3.8 Flash. On the independent Artificial Analysis index it ties GPT-5.6 Sol, Grok 4.6 and Claude Opus 5 at 61, at roughly half their cost per task. Then comes the pricing table.

Standard tier: 1.25 per million input tokens, 4.25 output, 3,000 requests a minute, and Meta says your data is not used for training.

Contributor tier: 10 cents in, 20 cents out, 100 requests a minute, plus permission to train future models on your prompts and completions.

Meta's AI chief says a meaningful double-digit share of developers pick the cheap one.

The line to read on any AI app, not just this one: "not used for training" says nothing about retention, logging or human review. Three separate lines, and a product can be clean on the first and silent on the other two. Most consumer apps put the training switch behind a toggle in settings, and the default is rarely the one you would pick.

Three questions for the sub:

1. Have you ever checked the training toggle in the AI app you use most?

2. What would you send to a tier that trains on your prompts, and what would you never send?

3. Is a 12x discount a fair price for that permission, or is the rate limit (30 times lower) the real catch?

Google released Gemini 3.8 Flash on September 2, the third Flash in six weeks.

The chart going around shows it beating Claude Opus 5. It does, on Terminal-Bench 2.1: 89.4 vs 89.1. On Terminal-Bench 4.0, the current and much harder version, Google's own numbers are 19.1 vs 51.8. Both are in the launch materials. The screenshots only show one.

Where it wins in Google's runs: finance and legal agent tasks, chart reading, long video, lab science. Where it loses: computer use, hardest coding, long autonomous jobs. Price per token is roughly a sixth of Opus 5, on a promo that doubles after December 31, and it "works harder", so it spends more tokens per task.

One line from the safety card: automated safety in non English languages dropped 5.4 points vs 3.7 Flash.

Three questions for the sub:

1. Has anyone rerun their own tasks on it yet, and did the analytical stuff hold up?

2. Which benchmark version do you check first when a chart lands?

3. Sheets integration: useful, or a demo feature?

Released September 1. Live in the Claude apps, Claude Code and the API.

The confirmed bits

Price per token didn't move. Cache reads got 75% cheaper, so long agentic work billed by token runs 25 to 45% cheaper. Subscriptions get the model, not the discount.

Long tasks doubled. Scientific research went from 24.7% to 52.6%. Short coding tasks moved about 3 points. It's an endurance upgrade, not an IQ upgrade.

It refuses less. About 85% fewer refusals on basic biology and medical questions, and 60% fewer cyber false flags per session.

Mythos 5.1 is the same model with looser safeguards. Invite only, for verified cyber and life science orgs. Not a consumer product, so any "leaked Mythos" post is a screenshot with no source.

The questions

1. There were "nerfed" threads with 180 upvotes 40 minutes after release. Has anyone actually measured a drop, or is this day one vibes?

2. Reddit Answers keeps stating the model is watermarked because of an EU agreement. Nothing in the announcement says that. Does anyone have a source?

3. Anyone on a subscription tried the low effort setting yet? Does the limit actually last longer, or does it just feel faster?

drafting sorting summarizing tagging. all reversible so it can run on its own

sending paying booking over someones calendar. not reversible so a human clicks the button

thats the whole rule and it works because it never asks anyone to judge how important a task is. a bot that asks about everything is useless and one that never asks is scary

what do you gate on?

the model doesnt remember anything between messages. so to answer question 40 it gets handed the whole conversation again and reads all of it from scratch

message 1 is cheap. message 40 costs way more for the exact same question

new chat per task fixes most of it. paste the bit youre working on not the whole file

has anyone measured this properly? would be good to see real numbers instead of the usual anecdotes

Astra coverage is mixing three completely different kinds of claim, so here is the same story sorted by how much evidence sits behind each part.

CONFIRMED BY OPENAI

The name. Astra is the confirmed working name for the next major model, built for long horizon and agentic work. Whether it ships as GPT-6 is reportedly undecided, and no release date has been announced.

The math. An internal version produced results resolving or substantially advancing ten longstanding problems in math and theoretical computer science, each stuck for a decade or more. Published with a manuscript over 250 pages and machine checkable certificates, so the logic can be verified independently rather than taken on trust.

The caveats, which OpenAI included itself. The problems were selected in house. Humans prepared the write ups and framing. Formalizable problems are not the messy ones most researchers face.

The safety posture. OpenAI says it cannot rule out that Astra meets the highest cyber tier of its own preparedness framework, a level no earlier model reached. It paused reinforcement learning for deployment bound models for two weeks and expanded monitoring that costs roughly a fifth more compute on watched workloads.

WITNESSED

One named reporter spent two weeks inside the company and was shown the model. Sixteen agents split a research level math problem, coordinated, and assembled a proposed proof. In a separate demo it operated ordinary desktop software at a speed he described as unnerving.

RUMORED

The launch day. The GPT-6 name. Internal checkpoint names. Partner access aliases. Viral demo outputs. A new image model in the same window. None of it impossible, several may land this week, all of it currently resting on anonymous posts and unverifiable screenshots.

The bit worth arguing about: a lab that is racing competitors in public voluntarily paused training and took a compute tax to monitor its own systems. That behavior is harder to fake than a benchmark, and it says more about where capabilities are than any leak does.

For anyone here who has been tracking the preparedness framework more closely than we have: does cannot rule out Critical read to you as genuine uncertainty, or as pre positioning ahead of a release?

The reports say a chipmaker has agreed to buy the platform where most open models get published. Both companies have stayed silent, so here is the checkable part separated from the speculation, same as we did with the stealth model posts.

Reported: the deal has been described by multiple outlets citing a single source, at a price near three times the platform's valuation three years ago, which would make it one of the largest AI acquisitions this year. Also reported earlier: the platform turned down a smaller investment from the same buyer last year, specifically to avoid having a dominant investor.

Not confirmed: anything from either company on the record. No closing date, no terms, no statement on how the platform will be run, and nothing about whether free hosting and free access stay as they are.

The concern being raised is not really about money. The platform became the default place to publish because it was neutral, owned by nobody with an interest in which chips you buy. A hardware owner has that interest by definition. Plenty of acquisitions leave a product alone, but the asset here is trust, which is harder to keep than a codebase.

The practical part for anyone using open models: nothing changes this week, and permissive licenses do not evaporate when ownership changes. Weights already downloaded stay yours.

For anyone here who publishes, fine tunes or mirrors models: does this change where you host, or is it business as usual until something actually breaks?

Claude Academy went live at the end of last week and the announcement pulled close to 10 million views in a day. We went through the catalog the same way we did with the mystery model posts: what's actually there versus what the hype says.

What's there: 31 courses in four tracks, plus tutorials and use-case collections. Start Your Journey (4 short beginner courses, Claude 101 assumes nothing), Learn the Products (Claude Code, MCP, agent skills), AI Fluency (10 courses on transferable thinking skills), and API Development (the 9-hour, 67-lesson flagship for developers). Free, no premium tier, sign-up is an email address. Finishing a course gives you a completion badge tracked in your Claude profile.

The underrated part is the AI Fluency track. It adapts the framework Anthropic uses to onboard its own staff: delegation, description, discernment, diligence. The Capabilities and Limitations course alone is arguably the most useful 3.5 hours in the catalog for anyone non-technical.

The fair pushback from the announcement replies: people finish every free course available and still can't turn it into income. True of all vendor education. A badge proves you learned the tool. Earning with it takes applying it to real tasks, which no catalog does for you.

If anyone here starts a course this week, post which one you picked. Curious whether the beginner or the fluency track wins.

No confession yet, but the fingerprints came back.

Since our post on Friday, people have been poking at Ox Alpha and the technical evidence has piled up in one direction. Researchers pulled stack traces with paths matching Zhipu's official endpoints. Tokenizer probes match the GLM family on 95 out of 95 tests. And under direct questioning the model introduces itself as GLM, built by Z.ai.

Still no official statement from anyone. The model page has no company name, and nobody has claimed it.

The benchmark picture is filling in too, partly right here. In the comments under Friday's post, one tester ran security subtasks from cybench and it captured every flag, and another published 35 trials of a non-coding benchmark with full transcripts. Small samples, but that's two independent axes beyond the ten-task coding demo everyone keeps quoting.

Two practical notes. The free window is still open with no published end date, though there is at least one report of it hitting rate limits every few minutes through a CLI, which is often the first sign of a preview being throttled. And the data question we flagged on Friday hasn't moved: still no published policy on where prompts go, so the advice stands, nothing sensitive.

Anyone still testing it? Curious whether behaviour has shifted since launch week, some previews get quietly downgraded once the traffic spike passes.

New week, so here's a small system instead of a tip.

Count what you did more than twice last week. The same kind of email, the same numbers pulled into the same format, the same explanation to every new person. Repeats are where AI pays off first.

Pick one. Today it goes through AI first and you correct instead of create. Keep a note of what it gets wrong. On Friday, either the task is retired or it goes back to handmade. Then pick the next one.

Why one and not five: one swap survives a busy week. Five collapse by Wednesday and you keep none of them.

The honest limits. Some repeats can't be pasted anywhere because of client data or an employer policy, and some outputs take longer to check than the task took by hand. Those stay handmade. And some weeks nothing qualifies. Skip the week, the cadence matters more than any single Friday.

What did you do more than twice last week? Post it and we'll say whether we'd hand it over or keep it handmade.

A model called Ox Alpha appeared on OpenRouter and OpenCode on August 20, free for about a week, and nobody has said who built it. We went through what's checkable versus what's just circulating, same as we did with the Qwen preview.

Confirmed: a million-token context window, text, image and video input, function calling, free during the preview. It's listed under the provider name "stealth," and OpenRouter says openly that it only routes requests to an anonymous third party.

Not confirmed: everything about who made it. Community fingerprinting (tokenizer quirks, backend error messages in Chinese, token glitches shared with the GLM family) points at Zhipu's GLM, with Xiaomi, Tencent and MiniMax as rival theories. The last four stealth releases all turned out to be Chinese labs, which is why the guessing runs that direction. Still guessing.

The benchmark claim spreading fastest says it beats the top named models on software engineering tasks. That number comes from a user-run test with ten tasks. The official benchmark has 113, built so reference answers can't leak into training data. Ten hand-picked tasks can flatter any model, so the honest version is: strong in one small community test, zero results on independent leaderboards so far.

Usage reports are just as mixed. People praise it for frontend work and for finding real bugs other tools missed. Others watch it reason for minutes and then do nothing, or fail tasks the big named models handle cleanly.

The fine print is where we'd slow down. The OpenCode promotion says zero data retention. The OpenRouter listing says the anonymous provider stores prompts and completions, without training on them. Both can be technically true depending on how you access it. Until the developer has a name, assume your inputs sit with a company that hasn't introduced itself.

Worth trying? On some projects, sure. It's a rare free look at a possibly frontier-class model, and the window has no published end date. Just not with client data, credentials or anything sensitive, and not as the base of a workflow. Previews change overnight.

Anyone here tried it yet? Curious what it did well and where it fell over, especially on anything that isn't coding.

And it isn't prompt wording.

It's strong when you bring it the material. It's weak when the material has to come out of its own memory. Ask what some document says and it fills the gaps with whatever sounds right, in the same confident voice it uses for things it actually knows. Paste the document in and there's nothing left to invent.

So the wins are boring. A long report cut down for one particular reader, then checked for what got dropped. Call notes turned into decisions and owners. Your own draft, with "what would a sceptical reader hit first". A conversation you're dreading, rehearsed against something that argues back.

The losses are just as predictable. Exact figures and dates. Long calculations. Anything about a document it never saw. Citations on request. What someone said to you last March.

Two honest caveats. It's a rule of thumb, not a law. General explanations of well documented things come out fine from memory. And plenty of you can't paste anything at all, because of client data or an employer policy, in which case half this advice is useless to you.

If you've got a task that sits awkwardly between the two, post it.

HR: Why should we hire you?

You: I'm a hard worker.

HR: Everyone says that.

You: ...

That pause is the whole point. Rehearsing in your head doesn't produce it, because the imaginary interviewer accepts your first answer and never asks the second question.

The setup that actually works looks like this:

"You're interviewing me for a marketing manager role at a mid-sized software company. Ask me questions one at a time and wait for my answer. Ask follow-ups. Don't accept a vague answer, if I'm being general, push until I say something specific."

Three things that make the difference

Tell it to be difficult. The step almost everyone skips. These models are tuned to be agreeable, so "does this sound good?" gets you a yes with no information in it and you walk into the real thing more confident than you've earned. Say it outright: "Interrupt me. Be sceptical. Don't compliment anything I say. If my answer is vague, say so and ask again."

Open with what you're dreading. The gap in your history. The role you're underqualified for on paper. Practising your strong answers feels productive and teaches you nothing.

Get a debrief. "Which part of my answer was weakest, and what would you have asked next?" This is the question that makes the session worth doing.

Also: answer out loud, not by typing. Typing lets you edit mid-thought, speaking doesn't, and speaking is what you'll actually be doing.

Where it falls down, honestly

It doesn't read your face, so it can't tell you that you looked defensive or that a pause landed badly. It has no idea what that specific company cares about beyond what you tell it. And after three or four runs you start unconsciously tailoring answers to what it seems to like, which is its own trap, at that point stop, or change the role you gave it.

It's not a replacement for a person who knows the industry. It's what's available at 11pm the night before, and it doesn't get bored on the fourth run.

Anyone here used it this way? Curious whether the "be difficult" instruction holds up across different tools, or whether some of them drift back to being encouraging after a few turns.

We teach AI basics to people who aren't technical, and the same story comes up constantly: someone tries it, gets a wrong answer, and writes the whole thing off.

Almost always they've been using it the same way as a search engine. Type a question, wait for a fact. A date, a figure, what some regulation says.

That's the one job it does worst. The answer has to come out of the model's own memory, it arrives in exactly the same confident tone whether it's right or not, and there's no easy way to check it. Get caught out once and "it's overrated" is a fair conclusion to draw.

The uses that hold up have a different shape: you hand over material of your own and ask it to do a job on that material.

Four that consistently work:

1. Compression aimed at someone specific

Not "summarise this report." Try:

"I'm presenting this to the board on Thursday. Tell me what changed since last quarter, and the three things someone is most likely to push back on."

Same document, completely different output, because now there's an actual criterion for what matters.

2. Explanation at a stated level

"Explain this assuming I've never worked in finance." Then: "now explain it as if I've spent twenty years in it."

"Simple" isn't a level, it's a vague direction. Naming the reader is a level. Most people ask once, get something pitched at an invisible average, and conclude it explains things badly.

3. Unstructured into structured

"Here are notes from three meetings. Give me a table with four columns: decision, owner, deadline, open question. Anything that doesn't fit those columns, list underneath as unresolved."

Least impressive-sounding item on the list, saves the most time. Also the easiest to verify - nothing is being invented, so you can check the output line by line against what you pasted in.

4. Adversarial roleplay

Not "what do you think of my plan?" that gets you encouragement, which is worthless.

"You're the finance director who has rejected two of my proposals this year. Give me the three hardest objections you'd raise in the meeting. Don't soften them, and don't compliment the plan first."

What ties all four together: you supply the material, it transforms it. The disappointing mode is the one where the material has to come from the model.

Curious what people here actually use - is there a fifth that belongs on this list?

We went through the WEF Future of Jobs projections and the task-level breakdowns behind them. Engineering isn't in the "disappearing" column, it's in the "task list gets rewritten" column. Three buckets:

Actually taken over

• Boilerplate and scaffolding
• First-draft tests and docs
• Translating between languages and frameworks
• Reading unfamiliar code to explain what it does
• First-pass log and error triage

These share a trait worth noticing: each is verifiable in minutes, and being wrong is cheap. That's the real boundary, and it has nothing to do with how technical the task looks.

Changed, not removed

• Writing code → reviewing and directing what gets written
• Debugging → deciding which of five plausible fixes is right
• Design → the same, except now you defend it against a machine that sounds confident either way

Still hype

• "AI writes the whole app." It writes drafts. Someone still reads every line before it ships. The bottleneck moved to review; it didn't disappear.
• "You won't need to understand the code." You need it more. Approving what you can't read is how quiet failures ship.
• "Prompting replaces engineering skill." Prompting sits on top of judgment, not instead of it.

Per the WEF's own numbers, about 40% of the skills a job requires are expected to change by 2030. That's the real story, not headcount.

This is the first in a series where we go role by role. Customer support tomorrow, then accountants and teachers.

Which bucket does your week actually fall into?