Tag: developer-productivity
-
Agentic coding: Difference between an agent and a slow script
A field-tested take on the difference between an agent and a slow script with Agentic coding: what it rewards, where it breaks, and how to keep the workflow honest.
-
AI coding workflows: Small reversible steps instead of one heroic prompt
A field-tested take on small reversible steps instead of one heroic prompt with AI coding workflows: what it rewards, where it breaks, and how to keep the workflow honest.
-
Prompt engineering for code: Acceptance criteria as the only prompt that matters
A field-tested take on acceptance criteria as the only prompt that matters with Prompt engineering for code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Agentic coding: Budgets as the only feature that stops a bad loop
A field-tested take on budgets as the only feature that stops a bad loop with Agentic coding: what it rewards, where it breaks, and how to keep the workflow honest.
-
AI coding workflows: Review cycle that keeps agent output honest
A field-tested take on the review cycle that keeps agent output honest with AI coding workflows: what it rewards, where it breaks, and how to keep the workflow honest.
-
Prompt engineering for code: Shortest prompt that still passes review
A field-tested take on the shortest prompt that still passes review with Prompt engineering for code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Agentic coding: Building trust with agents the way you build it with juniors
A field-tested take on building trust with agents the way you build it with juniors with Agentic coding: what it rewards, where it breaks, and how to keep the workflow honest.
-
AI coding workflows: Resting the agent: when taking the keyboard back beats another turn
A field-tested take on resting the agent: when taking the keyboard back beats another turn with AI coding workflows: what it rewards, where it breaks, and how to keep the workflow honest.
-
Prompt engineering for code: When to stop prompting and start coding
A field-tested take on when to stop prompting and start coding with Prompt engineering for code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Agentic coding: Why short agent loops beat heroic ones
A field-tested take on why short agent loops beat heroic ones with Agentic coding: what it rewards, where it breaks, and how to keep the workflow honest.
-
AI coding workflows: Time-boxing agent loops before they eat the day
A field-tested take on time-boxing agent loops before they eat the day with AI coding workflows: what it rewards, where it breaks, and how to keep the workflow honest.
-
Prompt engineering for code: Prompts as contracts, not wishes
A field-tested take on prompts as contracts, not wishes with Prompt engineering for code: what it rewards, where it breaks, and how to keep the workflow honest.
More posts tagged developer-productivity
- Agentic coding: Rollback plans for changes you did not watch land
- AI coding workflows: Rescue patterns when an agent has gone off the rails
- Prompt engineering for code: Few-shot examples that teach taste, not just format
- The honest case for agents that only suggest
- Writing acceptance tests first, agents second
- Diffing prompts the way you diff code
- Agentic coding: How to review a PR an agent opened in the middle of the night
- AI coding workflows: Treating diffs as the primary artefact, chat as exhaust
- Prompt engineering for code: How to write a system prompt you can still read in six months
- Agentic coding: Guardrails before autonomy, always
- AI coding workflows: Scorecard question: did this PR have to exist?
- Prompt engineering for code: Structured outputs: JSON schemas that keep agents honest
- Agentic coding: Planning outputs as the real product of the first turn
- AI coding workflows: Pair-with-AI rituals that survive a team of ten
- Prompt engineering for code: Difference between role prompts and persona cosplay
- Agentic coding: What to log when an agent writes for you
- AI coding workflows: Daily shutdown routine that actually ships code
- Prompt engineering for code: Turning specs into prompts without losing the nuance
- Agentic coding: Difference between an agent and a slow script
- AI coding workflows: Small reversible steps instead of one heroic prompt
- Prompt engineering for code: Acceptance criteria as the only prompt that matters
- Agentic coding: Budgets as the only feature that stops a bad loop
- AI coding workflows: Review cycle that keeps agent output honest
- Prompt engineering for code: Shortest prompt that still passes review
- Agentic coding: Building trust with agents the way you build it with juniors
- AI coding workflows: Resting the agent: when taking the keyboard back beats another turn
- Prompt engineering for code: When to stop prompting and start coding
- Agentic coding: Why short agent loops beat heroic ones
- AI coding workflows: Time-boxing agent loops before they eat the day
- Prompt engineering for code: Prompts as contracts, not wishes
- Automated Tests That Actually Make Sense
- Agentic coding: Rollback plans for changes you did not watch land
- AI coding workflows: Rescue patterns when an agent has gone off the rails
- Prompt engineering for code: Few-shot examples that teach taste, not just format
- Agentic coding: Honest case for agents that only suggest
- AI coding workflows: Writing acceptance tests first, agents second
- Prompt engineering for code: Diffing prompts the way you diff code
- Agentic coding: How to review a PR an agent opened in the middle of the night
- AI coding workflows: Treating diffs as the primary artefact, chat as exhaust
- Prompt engineering for code: How to write a system prompt you can still read in six months
- Agentic coding: Guardrails before autonomy, always
- AI coding workflows: Scorecard question: did this PR have to exist?
- Prompt engineering for code: Structured outputs: JSON schemas that keep agents honest
- Agentic coding: Planning outputs as the real product of the first turn
- AI coding workflows: Pair-with-AI rituals that survive a team of ten
- Prompt engineering for code: Difference between role prompts and persona cosplay
- Agentic coding: What to log when an agent writes for you
- AI coding workflows: Daily shutdown routine that actually ships code
- Prompt engineering for code: Turning specs into prompts without losing the nuance
- Agentic coding: Difference between an agent and a slow script
- AI coding workflows: Small reversible steps instead of one heroic prompt
- Prompt engineering for code: Acceptance criteria as the only prompt that matters
- Agentic coding: Budgets as the only feature that stops a bad loop
- AI coding workflows: Review cycle that keeps agent output honest
- Prompt engineering for code: Shortest prompt that still passes review
- Agentic coding: What agentic coding taught us about how we really work
- AI coding workflows: What we retired because an agent finally did it well
- Prompt engineering for code: Prompt engineering as writing, not programming
- Agentic coding: Retrospective after our first week of full agentic coding
- AI coding workflows: When taking the keyboard back was the real productivity move
- Prompt engineering for code: Honest taxonomy of prompts, as discovered in practice
- Agentic coding: Deliberate agent downtime as an early productivity discovery
- AI coding workflows: Daily checklist that outlasted two tool migrations
- Prompt engineering for code: Shorter prompts after a month of deliberately deleting words
- Agentic coding: First PR an agent opened that we merged without edits
- AI coding workflows: First retrospective on what AI did and did not change
- Prompt engineering for code: First prompt rot we detected, and the lessons from it
- Agentic coding: Cost-per-merged-change metric we invented out of necessity
- AI coding workflows: Diff as primary artefact, chat as exhaust, a first lesson
- Prompt engineering for code: How we measured prompt quality before we had metrics
- Agentic coding: Long-running agent that finally paused itself
- AI coding workflows: Acceptance tests first, agents second, as a beginner mantra
- Prompt engineering for code: Style guides for both humans and models, a beginner attempt
- Agentic coding: How a junior engineer earned their first autonomous task
- AI coding workflows: Choosing boredom over brilliance in the first year
- Prompt engineering for code: When a prompt quietly became a feature spec
- Agentic coding: Case for suggest-only agents in safety-critical code
- AI coding workflows: Shutdown routine that made AI-heavy days survivable
- Prompt engineering for code: Diffing prompts without a system, and the system that followed
- Agentic coding: Short loops as the winning rhythm, discovered through long ones
- AI coding workflows: Time-boxing agent loops before they ate the afternoon
- Prompt engineering for code: Prompt library we started in a shared Markdown file
- Agentic coding: First rollback plan we actually used
- AI coding workflows: Rescue patterns discovered after the first agentic disaster
- Prompt engineering for code: Few-shot examples drawn from our own first PRs
- Agentic coding: Guardrails before autonomy, learned the expensive way
- AI coding workflows: Scorecard that replaced vanity metrics in month three
- Prompt engineering for code: Role prompts the first time we stopped cosplaying with them
- Agentic coding: Planning outputs as the real product of the initial turn
- AI coding workflows: Pair-with-AI rituals for a team that had never tried them
- Prompt engineering for code: Structured outputs, discovered the hard way
- Agentic coding: Budgets as the first feature any agent had to have
- AI coding workflows: Small reversible steps as a rhythm we borrowed from elsewhere
- Prompt engineering for code: Learning that acceptance criteria beat cleverness
- Agentic coding: First overnight agent run we dared to approve
- AI coding workflows: First weekly review that made AI-assisted work sustainable
- Prompt engineering for code: First prompts we wrote that still pass review a year later
- Agentic coding: What agentic coding taught us about how we really work
- AI coding workflows: What we retired because an agent finally did it well
- Prompt engineering for code: Prompt engineering as writing, not programming
- Agentic coding: Retrospective after our first week of full agentic coding
- AI coding workflows: When taking the keyboard back was the real productivity move
- Prompt engineering for code: Honest taxonomy of prompts, as discovered in practice
- Agentic coding: Deliberate agent downtime as an early productivity discovery
- AI coding workflows: Daily checklist that outlasted two tool migrations
- Prompt engineering for code: Shorter prompts after a month of deliberately deleting words
- Agentic coding: First PR an agent opened that we merged without edits
- AI coding workflows: First retrospective on what AI did and did not change
- Prompt engineering for code: First prompt rot we detected, and the lessons from it
- Agentic coding: Cost-per-merged-change metric we invented out of necessity
- AI coding workflows: Diff as primary artefact, chat as exhaust, a first lesson
- Prompt engineering for code: How we measured prompt quality before we had metrics
- Agentic coding: Long-running agent that finally paused itself
- AI coding workflows: Acceptance tests first, agents second, as a beginner mantra
- Prompt engineering for code: Style guides for both humans and models, a beginner attempt
- Agentic coding: How a junior engineer earned their first autonomous task
- AI coding workflows: Choosing boredom over brilliance in the first year
- Prompt engineering for code: When a prompt quietly became a feature spec
- Agentic coding: Case for suggest-only agents in safety-critical code
- AI coding workflows: Shutdown routine that made AI-heavy days survivable
- Prompt engineering for code: Diffing prompts without a system, and the system that followed
- Agentic coding: Short loops as the winning rhythm, discovered through long ones
- AI coding workflows: Time-boxing agent loops before they ate the afternoon
- Prompt engineering for code: Prompt library we started in a shared Markdown file
- Agentic coding: First rollback plan we actually used
- AI coding workflows: Rescue patterns discovered after the first agentic disaster
- Prompt engineering for code: Few-shot examples drawn from our own first PRs
- Agentic coding: Guardrails before autonomy, learned the expensive way
- AI coding workflows: Scorecard that replaced vanity metrics in month three
- Prompt engineering for code: Role prompts the first time we stopped cosplaying with them
- Agentic coding: Planning outputs as the real product of the initial turn
- AI coding workflows: Pair-with-AI rituals for a team that had never tried them
- Prompt engineering for code: Structured outputs, discovered the hard way
- Agentic coding: Budgets as the first feature any agent had to have
- AI coding workflows: Small reversible steps as a rhythm we borrowed from elsewhere
- Prompt engineering for code: Learning that acceptance criteria beat cleverness
- Agentic coding: First overnight agent run we dared to approve
- AI coding workflows: First weekly review that made AI-assisted work sustainable
- Prompt engineering for code: First prompts we wrote that still pass review a year later