Programming

27640 readers

212 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Anyone else mass-renaming env variables and instantly regretting it? (lemmy.world)

submitted 2 days ago by indidev@lemmy.world to c/programming@programming.dev

26 comments fedilink hide all child comments

Spent an hour today renaming env vars across three services to make them "consistent." Broke staging in the process because one service cached the old values. Should've just left the mess alone — it worked fine before I touched it.

you are viewing a single comment's thread
view the rest of the comments

[–] Kache@lemmy.zip 1 points 2 hours ago* (last edited 2 hours ago)

Refactor first

Engineering has to draw the line somewhere. Excuse my analogy, but if the order is "you are not allowed to clean up the construction site, only build", and there's so much crap around that it's no longer safe, then the answer is, "no, I can't work like this, find someone else to do it"

That said, there is an art to working in and managing tech debt. The amazing thing about software is how flexible and how twisted it can get behind the external interface