top10.dev

𝗛𝗡'𝘀 𝗔𝗽𝗿𝗶𝗹 𝟮𝟬𝟮𝟲 𝗵𝗶𝗿𝗶𝗻𝗴 𝘁𝗵𝗿𝗲𝗮𝗱𝘀 𝗷𝘂𝘀𝘁 𝗱𝗿𝗼𝗽𝗽𝗲𝗱. 𝗧𝗵𝗲 𝘀𝗶𝗴𝗻𝗮𝗹-𝘁𝗼-𝗻𝗼𝗶𝘀𝗲 𝗿𝗮𝘁𝗶𝗼: "Who is hiring?" → 147 points "Who wants to be hired?" → 34 points A 4.3:1 ratio — employer demand still outpacing visible candidate supply. No recruiters, no job boards, just teams with open headcount. The monthly pulse check for the dev job market. #hiring #techjobs →

@ClaudeCode's leaked source has been dissected across 3 repos (~𝟮𝟬𝗸 combined @github stars) — and the most interesting finding isn't credentials or secrets. It's that @AnthropicAI's production agent architecture is a while-loop with tool dispatch. The real complexity? Dynamic system prompts and behavioral constraints baked into JSON Schema tool definitions. The moat was never the scaffolding. #LLM #AIcoding

Four astronauts are heading to the Moon for the first time since 1972 — on 𝟯.𝟯𝗠 lines of code running on a 400 MHz radiation-hardened processor. @orion's flight software uses triple-redundant voting (cosmic ray bit-flips are a real failure mode), deterministic time-triggered Ethernet (no TCP/IP — out-of-order delivery could be fatal), and store-and-forward networking for 2.6s round-trip latency. The constraints that shaped this stack are a masterclass in fault-tolerant design. #FaultTolerant #SpaceExplorer → top10.dev/story/artemis-… @artemis @NASA

@Forbes compiled every @OpenAI deal, product, and partnership that was announced but never shipped — and the list is longer than most devs realize. From the Jony Ive hardware collab to the AI browser to robotics bets, the gap between press releases and production is widening. If you're building on the @OpenAI API, the core inference stack is solid. But if you've made architectural bets on announced-but-unshipped features, this is your risk register. #openai #ai

The nonprofit made a deal: equity upside later, control surrender now. PBC law ensures fiduciary duty favors growth over values. That choice—not compromise—reveals everything. → top10.dev

HN sees this as necessary for Stargate scale. r/programming's cynical take: the nonprofit's equity is optics—control went to the PBC's cap table. Both miss the obvious: this was always the endgame, just delayed by legal constraints.

OpenAI's PBC move isn't a mission shift—it's capital-structure pragmatism. $𝟰𝟬𝗕 SoftBank unlock, IPO path clear, nonprofit gets a golden-handcuff equity stake. The structure bent because growth demanded it, not principle.

The subtext is brutal: when developers reverse-engineer your product just to understand it, your product has a trust problem. Healthy sign of demand. Unhealthy sign of transparency. The market is speaking. → top10.dev

Now when Claude Code makes a choice, developers can trace it. Why that refactor? What triggered the retry? Which code path was taken? Suddenly, black-box magic becomes debuggable. Behavior becomes predictable. Trust becomes possible.

𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗶𝘀 𝗲𝘃𝗲𝗿𝘆𝘄𝗵𝗲𝗿𝗲. 𝗜𝘁'𝘀 𝗮𝗹𝘀𝗼 𝗮 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗯𝗹𝗮𝗰𝗸 𝗯𝗼𝘅. You feed it code, it returns refactors/builds/debugs, you ship. But the actual decision logic? Hidden. The routing? Unknown. The constraints? Invisible.

Anthropic now has a choice: treat this as a security breach or own transparency as a strength. The code reveals discipline, not secrets. Publishing it officially would build trust without hurting anything → top10.dev

This changes debugging. When Claude Code fails, you're no longer guessing blindly. You see which provider failed, why it fell back, when retries gave up. Errors shift from mystery to understanding.

Claude Code was the ultimate black box. You typed commands, it synthesized code, it worked. But how? Why did it fail sometimes? What's happening under the hood? Nobody knew. Anthropic sealed the internals shut.

We optimized npm for speed over everything. No friction, no gates, no security checks. Supply chain attacks aren't a bug in this system—they're the obvious outcome. We chose velocity. Here's the bill. → top10.dev/story/axios-co…

Devs are now auditing lockfiles. Running forensic scans. Realizing npm audit fails here. The contract changed overnight: npm install is no longer enough. You need supply chain scanning to ship safely.

𝟱𝟬𝗠 Axios downloads per week. You npm install without thinking. The entire JavaScript ecosystem runs on this assumption: the registry is safe. That assumption just got very expensive.

Noncompetes are an employer tax on worker mobility. Washington got this right—ban them entirely. Labor is your only asset. You should be able to use it. → top10.dev

For engineers: you can accept a competitor's offer without lawyers threatening you. Negotiate freely. Leave without worrying about a five-year revenge clause. That's the job market you should have always had.

Noncompetes were career prison. Even Washington's 2020 law only fixed it for salaried engineers—contractors and junior devs were still locked in. Your job offer meant nothing if your old contract said you couldn't compete.