DEV Community

Babak K. Shandiz
Babak K. Shandiz

Posted on • Originally published at babakks.github.io on

On Ugly Face of Hardcoded Values [RE#5]

Recently I’ve been working on a service maintenance/migration problem and needed to change a few configuration parameters (names of several RabbitMQ queues/exchanges.)

Things were going smooth until when I found there’s no way to nicely apply such changes on tge production, because some developer, at some point hardcoded the names into the code base. She either decided these parameters are never going to change or to parameterizing them contributes to unnecessary complexity–I hope the former was the case. 🤦

Besides taking the precious time of fellow developers and waste their focus/energy, hardcoding ties your hands in emergency/disaster recovery. You never know what’s going to be happen in the next incident. The moral of the story, don’t leave hardcoded values as your heritage.


About Regular Encounters

I’ve decided to record my daily encounters with professional issues on a somewhat regular basis. Not all of them are equally important/unique/intricate, but are indeed practical, real, and of course, textually minimal.

Discussion (0)