Definition
Developer responsibility is the practice of owning the results of your work, including the parts that went wrong. A responsible developer commits to outcomes they can control, is honest when something fails, and brings solutions rather than alibis.
The Pragmatic Programmer authors phrase it sharply: provide options, do not make lame excuses. When a task cannot be done as planned, the professional response is to explain what can be done instead, not to blame circumstances.
Why it matters
How it works
Before committing to something, decide whether it is genuinely within your control; if it is not, say so honestly rather than over-promising. Once you do commit, the outcome is yours to own. If you cannot keep the commitment, raise it early with concrete alternatives and a clear assessment of the tradeoffs.
Responsibility also extends to code you did not write. Spotting a broken window and walking past it is a quiet abdication. The Pragmatic Programmer ideal is a developer whose presence raises the standard, because they treat the health of the whole system as part of their job.