3 ms·
> So the solution here is to not have that kind of "stack". Reminds me of my favorites debugging technique. It's super fast: Don't write any bugs!
by fragmede 2y ago
> So the solution here is to not have that kind of "stack".
Reminds me of my favorites debugging technique. It's super fast: Don't write any bugs!
- vinnymac 2y agoCode is a liability. Not writing code is one of the best things a developer can do on any particular day, aside of course from deleting it ;)
- halfcat 2y agoQuite an effective approach: https://github.com/kelseyhightower/nocode https://github.com/kelseyhightower/nocode
- arp242 2y agoWhat a boring trite reply. All of this is analogous to badly written spaghetti code. And yes, you can absolutely avoid all of this if you know what you're doing.
- Tainnor 2y agoNot trite at all. Bad code and bad architectures are a reality. You can fix them in theory, but that takes a lot of time and needs to be done incrementally. In the meantime, you have to live with the problem at hand.