Dev Horror Stories
Dev Horror Stories
Dev horror stories. We all have them. In this article, Travis Vachon provides a couple of examples from the software development community.
Join the DZone community and get the full member experience.
Join For FreeDownload the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.
Dev horror stories. We all have them. We’ve collected a handful of tales that still haunt our team and others on Twitter. We tried to keep them short, but like Python 3 adoption, they sometimes took longer than originally anticipated. Enjoy.
“None of these tests fail,” referring to a 1000-line TCL file where the first five lines were an infinite loop and nothing else ever ran.
“gRPC might change some day, so we wrote our own.”
“We wrote our own SQL dialect.”
“It’s just a CSS change. How hard could it be?”
“Multi-hour outage caused by ‘O’ instead of zero in config.”
“There are no bugs. My code is perfect!” > press cancel on first visible dialog box > application crashes.
“Several hours of Ruby troubleshooting caused by removing localhost from /etc/hosts.”
“Development halted after someone mapped Slackbot deploy train queuing functions to party parrot emoji.”
There’s still time to tweet your #DevHorror story to us, too!
Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.
Like This Article? Read More From DZone
Published at DZone with permission of Travis Vachon , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}