Skip to main content

4 posts tagged with "agents"

View all tags

Spec-Driven Development: is it the solution to Vibe Coding?

· 13 min read
Rafael Fernandes
NLP Engineer & Tech Writer at WiLine
Share:
Engineering practice · AI News

Spec-driven development, tested

Write the promptWrite the contract

Someone posted spec-driven development on LinkedIn this week as the answer to vibe coding — to prompting an agent, half-understanding what you're building, and ending up with code you can't vouch for. The linked toolkit has 127,000 stars and comes from GitHub itself. The pitch lands.

So I installed it and pointed it at a deliberately trivial task. One of the three principles it wrote for me was a dependency policy I never asked for — hold that thought.

Twenty minutes isn't a verdict, though. Two engineers have tested this properly, on real problems, long enough for the seams to show. They used different tools, on different continents, seven months apart — and both reached for the same comparison, unprompted: the last time our industry tried to generate working code from documents. On the one question that decides whether any of this survives contact with AI features, they flatly contradict each other. Neither has a measurement.

Muse Glimmer: a 30B agentic model that runs on one GPU, no data center required

· 4 min read
Rafael Fernandes
NLP Engineer & Tech Writer at WiLine
Share:
Models · AI News

A serious agent, no data center required

Cloud-only agentsOne GPU, fully local

Most "run it locally" model announcements come with an asterisk — smaller, weaker, a toy version of the real thing. Meta's newest release doesn't: Muse Glimmer, a 30B multimodal model built specifically for agentic work, fits on a single consumer GPU and beats larger models on the benchmarks that actually measure agent behavior.

'Loop Engineering Is Dead' — and the Real Story Is Weirder Than the Obituary

· 13 min read
Rafael Fernandes
NLP Engineer & Tech Writer at WiLine
Share:
Architecture · AI News

Loops, graphs, and the six-week obituary

Loop engineeringGraph engineering

In June 2026, the AI world got a new buzzword: loop engineering — roughly, disciplined design of a single agent's tool-calling loop. Six weeks later it was supposedly replaced by graph engineering — wiring up several agents at once — killed by twelve words that 3.1 million people saw:

Don't know what loop engineering is? Don't worry — neither did most of the people declaring it dead. Here are both terms, how a name became an obituary in six weeks, and the twist nobody checked before writing about it.

MCP Just Shipped Its Biggest Update Ever — Here's What Actually Changes for AI Agent Engineers

· 5 min read
Rafael Fernandes
NLP Engineer & Tech Writer at WiLine
Share:
Protocols · AI NewsModel Context Protocol — the 2026-07-28 specification

The Model Context Protocol just had its biggest revision since launch. The 2026-07-28 specification doesn't add a feature — it rewrites how every MCP server talks to every client. If you've deployed an MCP server anywhere past "runs on my laptop," this one touches your infrastructure, not just your changelog.