Time and Relative Distance in Source (Code)

Reasoning about a program’s behavior is extremely tricky in the best of circumstances. When you throw in asynchronicity, it is the absolute worst. It’s like your code is trapped in a convoluted time travel movie. You want to perform some operation, but that requires stepping into a time portal and coming out at some indeterminate future date. Who knows what has changed since you’ve been gone? Add a few more asynchronous operations, and your code very quickly becomes a tangled mess of wibbly-wobbly, timey-wimey stuff. Read more on Time and Relative Distance in Source (Code)…

Hacking “Time Out” and Forcing Myself to Take a Break

I have a bad habit of banging my head against a problem instead of taking a step back to clear my thoughts. I’m a D on the DISC profile, and I blame that for my tendency to keep attacking a problem full-tilt rather than re-evaluating my approach.

Rationally, I’m well aware of the benefits of taking a break. But in the moment, I just want to keep going for that next dopamine kick that comes with each minor breakthrough. Never mind that if I took a break, I might see that my whole approach is flawed, because “slow is smooth, smooth is fast.” Or as I like to think of it, “slow is smart, smart is fast.”
Read more on Hacking “Time Out” and Forcing Myself to Take a Break…