In 2017, a colleague graciously shared this technique with me, thoughtfully nitpicking one of my first pull requests on the job. I've since made it my own, and even got it to rub off on some others.
Redshift is a little async programming library I wrote in PHP over 9 years ago. Mostly intended as an exercise. I thought it'd be fun to take a few minutes to revisit it and see if there's anything I would've done differently today.
Time is the one resource we'll never get more of, yet somehow, it's one of the first things we forget when planning a project. If we know we're doing the right thing, then this is just what it takes, right? Maybe. But my advice would be to try and dig a little deeper.
"Program testing can be used to show the presence of bugs, but never to show their absence!" - Edsger W. Dijkstra.
This is easily one of my favorite quotes when it comes to software engineering.
I recently found myself pondering some questions about dealing with asynchronous requests in React specifically, and figured it might be worth sharing.
It’s things like these that sometimes drive me crazy. It doesn’t really prevent me from doing anything, but I can’t help but notice it every single time. I also kind of did this to myself.
It's been a while since I last published anything... and it certainly wasn't for the lack of content or ideas. I dropped the habit after my server went up in flames and just haven't picked it up since.