Start.dev

This is f*cking insane. Boris Cherny, the man who built Claude Code, was asked if people should still learn to code. His answer: "In a year or two, it's not going to matter" In 73 seconds, he explains what to do instead: play with the AI tools, learn them, don't be scared of them, stay on the frontier On his team, everyone codes now. The PM, the designer, even the finance guy He hasn't edited a single line of code by hand since last November. He ships 10 to 30 pull requests a day Writing Code → Prompting → Agents → Harness → Loops → Everyone on the Team Ships Claude Code is a harness: the tools, memory, rules and loops around the model. His team changes it with every new model and cut 80% of its system prompt Save this before it disappears from your feed Every doc, guide and repo below is free: Claude Code best practices code.claude.com/docs/en/best… Effective harnesses for long-running agents anthropic.com/research/effec… Building effective agents anthropic.com/research/build… Claude Code docs code.claude.com/docs/en/over… Memory: how Claude remembers your project code.claude.com/docs/en/memo… Custom subagents code.claude.com/docs/en/sub-… Hooks: rules the agent can't skip code.claude.com/docs/en/hook… Skills code.claude.com/docs/en/skil… Run Claude Code on a schedule code.claude.com/docs/en/rout… Free course: Claude Code in Action anthropic.skilljar.com/claud… Claude Code on GitHub github.com/anthropics/claude… Claude Code inside your PRs and issues github.com/anthropics/claude… Build your own agent on the same harness github.com/anthropics/claude… The best Claude Code resources in one list github.com/hesreallyhim/awes… Plugins, agents and skills for Claude Code github.com/wshobson/agents He compares it to the printing press. Writing went from a few scribes to everyone. Building software is next 95% will keep asking whether to learn to code, the 5% who build a harness will ship 30 pull requests a day Bookmark it and read the first link tonight Then use the guide below to build your harness before everyone else does ↓

Is coding still worth learning in the AI era?

AI coding is getting so strong that programming is basically just chatting now. Given that, is it still worth learning fundamentals like data structures, algorithms, and how computers actually work?

the weirdest career advice in tech right now: > learn to code. > don’t learn to code, AI does it. > learn AI. > AI will automate AI. > build a startup. AI already built your idea. bro can someone just tell me what to do on monday?

Disengaging from syntax is not disengaging from engineering. I’m working on a significant project at the moment. It’s in a pre-production state so far. More than a prototype, less than ready for real users. I’ve been making multiple passes over the structure for each of the following concerns: Architecture, coverage, race & concurrency, security, API, etc. Each of these requires significant interrogation and review of verification procedures; but not review of the code. At base are the /ub-mode (GitHub.com/unclebob) rules that keep the agents disciplined as far as coding structure and tests are concerned. But above that it’s me making sure that all the bases are covered well enough to keep my client safe from stupid sloppy mistakes. I am the engineer. I am responsible. The agents are just my tools. They are power tools, to be sure. But power tools in the hands of novices result in missing fingers. So I am very careful.

I'd wager that 99% of companies do NOT need a "software factory." They just need to figure out WHAT to fix, and WHAT to build. This example - Substack's search has been poor since forever, never addressed, even though it's easy to fix now (in hours, max days) a good example

"What the smartest people (or nerds) do on the weekend is what everyone else will do during the week in ten years."

Real vibe coding now is writing code by hand without any AI help.

The industry is changing SO FAST not just with development practices changing, but also how we learn changing. There are no programming video tutorials because it's not how most of us build any more. There are FAR more examples of ridiculously ambitious sw built eg via @poteto

Memory is what allows Claude to learn from experience. In a new Engineering Blog post, we share how “dreaming” helps Claude organize what it’s learned, correct its mistakes, and find what it needs more easily the next time. anthropic.com/research/compo…

For startups that have open source projects, I’m increasingly hearing that before posting positions they just ping top contributors to see if they can hire them Those contributors proved they know how to do the day-to-day work in ways better than an interview would prove. Plus they know what the product does, are motivated to help etc

Tip: Switch Claude Code's output style to Concise to get short, straight-to-the-point results. Enable it via /config → Output style, or add "outputStyle": "Concise" directly to your settings.json. You can still get the full details when you ask.

Copy pasting between Claude and Codex is the 2026 equivalent of copying pasting from Stack Overflow