Tag: developer-productivity
-
Agentic coding: Rollback plans for changes you did not watch land
A field-tested take on rollback plans for changes you did not watch land with Agentic coding: what it rewards, where it breaks, and how to keep the workflow honest.
-
AI coding workflows: Rescue patterns when an agent has gone off the rails
A field-tested take on rescue patterns when an agent has gone off the rails with AI coding workflows: what it rewards, where it breaks, and how to keep the workflow honest.
-
Prompt engineering for code: Few-shot examples that teach taste, not just format
A field-tested take on few-shot examples that teach taste, not just format with Prompt engineering for code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Agentic coding: Honest case for agents that only suggest
A field-tested take on the honest case for agents that only suggest with Agentic coding: what it rewards, where it breaks, and how to keep the workflow honest.
-
AI coding workflows: Writing acceptance tests first, agents second
A field-tested take on writing acceptance tests first, agents second with AI coding workflows: what it rewards, where it breaks, and how to keep the workflow honest.
-
Prompt engineering for code: Diffing prompts the way you diff code
A field-tested take on diffing prompts the way you diff code with Prompt engineering for code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Agentic coding: How to review a PR an agent opened in the middle of the night
A field-tested take on how to review a PR an agent opened in the middle of the night with Agentic coding: what it rewards, where it breaks, and how to keep the workflow honest.
-
AI coding workflows: Treating diffs as the primary artefact, chat as exhaust
A field-tested take on treating diffs as the primary artefact, chat as exhaust with AI coding workflows: what it rewards, where it breaks, and how to keep the workflow honest.
-
Prompt engineering for code: How to write a system prompt you can still read in six months
A field-tested take on how to write a system prompt you can still read in six months with Prompt engineering for code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Agentic coding: Guardrails before autonomy, always
A field-tested take on guardrails before autonomy, always with Agentic coding: what it rewards, where it breaks, and how to keep the workflow honest.
-
AI coding workflows: Scorecard question: did this PR have to exist?
A field-tested take on the scorecard question: did this PR have to exist? with AI coding workflows: what it rewards, where it breaks, and how to keep the workflow honest.