+1 that the plastic is the main difference are the "everything to Ryobi"-plastic adadpters you can buy. I use Makita battery->Ryobi tool and it works great.

Ryobi are actually the first batteries that I genuinely dislike; I have 8 year old Black & Decker drill whose battery still works great. Similar experience with some other manufacturers. But we went all-in on Ryobi at Home Depot a few years ago, and we now have to buy 2-4 new batteries a year. Then after 12-18 months, the battery shows as defective on its charger.... brutal.

(probably less-than-average usage patterns as we are lazy house owners; stored inside, not abused)

That pretty much echoes the reputation Ryobi tools have. ie. the tools themselves are really good but the batteries don't last.

I think using the Core Ideas Playlist and starting there would be good: https://www.youtube.com/playlist?list=PL8xK8kBHHUX43VVxO3b7s...

I have never listened to a podcast, just the cut out snippts on the youtube channel.

MrBeast is in the business of arbitrage.

I love this post. You've managed to describe my current frustration, when working with people that score low in those categories.

I've had a team member that was quite high in 3 out of 4 categories and low in actual programming skills and I found him to be a valuable team member.

Clojure is the ultimate interop language to me.

ClojureScript (shadow-cljs, nbb) for JavaScript

Clojure for JVM

babashka for scripts

libpython-clj for python interop.

ClojureCLR for .NET (beta state IMO)

ClojureDart for Dart/Flutter (early alpha state, one big shipped prod app on iOS/android)

--- Edit:

I don't quite know how to describe it, but having the _exact_ same files in a full-stack web application being read in both the Clojure backend and ClojureScript frontend (API contract) feels pretty neat. As an example having the frontend accurately give the user feedback why his input form isn't going to be accepted without a server round-trip or duplicating code just feels elegant.

I wonder if there is Clojure for the BEAM

Why yes!

https://github.com/clojerl/clojerl

Ok interesting thanks.

Not to make you feel too bad, but based on your sentence you may appreciate a recent addition to my personal REPL toolkit in Clojure which I very much enjoy.

You may remember the rich comment forms in Clojure development as a communication tool to your future self and others. Now someone made them testable https://github.com/hyperfiddle/rcf#readme I feel this is even closer to the platonic ideal Clojure way of serializing your thoughts to file.