I've realised the big advantage of teaching OO with physical analogies. It's well accepted that OO isn't just about modelling the eworld.
Physical items are great for explaining subtyping.
You can view types as subsets, and Ferrari <: Car <: Vehicle is intuitive.
miniblog.
Related Posts
LLMs are surprisingly good at reducing crash samples.
I've had success with "this project crashes my static analysis tool with the following command, try to shrink the repro whilst preserving the crash. Commit each smaller version to a branch".
Has the JS ecosystem reached a point where people agree roughly what a good architecture looks like?
I don't see as many blog posts complaining about new framework churn and I'm wondering why.
Rust and RISC-V both feel like they've reached critical mass and I'd guess that they'll be used more in 5 years than they are today.
What other technologies fit this description?