and edge cases

Author: atuttle

blog/2023/my-theory-of-technical-debt.md

@@ -104,6 +104,6 @@ I don't have any silver bullets (yet?) for doing better at estimating, but I ack
 
 I've heard people say that they come up with their estimation, and then they double or triple it, and give that as the actual estimation, to cover anything they haven't thought of. That's one way to do it, though probably imprecise.
 
-I think it's more likely that we just forget to think about planning, testing, refactoring, and code review when we make estimations, because writing code quickly can be a point of pride. _You need 4 weeks to write that? I could do it in 2!_ But never in the history of ever has _I could do it in 2!_ guy been thinking about planning, testing, refactoring and code review when he gives that number.
+I think it's more likely that we just forget to think about planning, testing, refactoring, and code review —and edge-cases!— when we make estimations, because writing code quickly can be a point of pride. _You need 4 weeks to write that? I could do it in 2!_ But never in the history of ever has _I could do it in 2!_ guy been thinking about planning, testing, refactoring, edge-cases, and code review when he gives that number.
 
 Don't be that guy.