An Exploded View publication

Reading Room

Vol. 1 · No. 24 Saturday, August 15, 2026 aikansh.com

This week's theme

What it takes to build well with AI now

Today runs on the craft of building with AI: which skills matter, what running agents actually costs, and where automated systems fail the people behind them.

A 16-minute read · 13 stories

In this issue

01 Front Page

Andrew Ng maps the four skills that matter in AI engineering

A new map of the four skills that matter most in AI engineering, built from over 10,000 job postings.

Andrew Ng, the AI researcher behind DeepLearning.AI, just published a map of the skills that actually matter in AI engineering (building and running software that uses AI models) right now. It is worth your time because it doubles as a checklist: hold your own skills and your teaching plans up against it and see what is missing.

Ng's team built the map from three sources: an analysis of more than 10,000 job postings, dozens of structured interviews with AI experts, hiring managers, and recruiters, and surveys plus other online data. Out of that work they pulled four skills that matter most, not just today but in the near future too.

The first is building and deploying AI applications. The core difference between AI software and regular software, in Ng's words, is that AI software gives unpredictable outputs: you don't know exactly what a language model will say back, or what a trained model will predict on a new example. People good at this skill understand the building blocks (language models, feeding the model your own documents before it answers, letting the model take several steps on its own, and classic machine learning) and know how to run disciplined tests to measure and steer how the system behaves.

The second is software engineering fundamentals: the trade offs between cost, speed, reliability, and scale that every system has to make. Ng draws a sharp line here: an experienced engineer who understands these trade offs can steer an AI coding tool with precision, while an inexperienced one who just lets the tool write code without knowing what trade offs it is making will often get poor results, because they don't know what context to hand it.

The third is using coding agents (AI tools that can take several steps on their own to write and fix code) well. That means having a working mental model of how they behave, knowing their limits, and knowing when to step in and when to leave them alone.

The fourth is shaping the build itself.

One deliberate choice in how Ng frames this: he talks about AI engineering skills, not the AI engineer job title, because he thinks every kind of developer, full stack, data, DevOps, machine learning, will need these skills. DeepLearning.AI's main focus now, he says, is helping developers build exactly these four skills.

The key difference between AI and non-AI applications is that the former has unpredictable outputs.
via @AndrewYNg on X →
02 Also on the Front Page

Anthropic eyes 2 trillion dollar IPO despite thin profit

Backers reportedly expect an October IPO near 2 trillion dollars, even though Anthropic isn't yet profitable.

He runs his day to day work on Claude Max, so it matters where Anthropic, the company behind Claude, actually stands as a business. According to the Financial Times, a handful of Anthropic's backers now expect the company to go public in October at a valuation of 2 trillion dollars or more.

That would make it the most valuable initial stock sale (IPO, when a private company first sells shares to the public) in history, beating SpaceX's 1.77 trillion dollar IPO from June. It would also be more than double the 965 billion dollar valuation Anthropic carried after its Series H funding round in May. Separately, Bloomberg reports Anthropic is in talks to buy the AI startup Decart AI for 6 billion dollars.

Anthropic filed confidentially for its IPO with the Securities and Exchange Commission back in June, but has not set a public date. Rival OpenAI filed shortly after, though it isn't expected to go public until 2027.

Here is the awkward part: Anthropic is not yet profitable. Companies in the Nasdaq 100 (the index of large tech companies Anthropic would join) trade on average at about 34 times their trailing yearly profit and 25 times their expected future profit. A multiple like that just means the price divided by the yearly profit number. To justify a 2 trillion dollar price tag at those same multiples, Anthropic would need to be earning somewhere between 59 billion and 79 billion dollars a year. It currently earns nowhere near that.

None of this means Claude goes away tomorrow. But it is a real signal to watch: a company priced for profits it has not shown yet is under more pressure to either grow into that price fast or eventually reset it, and either path can shape pricing and how much Anthropic invests in the tools you use daily.

Anthropic isn’t making money yet.
via reddit r/ArtificialInteligence →
03 Insights

Write to learn, not to teach, says one blogger's rule

A developer's rule: only publish what teaches you something while you write it.

Outside your usual reading: this is a software engineer's essay on why he only publishes posts about things he does not yet fully understand, and it is a direct nudge for your own Exploded View writing process. His claim: the posts worth publishing are the ones that teach the writer something, not the ones that just repeat what he already knew going in.

His rule of thumb: every post he publishes represents at least two things he learned, the thing that made him want to write it, and the thing he discovered while actually writing it. If he does not learn something new in the writing, he says the post is not interesting enough to publish. He gives examples. A post about AI geolocation prompts started as "most AI prompts probably do not work" and ended with the discovery that newer OpenAI models had lost an older model's (o3) ability to guess a photo's location. A post about C2PA (a system for labeling whether a photo or video is authentic) started as "this needs near universal adoption to work" and turned into a real education on public key infrastructure, the system of digital keys that proves who created a file, and how people manage private keys on their own devices. A post about the Luddites started with the idea that the movement was leaderless and spread out, and ended up describing a culture that was more elitist, sexist, and violent than the popular history books admit.

The mechanism, he argues, is that every post has to argue a specific point. He throws out any draft that "nobody sensible could disagree with." That rule forces him to find the sharpest version of his own position and do enough digging to defend it against the obvious counterargument. He compares it to writing poetry: it is easier to write inside a strict structure, like rhyme, than to just "write what you feel," because the structure narrows an impossible number of choices down to a workable few. Writing itself, he says, is the actual thinking. It is easy to believe you understand a topic while it is still just floating around in your head. The moment you have to turn it into sentences, you find out exactly how much you do not understand. He says he constantly stops mid-sentence and thinks, in his words, "is that really true?" and that his conclusion, by the time he reaches it, is usually sharper than his opening paragraph.

He is upfront that this raises a fair question: is it irresponsible to publish on topics you are still learning, rather than leaving that to the historians and specialists? He gives three answers. First, a beginner sometimes writes a clearer introduction than an expert. Second, the public consensus on a topic is sometimes flatly wrong, and a little digging is enough to show it: he points to the widely repeated claim that each AI prompt uses about 500ml of water as absurd on inspection, to a popular Apple research paper being misread as proof AI models cannot really reason when it was actually measuring something else, and to the common claim that AI chips wear out within three years, when in practice they last longer and AI companies are running healthy profit margins on the running-the-model business. Third, he keeps his real name, background, and resume visible on his site, so no reader could mistake him for an authority he is not.

For your own writing, the takeaway is not "publish more first drafts." It is closer to a filter: if a piece does not force you to learn or resolve something you were not sure of when you sat down to write it, it is probably not worth publishing, and the fix is not more editing, it is picking a sharper claim to defend before you start.

If I write a draft that nobody sensible could disagree with, I scrap the draft.
via Sean Goedecke's blog →

A locked account shows what happens when a compliance bot errs

An automated sanctions check locked a developer out of Apple, even after he proved who he was.

Outside your usual reading: this is a software developer's account of getting locked out of his own Apple developer account by an automated compliance check, and it is a clean, real case study in what happens when an automated system makes a wrong call and there is no clear way to appeal it.

The writer, Sean Byrne, was denied access to Apple's App Store Connect (the dashboard developers use to publish and manage apps) after Apple decided he matched a name on a U.S. government restricted-party list. Apple's message to him was blunt: "The information you provided fully matches one or more restricted parties on the U.S. government consolidated screening list or another government's sanctions list." Apple already had his passport on file. He replied with his full legal name, Sean Joseph Byrne, uploaded his driver's license, and pointed out that the address on the government record was one he had never lived at, in County Sligo, Ireland, a county he has no connection to. As of writing, Apple has not replied.

The government list in question is the Consolidated Screening List, a U.S. tool that combines several export-control and sanctions lists from the Departments of Commerce, State, and Treasury. Searched for "Sean Byrne," it returns exactly one entry: a name tied to Cloonmull House, Drumcliffe, County Sligo, added July 21, 2009, sourced from the Commerce Department's Entity List. That entry carries a "presumption of denial" for any export license request involving that person, and a note that "all items subject to the EAR" apply, meaning the Export Administration Regulations, the rules that govern what U.S. companies are allowed to ship abroad. It is an export-control flag, not a general sanctions list, and it says nothing about who can be hired or who can sell shares.

Here is the twist: the "Sean Byrne" on that list does not appear to be a real person. The entry traces back to the 2009 prosecution of Mac Aviation, a small Irish aircraft-parts business run by a father and son, Thomas and Sean McGuinn, out of a cottage in Sligo. The Department of Justice originally named Sean Byrne as Mac Aviation's commercial manager and charged him alongside the McGuinns over the illegal export of U.S. aircraft equipment. But Mac Aviation had invented employees to look bigger than it actually was, signing paperwork with false names to impress suppliers, and "Sean Byrne" was one of those invented names. It appeared on so much company paperwork that U.S. investigators became convinced the person existed and tried to indict him. By the time DOJ filed a superseding indictment in 2010, Sean Byrne was gone as a defendant. That later filing describes "Sean Byrne" as an alias used by one or more of the real conspirators. Cloonmull House itself was simply Thomas McGuinn's home and Mac Aviation's mailing address. The Entity List entry still lists just a common Irish name and an address that belongs to someone else's house.

Apple already had the passport, received the driver's license and a detailed written explanation, and still told him he "fully" matched a restricted party, with no next step offered.

The lesson worth keeping is not about Apple specifically. It is that an automated compliance system built on a stale government list can lock a real person out of real infrastructure, and unless the company on the other end has a working human escalation path, there may be no way back in.

They already had my passport.
via conic.al →

Two paths to AI reasoning: adjustable thinking versus open weights

Claude 3.7 Sonnet lets you set how long it thinks before answering. DeepSeek R1 is a free, downloadable model (its files are public, so anyone can run it) with 671 billion total settings, called parameters, that reasons nearly as well by training hard on problem solving. A smaller version trained to copy the big one, a process called distillation, beat OpenAI's o1-mini on math and coding.

via Business Analytics Review →
04 Learnings

OpenAI's own field notes on cheaper, faster AI agents

OpenAI's own field notes on what actually saves money running AI agents.

This is on your desk because it is a direct playbook for exactly the kind of agent work you are doing with career_coach and Exploded View: OpenAI collected the actual lessons startups learned running its newest model family, GPT-5.6, in production, and most of them are about spending less to get the same or better results.

The headline finding is that a cheaper setting can now beat a more expensive one. On OpenAI's "Agents' Last Exam" test, GPT-5.6 Sol running at "low" thinking effort outperformed the previous model, GPT-5.5, running at its high thinking effort, with everything else held the same. On BrowseComp, a test that measures how well a model can search out obscure facts, GPT-5.5 at its most thorough setting scored 84.36 percent three months ago for a total run cost of $33.27. At launch, the new GPT-5.6 Luna model matched that score, 84.04 percent, for $1.33, roughly a 25-times price drop for the same result. The practical move for you: before reaching for the most expensive model or the highest thinking-time setting on a task, test whether a cheaper one now matches it. The old rule of always using the flagship model at maximum effort for anything hard no longer holds by OpenAI's own account.

The guide also gives a concrete pattern for when to use small versus large models. It describes a legal-tech startup that parses handwritten memos before doing any real analysis on them. Instead of running the expensive flagship model across the whole job, the startup uses a small, fast model, called Terra or Luna, just for the extraction step, the mechanical work of reading and pulling out data, and saves the expensive model for the judgment calls afterward. That is a template worth stealing for your own agent work: split a task into mechanical extraction and judgment, and only pay flagship prices for the judgment half.

Two specific technical features stood out. First, reasoning continuity: OpenAI now lets a model's internal reasoning carry over between turns, plus a feature called native compaction that compresses a long-running conversation automatically, so the agent does not lose the thread as the conversation grows. Second, native multi-agent orchestration: a lead agent can now split a complex task and hand pieces to several subagents running at the same time, then merge their answers back into one final result.

The takeaway for your own build: test a cheaper model and a lower thinking-effort setting before defaulting to the expensive one, and split mechanical work from judgment work.

GPT‑5.6 Sol at “low” reasoning outperformed GPT‑5.5 at “high” reasoning when the harness was kept constant.
via OpenAI →
05 Tools & Craft

A new local AI model already replacing paid subscriptions

A new AI model called Qwen 3.8 27b (27 billion settings, or parameters) was just released, and Reddit users say it is already good enough to replace their paid AI subscriptions when run on their own machine. It is not at the very top of the pack, but the post argues more work will shift from the cloud to local computers by the end of the year.

via Reddit r/ArtificialInteligence →

OpenAI previews a mode that answers 14 times faster

OpenAI is previewing Ultrafast, a mode that runs its GPT-5.6 Sol model up to 14 times faster than normal, generating up to 750 chunks of text per second using special chips from Cerebras. It is aimed at fast-moving jobs like reading application logs during an outage, a sign AI labs are now competing on speed as much as raw intelligence.

via OpenAI →

A writer built a working Breakout game with Claude in five minutes

A TechRadar writer says they used Claude to build a playable clone of the classic game Breakout in five minutes, start to finish. There are no further details in what came through beyond that headline, but it is a quick, concrete data point on how fast AI coding tools can now produce a small working game.

via TechRadar →
06 Key News

Pittsburgh AI security firm quadruples its office space

A Pittsburgh based AI security company just quadrupled the size of its office and says it plans to double its staff. It's a sign that AI security jobs and investment are growing outside the usual tech hubs.

via Google News →

Defense Intelligence Agency plans agent to agent operations

The Defense Intelligence Agency's AI chief says the agency is planning for AI agents (tools that can take several steps on their own) to talk directly to other AI agents in support of military operations. It shows agent to agent systems moving well past the office, into government and defense use.

via Google News →

AI tested for spotting body wide disease from eye scans

Researchers are testing whether AI can catch early signs of disease elsewhere in the body just by reading a scan of the retina, the light sensing layer at the back of the eye. It's a concrete case of AI catching patterns doctors might otherwise miss.

via Google News →

Some Claude users cancel over Anthropic's new AI watermark

Some Claude subscribers say they are canceling their plans over Anthropic's new AI content watermark. It's worth watching since he's a Claude Max subscriber himself, a live read on what's frustrating paying users right now.

via Google News →
The Last Word
Automate the check, and you also automate the lockout.
The Desk Report

How this edition came together — from bookmarks and feeds to the page.

218links gathered
40read by the desk
14made the edition

Where they came from

On the cutting-room floor — 26 links read but not run this week

Quality over volume: most links get a second look and a pass. The ones that made it earned their place.

Reading Room — every Sunday

The week's AI signal in 16 minutes — what happened, why it matters, and what to do with it. Curated by someone who actually builds, not a feed algorithm.