I've spent a few hours spiking a first AWS microservice to extract from our Rails monolith. I had thought to use the node.js runtime, because "JS is a lingua franca among web devs" (maintainability), and given I know JS, it should be easy to get going, right? WRONG
Hoo boy. node.js and async-first JS is nothing like anything I've encountered in the browser. I spent most of the time slamming my head against learning the ins and outs of async/await and how to cross seams between promise rejection and traditional errors
Then hit another wall when I tried to integrate the client library for a third-party platform we integrate with
I'm going to make a run at a Ruby version the next time I sit down with it. At least I have my test cases defined & can port them over to RSpec
Or heck, as long as I am visiting foreign platforms, maybe I should try out a golang version
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I've been bingeing How I Met Your Mother, a show I had not previously heard of
I find it very entertaining generally; it's worth turning a critical eye on its treatment of gender
A lot of bald transmisogynistic and transphobic humor. Other characters' (men and women) punishment of Ted for failing/refusing to conform to bro norms. Humorous and not particularly critical treatment of toxic masculinity and rape culture
Those of us who started making software largely to REDUCE the amount of work we had to do will have an easier time seeing the lie in "work ethic" when it comes to software development
Work isn't inherently good. Idleness isn't inherently evil. A job description invoking "work ethic" is coming from a capitalist place of wanting to extract the maximum amount of value from you