Tag: software-engineering
All the articles with the tag "software-engineering".
-
AI Tool Note 1 ReferencesSelf-Improving Agents Need a Judge Outside the Loop
A self-improving AI agent without an external judge is just a machine for producing cleaner mistakes. Why autonomous improvement loops need strict human and technical boundaries.
-
AI Tool Note 3 ReferencesUse HTML to Review Agent Output, Not to Replace the Contract
HTML is great for reviewing complex AI agent outputs, but dangerous as a system of record. Learn why the final decision must always export back to Markdown or JSON.
-
AI Market Watch 3 ReferencesStateless MCP Servers Can Still Leak Shared State: A Security Contract
An HTTP endpoint might be stateless, but your MCP server might not be. Learn how shared object state in AI agent infrastructure can silently leak data across clients.
-
AI Tool Note 3 ReferencesThe Work Disk Contract: Managing Artifacts in AI Coding Agents
AI coding agents generate artifacts like builds, tests, and logs. Discover why defining a strict 'Work Disk Contract' is crucial to prevent operating system failures and lost evidence.
-
Field Log 3 ReferencesVercel Is Not a Deployment Contract
A Coolify migration audit exposed two hidden Vercel assumptions: rewrites that only existed in vercel.json and a build script that depended on a Unix shell. Learn how to verify your deployment contract.
-
AI Explainer 3 ReferencesHow to Stop AI Agents From Losing Their Memory: The Operating Structure
Long LLM prompts are not operating memory. Learn how to build an artifact-driven memory stack with source notes, specs, and searchable indexes for autonomous AI agents.
-
AI Explainer 3 ReferencesSoftware 3.0 Is a Verification Problem
The useful Software 3.0 lesson is not that LLMs replace engineering. It is that faster generation moves the bottleneck to context, review, and evidence.
-
About 0 ReferencesAbout Vibecode Town: A Field Log for AI-Assisted Software Engineering
Vibecode Town is an evidence-backed field log tracking AI-assisted software development, agentic workflows, and technical contracts. We focus on verifiable proof, not AI hype.
-
Field Log 3 ReferencesFrustration Is a Signal, Not the Specification: Engineering Agentic Boundaries
Don't just vent at your AI agent when it makes a mistake. Turn repeated frustration into a strict technical contract, a verifier, and a durable test.
-
AI Explainer 3 ReferencesWhat Vibe Coding Actually Is: Exploration vs Production
Vibe coding is useful for exploration, but production work starts when intent becomes a technical contract the agent can verify against.