Python still owns the models. TypeScript ate the application layer. Here’s why — and what it means for what you build next. Table Of Contents The framing nobody puts on the cover If you read tech headlines in late 2025 and early 2026, you’ve probably seen the claim that TypeScript “overtook Python” or “won AI.” […]
Read More →The ecosystem of “AI skills” — modular instruction packs that extend an LLM with task-specific know-how, whether they’re called Skills, plugins, agents, MCP servers, system-prompt templates, or tool bundles — has exploded fast enough that “which one should I use?” has become the dominant question. The answer is rarely obvious from a README, and almost […]
Read More →Specs and change proposals live in the repo; Jira still owns Epics, Stories, and the board. You can do both without maintaining two truths: tie one OpenSpec change folder to one Story, leave tasks.md out of Sub-tasks, and link every ticket to openspec/changes/…. Most organizations will not retire Jira; this split is how you get SDD anyway without […]
Read More →“Most people are using MCP wrong,” said MCP’s co-creator, David Soria Parra. I agree. Because I made the same mistake. Engineers would do the obvious thing: wrap each REST endpoint as an MCP tool and shove them into a custom registry. The result? Zero value over just calling the APIs directly. Worse than zero, honestly. […]
Read More →Chrome shipped something quietly huge. Your real, signed-in browser can now be natively accessible to any coding agent. No extensions. No headless browser. No screenshots. No separate logins. One toggle. Here’s the official blog post from the Chrome team. The actual unlock people are glossing over I keep seeing reactions focused on “browser control” and […]
Read More →