Updated 20 October 2026.
Discuss a software deadline by separating what is known from what still needs investigation, explaining the dependencies, and offering concrete tradeoffs. An estimate describes your current expectation. A commitment should also reflect the scope, conditions, and responsibility the people involved have agreed to.
The Clean Coder by Robert C. Martin discusses professionalism, saying no, saying yes, commitments, and estimation. The publisher's overview and contents verify those subjects. The conversation exercise below is our own application; it does not claim that the book provides a universal rule for predicting completion dates.
Clarify what the date is meant to support
Ask what happens on the requested date. A customer demonstration, an internal review, and a production launch can require different deliverables and checks.
Then clarify what complete means. Does the request include migration, review, testing, documentation, and rollout? If those tasks are not visible, a date can sound plausible while describing only part of the work.
Avoid silently accepting a broader meaning than the one you estimated. Bring the difference into the discussion while the plan can still change.
Put uncertainty into the description of the work
List the known tasks, the unresolved questions, and any external dependency. Distinguish work you control from an approval or service you must wait for.
If you have not examined a risky integration, say so. Identify a bounded investigation that could improve the estimate and when you can report back. This is more useful than attaching a confident date to an unknown task.
Do not treat precision as accuracy. A date written with confidence is still uncertain if the underlying conditions have not been investigated.
Work through a requested Friday release
Imagine a developer asked to release a new export feature by Friday. The basic export is understood, but the required permissions and behavior for large files are unresolved.
A fictional preparation note might separate three options:
- Demonstrate a local prototype with synthetic data on Friday.
- Deliver a smaller reviewed export after confirming the permission rules.
- Plan the complete release once the large-file investigation is finished.
The developer explains which questions each option leaves open. They do not present an unreviewed prototype as production-ready or remove essential checks merely to preserve the date.
The team may still face a difficult constraint. Honest options do not guarantee an easy agreement; they allow the decision to be made with a clearer account of the work.
Make the chosen commitment explicit
Record the deliverable, scope boundary, owner, dependencies, and review point. Include how a material change will be raised. Make sure the person relying on the date has the same understanding.
If a deadline becomes doubtful, communicate the new information and its effect early. “Still working on it” may be true while failing to answer the other person's planning question.
The trusted-professional learning path offers broader reading. This article focuses on the practical conversation between an engineering estimate and a promise someone else may rely on.
Review the estimate after the work
Compare the original assumptions with what happened. Were tasks missing, dependencies late, or requirements changed? Use the record to improve the next estimate without treating every variance as a character judgment.
For recall, explain the difference between an estimate, a prototype demonstration, and a production commitment. Then draft one honest statement about an unresolved dependency in your current work, including the next investigation that would make the plan clearer.
Continue with ReadSprint
Open the related book summary to revisit the book's broader ideas. Use the free Book-to-Action Plan to organize your own takeaways into practice and review phases; the tool arranges the entries you supply rather than validating the method or predicting results.
Source checked 20 October 2026: The Clean Coder publisher overview and contents. The source supports the attributed book concept. The scenarios, questions, and practice steps in this article are original ReadSprint suggestions; example outcomes are hypothetical.
