this post was submitted on 15 Dec 2024
95 points (97.0% liked)
Asklemmy
44148 readers
1283 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Code is both great and terrible until it compiles.
Site reliability engineer here, your application is both alive and dead until the monitoring server pings its health status API.
My company is basically 30 startups in a trenchcoat. The bulk of our my org's application was written 5-10 years ago by like 4 dudes, none of whom work at the company anymore. Cowboy coding doesn't come close. We have so much legacy code and I alternate between "how the fuck does this work" in an impressed way and a horrified way anytime I look at it
In programming there is also the Heisenbug: as soon as you try to observe the bug, it disappears or changes its behavior.
I fucking hate Heisenbergs!
Hrm, weird reproducible bug. Ok let's hook up the ol' debugger and.... Where did the bug go? Shiiiiiiit.
It's mostly because many observation processes are invasive and change the nature of the system under test