3 ms·
This is why you shouldn't write one line of code, ever again. /s We've all been there though, at some point in our careers. Possibly multiples of times (try ch
by withinboredom 2y ago
This is why you shouldn't write one line of code, ever again. /s
We've all been there though, at some point in our careers. Possibly multiples of times (try changing thousands of "echo" statements to call a logger because it was initially meant to be a simple script that just kept growing).
It sucks but I've also been on the other side, where it was DRY but 20% of the calls to the function now needed different behavior. Finding all of those usages was just as hard.
- noisy_boy 2y ago> We've all been there though, at some point in our careers. Possibly multiples of times (try changing thousands of "echo" statements to call a logger because it was initially meant to be a simple script that just kept growing). Been there - now unless it is a very simple / throwaway code, I always start with logging setup from the start. It also helps with print based debugging because you can tune the output.