"If you've been at this a while, you probably have debugging down to some sort of an art. For the rest of y'all, here's a few rules from the trenches." #ThrowbackThursday https://dev.to/codemouse92/the-rules-of-debugging-2hf5
whenever you're having a bad day, just remember that someone out there is debugging a shallow vs deep copy issue for the first time
So much yes.
the 5 stages of grief apply perfectly to debugging code
"The compiler is wrong"
"Why the hell isn't it working?"
"If I use enough print statements I'll figure this out"
"I will never fix this bug"
"It's a feature"
Running late is my cardio
"I've learned there are three things that are never predictable in software: problem complexity, production time, and the viability of third-party software." #ThrowbackThursday https://dev.to/codemouse92/gallifreyan-software-project-management-29a1
YOU are responsible for your own message. "You misunderstood" is blame-shifting; 99 out of 100 times, you could have communicated better, whether you realized it or not, and you need to take the responsibility for that. It's not the listener's job to read your mind. #lifeskills
I signed a petition on Action Network urging Congress to reject the dangerous EARN IT Act and save important encryption technology that keeps us safe and secure online. Please join me! https://actionnetwork.org/petitions/dont-let-congress-kill-encryption
I cannot overstate how epic this is! Great work @email@example.com https://dev.to/epranka/how-does-your-code-sound-3c25
Author | Speaker | Hacker | Time Lord
Generalistic and moderated instance.