"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." dev.to/codemouse92/the-rules-o

"Can't happen" is your subconscious telling you that there's a bug just waiting for an opportunity to violate the laws of physics. And it will. Probably in the middle of your next demo.

RT @ctrlshifti@twitter.com

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

🐦🔗: twitter.com/ctrlshifti/status/

If you can't see the bug in your code, consider printing off the relevant source code on PAPER, and reading it in a different light (literally).

So much yes.

RT @ctrlshifti@twitter.com

the 5 stages of grief apply perfectly to debugging code

1. Denial
"The compiler is wrong"

2. Anger
"Why the hell isn't it working?"

3. Bargaining
"If I use enough print statements I'll figure this out"

4. Depression
"I will never fix this bug"

5. Acceptance
"It's a feature"

🐦🔗: twitter.com/ctrlshifti/status/

Java on Hayden is one of my most favorite places in the world. No better place to remote work or chat with awesome people in my community. Plus, their coffee is amazing.

If you get sick from too many dollar store greeting cards, is that tacky-card-ia (tachicardia)?

"Duplication is far cheaper than the wrong abstraction." -@sandimetz@twitter.com, “The Wrong Abstraction”

"I've learned there are three things that are never predictable in software: problem complexity, production time, and the viability of third-party software." dev.to/codemouse92/gallifreyan

All external dependencies should be considered a bad idea until you've figured out how to deploy the finished product with them.

And YES, this extends to sarcasm, irony, and humor. If your message is lost on a listener, even one listener, take that as a cue that you should rephrase to remove the ambiguity. NO ONE can read your mind; it is your responsibility alone to communicate your own ideas effectively.

Of course, this doesn't account for the rarer times when someone chooses to deliberately misinterpret you. That's a hostile action you can do nothing about. HOWEVER, before you conclude this is the case, assume you could have been clearer, and try again.

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.

Very helpful guide to cognitive biases, which can submarine good decision-making. Recognize any in yourself? (Hint: Everyone regularly defaults to at least most of these.)

You can't estimate how long a task will take until you start working on it, no matter what your "gut" says.

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! actionnetwork.org/petitions/do

What do you call a long stick with a donut tied on then end? Baited switch.

Show more
mastodon.cloud

Generalistic and moderated instance.