Blog

When designing AWS Lambda’s, try to keep the side effects low. Think of your handler function having just 1 IO type. Just like a list can be typed as Array[string], try keeping just one IO type as well.

Had mid-year performance reviews at work recently and it reminded me how, yet again, what I specialize in has changed in the past 4 years, specifically in Cloud Engineering in AWS. At work you fill out what you want to accomplish in the next 6 months personal growth & career wise. Your manager reviews & confirms/denies/suggests differences. You accept/reject/suggest changes, until you both agree on a path forward. Think like a video game skill tree and you pick a few branches and boxes you want to work towards.

I’m going down the rabbit hole of reading about microservices for an upcoming talk. As a UI guy, I’m always playing catchup, more so on the back-end. I’m intentionally targeting my survival bias trying to find _anything_ that cites Distributed Monoliths as good (most assume bad). This was originally posted on Twitter.

I see a lot of new, veteran, and non-JavaScript developers confused about the 2 styles of writing Promises in JavaScript. I wanted to cover what both style offers, why you’d use one or the other, and why you typically should choose one and not mix both together. Promises are a deep topic, so this isn’t a guide on the various ways Promises work, but it does include the basics.