> The Illusion of Finality One of the most important skills that I've learned, through writing ship software, is "Knowing what 'Done' looks like." There's a p

> The Illusion of Finality One of the most important skills that I've learned, through writing ship software, is "Knowing what 'Done' looks like." There's a point, where -even though there's still stuff that I have to do- I need to declare the project "done," wrap it up, slap a bow on it, and push it out the door. There's always a 2.0. Writing in an iterative manner (where I "discover" a design, as I develop the software), makes this more difficult. One thing about "hard" requirements, is that there's no question about what "Done" looks like.