Content Topics
These topic tags help organize content within the main categories. Unlike categories, these are informative metadata that help with content discovery but do not represent main content silos.
Conceptual Topics
Tool Topics
Format Topics
acceptance-criteria
- The spec is the contract: what that means in practice(July 20, 2026)
- Reading a repo into product artifacts: stories, criteria, decisions(July 20, 2026)
- Spec-driven without the overhead: a lightweight workflow(July 20, 2026)
- Done means done: making agents prove completion(July 20, 2026)
- Acceptance criteria agents can actually verify(July 20, 2026)
agent-memory
agentic-development
- What is vibe coding? (and where it stops working)(July 20, 2026)
- The local software factory: product, code and evidence on your machine(July 20, 2026)
- Adding specs to an existing codebase without stopping the world(July 20, 2026)
- Spec vs PRD: what each one is for (and what agents need)(July 20, 2026)
- Spec drift: why your spec and your code stop telling the same story(July 20, 2026)
- Local-first AI development: why the factory should live on your Mac(July 20, 2026)
- Living specs: specifications that update with the code(July 20, 2026)
- Spec-driven without the overhead: a lightweight workflow(July 20, 2026)
- Beyond Spec Kit: what spec-driven needs after the spec is written(July 20, 2026)
- Acceptance criteria agents can actually verify(July 20, 2026)
- Software specifications should be portable(July 16, 2026)
agents
- The run died at 2am: recovery as a first-class workflow(July 20, 2026)
- Running eight sessions: worktrees, parallelism and the cost of being the scheduler(July 20, 2026)
- Onboard against the graph, not tribal knowledge(July 20, 2026)
- Orchestrating multiple coding agents without them poisoning each other(July 20, 2026)
- Memory for coding agents: what should persist outside the chat(July 20, 2026)
- Your rules file is lying to your agents: keeping instructions alive(July 20, 2026)
- Harness engineering: the discipline forming around agent operations(July 20, 2026)
- Compaction eats your decisions: managing the context window on long work(July 20, 2026)
- Context loss between sessions: the productivity killer nobody budgets for(July 20, 2026)
- Codebase maps, not bigger prompts(July 20, 2026)
- Code knowledge graphs: what they are and why agents need them(July 20, 2026)
- Building software with AI agents: the operating guide(July 20, 2026)
- Agents will drift: engineering for divergence instead of praying against it(July 20, 2026)
- AGENTS.md, CLAUDE.md, cursor rules: where your decisions should actually live(July 20, 2026)
- Handoffs: passing work between agents without losing the plot(July 20, 2026)
- You do not have a Claude Code problem. You are the runtime.(June 16, 2026)
agents-md
agents-will-drift
ai-agents
- A factory of one: shipping serious software as a solo founder(July 20, 2026)
- PAELLADOC now has inference benchmarks(July 17, 2026)
ai-architectures
- Architecture patterns for AI systems(May 04, 2025)
ai-assisted-engineering
ai-coding
- When to add tests and architecture to an AI-built project(July 20, 2026)
- What is vibe coding? (and where it stops working)(July 20, 2026)
- Vibe coding vs AI-assisted engineering: the line that matters(July 20, 2026)
- From vibe coding to production: the bridge nobody explains(July 20, 2026)
- Vibe coding debt: what you actually owe and when it's due(July 20, 2026)
- The security holes vibe coding leaves behind(July 20, 2026)
- The 90-day reckoning: why vibe-coded apps break at month 3(July 20, 2026)
- Verifying AI-generated code: evidence, not vibes(July 20, 2026)
- Verification loops: hooks, gates and the end of self-reported success(July 20, 2026)
- You shipped code you can't read. Now what?(July 20, 2026)
- Tribal knowledge is a single point of failure(July 20, 2026)
- The local software factory: product, code and evidence on your machine(July 20, 2026)
- Testing AI-generated code: what changes and what doesn't(July 20, 2026)
- Adding specs to an existing codebase without stopping the world(July 20, 2026)
- Spec vs PRD: what each one is for (and what agents need)(July 20, 2026)
- Reviewing specs before agents build: the cheapest review you will ever do(July 20, 2026)
- Spec-driven vs test-driven: rivals or layers?(July 20, 2026)
- Spec drift: why your spec and your code stop telling the same story(July 20, 2026)
- The spec is the contract: what that means in practice(July 20, 2026)
- From production to assurance: the new bottleneck in software(July 20, 2026)
- Scared to touch it: turning fear of your own codebase into a safety net(July 20, 2026)
- Test the riskiest assumption before the agents build the whole thing(July 20, 2026)
- Reviewing code you didn't write: scope first, diff last(July 20, 2026)
- Reading a repo into product artifacts: stories, criteria, decisions(July 20, 2026)
- Your Lovable prototype is now the product: surviving the promotion(July 20, 2026)
- Prototype as spec: impossible to misinterpret(July 20, 2026)
- Product memory: what your team forgets and your system shouldn't(July 20, 2026)
- Product discovery with AI: partner for thinking, not for deciding(July 20, 2026)
- Decision logs: ending the "I never agreed to that" problem(July 20, 2026)
- You write PRDs nobody reads. The artifact is the problem.(July 20, 2026)
- The PM–engineering bridge: one system from discovery to merged code(July 20, 2026)
- Memory for coding agents: what should persist outside the chat(July 20, 2026)
- Local-first AI development: why the factory should live on your Mac(July 20, 2026)
- Living specs: specifications that update with the code(July 20, 2026)
- Living documentation: docs that stop rotting(July 20, 2026)
- Spec-driven without the overhead: a lightweight workflow(July 20, 2026)
- Knowledge graph vs vector search for code: when each one wins(July 20, 2026)
- Insight → decision → outcome: the chain AI speed keeps breaking(July 20, 2026)
- Every new feature breaks an old one: the missing contract(July 20, 2026)
- "Tests pass": anatomy of a false success claim(July 20, 2026)
- Product decisions with evidence attached(July 20, 2026)
- Evidence-based development: closing work with proof attached(July 20, 2026)
- Done means done: making agents prove completion(July 20, 2026)
- Docs-as-code in the agent era(July 20, 2026)
- A definition of done that survives AI speed(July 20, 2026)
- Controlling AI costs when every task can burn tokens(July 20, 2026)
- Context loss between sessions: the productivity killer nobody budgets for(July 20, 2026)
- Codebase maps, not bigger prompts(July 20, 2026)
- Your code never leaves: privacy as an architecture decision(July 20, 2026)
- Code knowledge graphs: what they are and why agents need them(July 20, 2026)
- Cloud vs local AI dev tools: what you trade in each direction(July 20, 2026)
- Building software with AI agents: the operating guide(July 20, 2026)
- Beyond Spec Kit: what spec-driven needs after the spec is written(July 20, 2026)
- AI-assisted user research without laundering your evidence(July 20, 2026)
- AI slop with a nice format: the failure mode of AI-assisted product work(July 20, 2026)
- An operating model for product teams that build with agents(July 20, 2026)
- The trust gap: why output stopped being the bottleneck(July 20, 2026)
- Review fatigue: when code arrives faster than you can read it(July 20, 2026)
- Acceptance criteria agents can actually verify(July 20, 2026)
- Software specifications should be portable(July 16, 2026)
- I asked the Codex app to build an app twice. Neither made it to tomorrow.(July 11, 2026)
- Product knowledge graph: read your product's shape, not the repo's feature list(June 20, 2026)
- Product management in the AI era: building got cheap, deciding got expensive(June 19, 2026)
- You do not have a Claude Code problem. You are the runtime.(June 16, 2026)
- No vendor lock-in: route every task to the right engine(June 14, 2026)
- The product brain that maintains itself(June 12, 2026)
- What is spec-driven development?(June 07, 2026)
- Spec-driven development: a green build is not a correct feature(June 07, 2026)
- Locally correct, globally incoherent: the real problem with AI-generated code(June 07, 2026)
ai-cost-control
- Controlling AI costs when every task can burn tokens(July 20, 2026)
ai-discovery
ai-first-development
- Architecture patterns for AI systems(May 04, 2025)
- AI-first development framework: context, execution and evidence(April 27, 2025)
- Securing AI code with Snyk: A practical guide(April 17, 2025)
- When faster AI coding does not improve delivery(April 16, 2025)
- Why AI-generated code becomes hard to maintain(April 14, 2025)
- Principles for maintainable AI-assisted development(April 12, 2025)
- PaellaDoc and context in AI-assisted development(April 08, 2025)
ai-models
- PAELLADOC now has inference benchmarks(July 17, 2026)
ai-slop-product
api-keys
apple-silicon
- Why native on macOS still matters for developer tools(July 20, 2026)
architecture
- When to add tests and architecture to an AI-built project(July 20, 2026)
building-with-agents
- Building software with AI agents: the operating guide(July 20, 2026)
byo-model
characterization-tests
checkpoints
- The run died at 2am: recovery as a first-class workflow(July 20, 2026)
claude-code
- You do not have a Claude Code problem. You are the runtime.(June 16, 2026)
claude-md
cloud-vs-local
code-review
codebase-maps
- Codebase maps, not bigger prompts(July 20, 2026)
- Code knowledge graphs: what they are and why agents need them(July 20, 2026)
codebase-understanding
- You shipped code you can't read. Now what?(July 20, 2026)
codex
compaction
compass
context
context-engineering
context-loss
context-preservation
- AI-first development framework: context, execution and evidence(April 27, 2025)
- Principles for maintainable AI-assisted development(April 12, 2025)
- PaellaDoc and context in AI-assisted development(April 08, 2025)
context-window
continuous-integration
contract
- The spec is the contract: what that means in practice(July 20, 2026)
cursor-rules
data-ownership
- Your code never leaves: privacy as an architecture decision(July 20, 2026)
decision-logs
decision-making
- Insight → decision → outcome: the chain AI speed keeps breaking(July 20, 2026)
- Product decisions with evidence attached(July 20, 2026)
decision-quality
definition-of-done-ai
- A definition of done that survives AI speed(July 20, 2026)
dependencies
- The security holes vibe coding leaves behind(July 20, 2026)
developer-tools
- Tools without accounts: what no-signup design says about a product(July 20, 2026)
- Why native on macOS still matters for developer tools(July 20, 2026)
- Local-first AI development: why the factory should live on your Mac(July 20, 2026)
- Cloud vs local AI dev tools: what you trade in each direction(July 20, 2026)
- PAELLADOC now has inference benchmarks(July 17, 2026)
development-philosophy
- Principles for maintainable AI-assisted development(April 12, 2025)
- PaellaDoc and context in AI-assisted development(April 08, 2025)
discovery
divergence
docs-as-code
- Living documentation: docs that stop rotting(July 20, 2026)
- Docs-as-code in the agent era(July 20, 2026)
done-means-done
- Done means done: making agents prove completion(July 20, 2026)
engineering
engineering-process
- From production to assurance: the new bottleneck in software(July 20, 2026)
evals
evidence
- Product decisions with evidence attached(July 20, 2026)
evidence-based-dev
- Evidence-based development: closing work with proof attached(July 20, 2026)
evidence-based-development
- Verifying AI-generated code: evidence, not vibes(July 20, 2026)
- A definition of done that survives AI speed(July 20, 2026)
execution-gate
existing-codebase
experiments
false-success
- "Tests pass": anatomy of a false success claim(July 20, 2026)
feature-factory
- What is a feature factory?(June 07, 2026)
- Making product means installing a behavior, not running a feature factory(June 07, 2026)
features-breaking-features
- Every new feature breaks an old one: the missing contract(July 20, 2026)
handoffs
harness-engineering
inference-benchmarks
- PAELLADOC now has inference benchmarks(July 17, 2026)
input-validation
- The security holes vibe coding leaves behind(July 20, 2026)
intent-driven-architecture
- AI-first development framework: context, execution and evidence(April 27, 2025)
interoperability
- Software specifications should be portable(July 16, 2026)
knowledge-graph
- Tribal knowledge is a single point of failure(July 20, 2026)
- Reading a repo into product artifacts: stories, criteria, decisions(July 20, 2026)
- Product memory: what your team forgets and your system shouldn't(July 20, 2026)
- Onboard against the graph, not tribal knowledge(July 20, 2026)
- Living documentation: docs that stop rotting(July 20, 2026)
- Knowledge graph vs vector search for code: when each one wins(July 20, 2026)
- Docs-as-code in the agent era(July 20, 2026)
- Code knowledge graphs: what they are and why agents need them(July 20, 2026)
- Product knowledge graph: read your product's shape, not the repo's feature list(June 20, 2026)
- The product brain that maintains itself(June 12, 2026)
knowledge-management
- Why AI-generated code becomes hard to maintain(April 14, 2025)
legacy-code
lightweight-sdd
- Spec-driven without the overhead: a lightweight workflow(July 20, 2026)
living-documentation
- Living documentation: docs that stop rotting(July 20, 2026)
- Docs-as-code in the agent era(July 20, 2026)
living-specs
- Spec drift: why your spec and your code stop telling the same story(July 20, 2026)
- You write PRDs nobody reads. The artifact is the problem.(July 20, 2026)
- Living specs: specifications that update with the code(July 20, 2026)
- Beyond Spec Kit: what spec-driven needs after the spec is written(July 20, 2026)
llm
- No vendor lock-in: route every task to the right engine(June 14, 2026)
llm-behavior
- "Tests pass": anatomy of a false success claim(July 20, 2026)
local-first
- Tools without accounts: what no-signup design says about a product(July 20, 2026)
- The local software factory: product, code and evidence on your machine(July 20, 2026)
- Why native on macOS still matters for developer tools(July 20, 2026)
- Local-first AI development: why the factory should live on your Mac(July 20, 2026)
- A factory of one: shipping serious software as a solo founder(July 20, 2026)
- Your code never leaves: privacy as an architecture decision(July 20, 2026)
- Cloud vs local AI dev tools: what you trade in each direction(July 20, 2026)
local-software-factory
- Tools without accounts: what no-signup design says about a product(July 20, 2026)
- The local software factory: product, code and evidence on your machine(July 20, 2026)
- Local-first AI development: why the factory should live on your Mac(July 20, 2026)
- Your code never leaves: privacy as an architecture decision(July 20, 2026)
- Cloud vs local AI dev tools: what you trade in each direction(July 20, 2026)
macos-native
- Why native on macOS still matters for developer tools(July 20, 2026)
maintainability
- Vibe coding debt: what you actually owe and when it's due(July 20, 2026)
- The 90-day reckoning: why vibe-coded apps break at month 3(July 20, 2026)
- You shipped code you can't read. Now what?(July 20, 2026)
- Foundations under the house of cards: fixing a vibe-coded app without a rewrite(July 20, 2026)
ml-pipeline-security
- Securing AI code with Snyk: A practical guide(April 17, 2025)
- Why AI-generated code becomes hard to maintain(April 14, 2025)
model-portability
model-routing
- Controlling AI costs when every task can burn tokens(July 20, 2026)
- No vendor lock-in: route every task to the right engine(June 14, 2026)
model-selection
- PAELLADOC now has inference benchmarks(July 17, 2026)
multi-agent
no-account
ollama
onboarding
- Tribal knowledge is a single point of failure(July 20, 2026)
- Onboard against the graph, not tribal knowledge(July 20, 2026)
one-person-company
operating-model
- An operating model for product teams that build with agents(July 20, 2026)
orchestration
paelladoc
- When to add tests and architecture to an AI-built project(July 20, 2026)
- What is vibe coding? (and where it stops working)(July 20, 2026)
- Vibe coding vs AI-assisted engineering: the line that matters(July 20, 2026)
- From vibe coding to production: the bridge nobody explains(July 20, 2026)
- Vibe coding debt: what you actually owe and when it's due(July 20, 2026)
- The security holes vibe coding leaves behind(July 20, 2026)
- The 90-day reckoning: why vibe-coded apps break at month 3(July 20, 2026)
- Verifying AI-generated code: evidence, not vibes(July 20, 2026)
- Verification loops: hooks, gates and the end of self-reported success(July 20, 2026)
- You shipped code you can't read. Now what?(July 20, 2026)
- Tribal knowledge is a single point of failure(July 20, 2026)
- Tools without accounts: what no-signup design says about a product(July 20, 2026)
- The local software factory: product, code and evidence on your machine(July 20, 2026)
- Testing AI-generated code: what changes and what doesn't(July 20, 2026)
- Adding specs to an existing codebase without stopping the world(July 20, 2026)
- Reviewing specs before agents build: the cheapest review you will ever do(July 20, 2026)
- Spec-driven vs test-driven: rivals or layers?(July 20, 2026)
- The spec is the contract: what that means in practice(July 20, 2026)
- From production to assurance: the new bottleneck in software(July 20, 2026)
- Scared to touch it: turning fear of your own codebase into a safety net(July 20, 2026)
- Test the riskiest assumption before the agents build the whole thing(July 20, 2026)
- Reviewing code you didn't write: scope first, diff last(July 20, 2026)
- Reading a repo into product artifacts: stories, criteria, decisions(July 20, 2026)
- Your Lovable prototype is now the product: surviving the promotion(July 20, 2026)
- Prototype as spec: impossible to misinterpret(July 20, 2026)
- Product memory: what your team forgets and your system shouldn't(July 20, 2026)
- Product discovery with AI: partner for thinking, not for deciding(July 20, 2026)
- Decision logs: ending the "I never agreed to that" problem(July 20, 2026)
- You write PRDs nobody reads. The artifact is the problem.(July 20, 2026)
- The PM–engineering bridge: one system from discovery to merged code(July 20, 2026)
- Running eight sessions: worktrees, parallelism and the cost of being the scheduler(July 20, 2026)
- Onboard against the graph, not tribal knowledge(July 20, 2026)
- Why native on macOS still matters for developer tools(July 20, 2026)
- Orchestrating multiple coding agents without them poisoning each other(July 20, 2026)
- Memory for coding agents: what should persist outside the chat(July 20, 2026)
- Local-first AI development: why the factory should live on your Mac(July 20, 2026)
- Living documentation: docs that stop rotting(July 20, 2026)
- Knowledge graph vs vector search for code: when each one wins(July 20, 2026)
- Insight → decision → outcome: the chain AI speed keeps breaking(July 20, 2026)
- Foundations under the house of cards: fixing a vibe-coded app without a rewrite(July 20, 2026)
- Every new feature breaks an old one: the missing contract(July 20, 2026)
- "Tests pass": anatomy of a false success claim(July 20, 2026)
- A factory of one: shipping serious software as a solo founder(July 20, 2026)
- Product decisions with evidence attached(July 20, 2026)
- Evidence-based development: closing work with proof attached(July 20, 2026)
- Done means done: making agents prove completion(July 20, 2026)
- Docs-as-code in the agent era(July 20, 2026)
- A definition of done that survives AI speed(July 20, 2026)
- Controlling AI costs when every task can burn tokens(July 20, 2026)
- Context loss between sessions: the productivity killer nobody budgets for(July 20, 2026)
- Codebase maps, not bigger prompts(July 20, 2026)
- Your code never leaves: privacy as an architecture decision(July 20, 2026)
- Code knowledge graphs: what they are and why agents need them(July 20, 2026)
- Cloud vs local AI dev tools: what you trade in each direction(July 20, 2026)
- Building software with AI agents: the operating guide(July 20, 2026)
- Bring your own model: API keys, local engines and staying portable(July 20, 2026)
- Beyond Spec Kit: what spec-driven needs after the spec is written(July 20, 2026)
- AI-assisted user research without laundering your evidence(July 20, 2026)
- AI slop with a nice format: the failure mode of AI-assisted product work(July 20, 2026)
- An operating model for product teams that build with agents(July 20, 2026)
- The trust gap: why output stopped being the bottleneck(July 20, 2026)
- Review fatigue: when code arrives faster than you can read it(July 20, 2026)
- Agents will drift: engineering for divergence instead of praying against it(July 20, 2026)
- PAELLADOC now has inference benchmarks(July 17, 2026)
- Software specifications should be portable(July 16, 2026)
- I asked the Codex app to build an app twice. Neither made it to tomorrow.(July 11, 2026)
- Product knowledge graph: read your product's shape, not the repo's feature list(June 20, 2026)
- Product management in the AI era: building got cheap, deciding got expensive(June 19, 2026)
- You do not have a Claude Code problem. You are the runtime.(June 16, 2026)
- No vendor lock-in: route every task to the right engine(June 14, 2026)
- The product brain that maintains itself(June 12, 2026)
- What is spec-driven development?(June 07, 2026)
- What is a feature factory?(June 07, 2026)
- Spec-driven development: a green build is not a correct feature(June 07, 2026)
- Making product means installing a behavior, not running a feature factory(June 07, 2026)
- Locally correct, globally incoherent: the real problem with AI-generated code(June 07, 2026)
- Architecture patterns for AI systems(May 04, 2025)
- When faster AI coding does not improve delivery(April 16, 2025)
parallel-sessions
prds-nobody-reads
- You write PRDs nobody reads. The artifact is the problem.(July 20, 2026)
privacy
- Your code never leaves: privacy as an architecture decision(July 20, 2026)
product-development
product-graph
product-incentives
product-management
- Test the riskiest assumption before the agents build the whole thing(July 20, 2026)
- Prototype as spec: impossible to misinterpret(July 20, 2026)
- Product discovery with AI: partner for thinking, not for deciding(July 20, 2026)
- Decision logs: ending the "I never agreed to that" problem(July 20, 2026)
- You write PRDs nobody reads. The artifact is the problem.(July 20, 2026)
- The PM–engineering bridge: one system from discovery to merged code(July 20, 2026)
- Insight → decision → outcome: the chain AI speed keeps breaking(July 20, 2026)
- Product decisions with evidence attached(July 20, 2026)
- AI-assisted user research without laundering your evidence(July 20, 2026)
- AI slop with a nice format: the failure mode of AI-assisted product work(July 20, 2026)
- An operating model for product teams that build with agents(July 20, 2026)
- Product knowledge graph: read your product's shape, not the repo's feature list(June 20, 2026)
- Product management in the AI era: building got cheap, deciding got expensive(June 19, 2026)
- The product brain that maintains itself(June 12, 2026)
- What is a feature factory?(June 07, 2026)
- Making product means installing a behavior, not running a feature factory(June 07, 2026)
product-memory
product-outcomes
product-requirements
- Spec vs PRD: what each one is for (and what agents need)(July 20, 2026)
product-research
product-strategy
- What is a feature factory?(June 07, 2026)
- Making product means installing a behavior, not running a feature factory(June 07, 2026)
production
productivity
- When faster AI coding does not improve delivery(April 16, 2025)
prototype-as-spec
- Prototype as spec: impossible to misinterpret(July 20, 2026)
prototype-to-product
- What is vibe coding? (and where it stops working)(July 20, 2026)
- From vibe coding to production: the bridge nobody explains(July 20, 2026)
- The 90-day reckoning: why vibe-coded apps break at month 3(July 20, 2026)
- You shipped code you can't read. Now what?(July 20, 2026)
prototyping
rag
recovery
- The run died at 2am: recovery as a first-class workflow(July 20, 2026)
regression
- Every new feature breaks an old one: the missing contract(July 20, 2026)
reliability
retrieval
reverse-intake
review-fatigue
reviewing-unwritten
- Reviewing code you didn't write: scope first, diff last(July 20, 2026)
riskiest-assumptions
runtime
- The run died at 2am: recovery as a first-class workflow(July 20, 2026)
- Running eight sessions: worktrees, parallelism and the cost of being the scheduler(July 20, 2026)
- Orchestrating multiple coding agents without them poisoning each other(July 20, 2026)
- Memory for coding agents: what should persist outside the chat(July 20, 2026)
- Your rules file is lying to your agents: keeping instructions alive(July 20, 2026)
- Harness engineering: the discipline forming around agent operations(July 20, 2026)
- Compaction eats your decisions: managing the context window on long work(July 20, 2026)
- Context loss between sessions: the productivity killer nobody budgets for(July 20, 2026)
- Building software with AI agents: the operating guide(July 20, 2026)
- Agents will drift: engineering for divergence instead of praying against it(July 20, 2026)
- AGENTS.md, CLAUDE.md, cursor rules: where your decisions should actually live(July 20, 2026)
- Handoffs: passing work between agents without losing the plot(July 20, 2026)
- You do not have a Claude Code problem. You are the runtime.(June 16, 2026)
security
- The security holes vibe coding leaves behind(July 20, 2026)
snyk
- Securing AI code with Snyk: A practical guide(April 17, 2025)
software-architecture
software-assurance
- Verifying AI-generated code: evidence, not vibes(July 20, 2026)
- From production to assurance: the new bottleneck in software(July 20, 2026)
- Evidence-based development: closing work with proof attached(July 20, 2026)
- The trust gap: why output stopped being the bottleneck(July 20, 2026)
software-specifications
- Software specifications should be portable(July 16, 2026)
solo-founder
spec-as-contract
- Every new feature breaks an old one: the missing contract(July 20, 2026)
spec-drift
spec-driven-development
- Vibe coding vs AI-assisted engineering: the line that matters(July 20, 2026)
- From vibe coding to production: the bridge nobody explains(July 20, 2026)
- Adding specs to an existing codebase without stopping the world(July 20, 2026)
- Spec vs PRD: what each one is for (and what agents need)(July 20, 2026)
- Reviewing specs before agents build: the cheapest review you will ever do(July 20, 2026)
- Spec-driven vs test-driven: rivals or layers?(July 20, 2026)
- Spec drift: why your spec and your code stop telling the same story(July 20, 2026)
- The spec is the contract: what that means in practice(July 20, 2026)
- Living specs: specifications that update with the code(July 20, 2026)
- Spec-driven without the overhead: a lightweight workflow(July 20, 2026)
- Foundations under the house of cards: fixing a vibe-coded app without a rewrite(July 20, 2026)
- Building software with AI agents: the operating guide(July 20, 2026)
- Beyond Spec Kit: what spec-driven needs after the spec is written(July 20, 2026)
- Acceptance criteria agents can actually verify(July 20, 2026)
- Software specifications should be portable(July 16, 2026)
- What is spec-driven development?(June 07, 2026)
- Spec-driven development: a green build is not a correct feature(June 07, 2026)
spec-gated-development
- What is spec-driven development?(June 07, 2026)
spec-kit
spec-review
spec-vs-prd
- Spec vs PRD: what each one is for (and what agents need)(July 20, 2026)
specs
- Prototype as spec: impossible to misinterpret(July 20, 2026)
stale-rules
team-process
- An operating model for product teams that build with agents(July 20, 2026)
technical-debt
- When to add tests and architecture to an AI-built project(July 20, 2026)
- From vibe coding to production: the bridge nobody explains(July 20, 2026)
- Vibe coding debt: what you actually owe and when it's due(July 20, 2026)
- The 90-day reckoning: why vibe-coded apps break at month 3(July 20, 2026)
- Foundations under the house of cards: fixing a vibe-coded app without a rewrite(July 20, 2026)
test-automation
- Testing AI-generated code: what changes and what doesn't(July 20, 2026)
test-driven-development
- Spec-driven vs test-driven: rivals or layers?(July 20, 2026)
testing
- When to add tests and architecture to an AI-built project(July 20, 2026)
- Spec-driven vs test-driven: rivals or layers?(July 20, 2026)
- Scared to touch it: turning fear of your own codebase into a safety net(July 20, 2026)
testing-ai-code
- Testing AI-generated code: what changes and what doesn't(July 20, 2026)
token-budget
- Controlling AI costs when every task can burn tokens(July 20, 2026)
tooling
tribal-knowledge
- Tribal knowledge is a single point of failure(July 20, 2026)
- Onboard against the graph, not tribal knowledge(July 20, 2026)
trust-gap
- The trust gap: why output stopped being the bottleneck(July 20, 2026)
user-research
- AI-assisted user research without laundering your evidence(July 20, 2026)
verification
- Vibe coding vs AI-assisted engineering: the line that matters(July 20, 2026)
- Vibe coding debt: what you actually owe and when it's due(July 20, 2026)
- Verifying AI-generated code: evidence, not vibes(July 20, 2026)
- Verification loops: hooks, gates and the end of self-reported success(July 20, 2026)
- Testing AI-generated code: what changes and what doesn't(July 20, 2026)
- Reviewing specs before agents build: the cheapest review you will ever do(July 20, 2026)
- Spec-driven vs test-driven: rivals or layers?(July 20, 2026)
- The spec is the contract: what that means in practice(July 20, 2026)
- From production to assurance: the new bottleneck in software(July 20, 2026)
- Scared to touch it: turning fear of your own codebase into a safety net(July 20, 2026)
- Reviewing code you didn't write: scope first, diff last(July 20, 2026)
- "Tests pass": anatomy of a false success claim(July 20, 2026)
- Evidence-based development: closing work with proof attached(July 20, 2026)
- Done means done: making agents prove completion(July 20, 2026)
- A definition of done that survives AI speed(July 20, 2026)
- The trust gap: why output stopped being the bottleneck(July 20, 2026)
- Review fatigue: when code arrives faster than you can read it(July 20, 2026)
- Acceptance criteria agents can actually verify(July 20, 2026)
- Software specifications should be portable(July 16, 2026)
- What is spec-driven development?(June 07, 2026)
- Spec-driven development: a green build is not a correct feature(June 07, 2026)
verification-loops
verify-ai-code
- Verifying AI-generated code: evidence, not vibes(July 20, 2026)
vibe-coding
- When to add tests and architecture to an AI-built project(July 20, 2026)
- What is vibe coding? (and where it stops working)(July 20, 2026)
- Vibe coding vs AI-assisted engineering: the line that matters(July 20, 2026)
- From vibe coding to production: the bridge nobody explains(July 20, 2026)
- Vibe coding debt: what you actually owe and when it's due(July 20, 2026)
- The security holes vibe coding leaves behind(July 20, 2026)
- The 90-day reckoning: why vibe-coded apps break at month 3(July 20, 2026)
- You shipped code you can't read. Now what?(July 20, 2026)
- Scared to touch it: turning fear of your own codebase into a safety net(July 20, 2026)
- Your Lovable prototype is now the product: surviving the promotion(July 20, 2026)
- Foundations under the house of cards: fixing a vibe-coded app without a rewrite(July 20, 2026)
- Every new feature breaks an old one: the missing contract(July 20, 2026)
- I asked the Codex app to build an app twice. Neither made it to tomorrow.(July 11, 2026)
what-is-vibe-coding
- What is vibe coding? (and where it stops working)(July 20, 2026)
worktrees
Note: Tags are used solely for content organization and do not generate indexed pages. For main content areas, please visit the categories.