The article highlights the pitfalls of traditional software development methods, particularly the risks of lengthy development cycles without early deployment. The author recounts a personal experience from working on a software team where significant issues arose due to a delayed deployment, emphasizing the value of releasing software early to avoid surprises. The story illustrates how a miscommunication and a critical code change led to deployment problems, showcasing the challenges teams face when they do not seek feedback from real users until it's too late.
I found the problem rather quickly: It was a code change the dev manager had made to the way we handled cookies, which didn't show a problem on the internal test server but broke things during deployment.
There's 'release early, release often,' which seemed revolutionary the first time I heard it after living under a waterfall for years, or there's building so much while waiting so long to deploy that you guarantee weird surprises.
Collection
[
|
...
]