Sam Rose

https://samwho.dev has some fantastic blog posts with great visualisations

Love the detailed interactive visual explanations, https://samwho.dev/ is another one like Ciechanow.ski

I‘m at https://nik.digital :) Some others: https://samwho.dev https://www.nicchan.me

Sam has a long history of building beautiful visual explanations like this - I didn't realize he works for ngrok now, here's his previous independent collection: https://samwho.dev/

I love this so much, thank you for putting this together! My only piece of feedback would be for the "Inline Bookkeeping" section (https://samwho.dev/memory-allocation/#inline-bookkeeping), it took a while for me to grok the numbered list to figure out which block corresponded to address + X. I wonder if there is a better way to visualize the 4 numbered bullet points? Maybe just arrows and text pointing to the visualization? Thanks again for this wonderful article!

All credit goes to my wonderful friend Sam Who: https://twitter.com/samwhoo He recently published a similar guide on load balancing that is equally intuitive and insightful: https://samwho.dev/load-balancing/ I can't wait to see what he puts out next!

I have some potentially bad news for you: https://samwho.dev/load-balancing https://encore.dev/blog/queueing

You might want to check out this very nice article on reservoir sampling, which discusses its application to logging: https://samwho.dev/reservoir-sampling/

Here's a Turing machine that uses finite space but infinite time: https://samwho.dev/christopher/?code=H4sIAAAAAAAAE8tNzMxTqFHQUqhRCNAw1… (from Sam Rose's wonderful article on Turing machines [1]) Your last point is correct, though: if you can detect a "cycle" (like the one the Turing machine I linked to goes through) then you can conclude that the machine won't halt. [1] https://samwho.dev/turing-machines/

I really like this husky graphic, did you create it? https://samwho.dev/images/sage-warning.png

https://samwho.dev/blog/ The visualizations help with the understanding while keeping it engaging too

This one came up on HN previously. Playground is at the bottom: https://samwho.dev/load-balancing/

It even has a playground! https://samwho.dev/allocator-playground/ How I wish I had something like that when I first learned C.

This is really, really well done. Also, the allocator playground[0] is really cool. Will be my go-to when teaching this topic moving forward :) [0] https://samwho.dev/allocator-playground/

Looks like it - https://samwho.dev/rss.xml

[40 minutes into the talk]: Looks like the study scanned 3.6 million github issues across 1.7 million repositories and looked for the number of bugs that were TypeError, AttributeError, or NameError and found it was 2.7% of issues. I'm not a fan of this kind of methodology, because there are so many different use cases for github issue tracker (including feature requests, documentation requests, etc.) that I think the denominator here is overestimated. I'd rather have a study that looked at 1000 issues in depth with a rigorous rubric than one that grepped through millions of issues. Also, looking only at the issues doesn't count the ones that were caught in development or testing. I like the notion of "moving your bugs to the left"[1] and would much rather find these type errors at build time than later. Finally as I said in my other comment, avoiding type errors is not the only benefit of type checking. Making code easier to understand and refactor (including programmatic refactoring) are other benefits that are not captured only by counting bugs. [1] https://samwho.dev/blog/move-your-bugs-to-the-left/