We've all been there, a problem or feature presents itself that we can see a mile away will need rework or have scope creep. We'd love to take the time to ascertain every outlier, scope out extensibility and plan for seamless future maintainability. ...

Markdown supported · ⌘↵ to post
Amazingly I was just catching up on one of my favourite podcasts Developer Tea and Jonathan talks about this exact thing! Introduce Intentional Asymmetry
Nicklas Møller Jepsen
Everything Azure and .NET
Spot on! But how tempting it can be to do perfect... :D I have had things running for years for thousands of users that took me 5 minutes to develop, but then again I have also spent weeks on the most elegant solutions that never got released.