Thank you Eatonphil for writing this. I agree that I would love to see more of this kind and quality this kind of article of technical subjects. https://blog.

Thank you Eatonphil for writing this. I agree that I would love to see more of this kind and quality this kind of article of technical subjects. https://blog.jcoglan.com/2017/02/12/the-myers-diff-algorithm-part-1/ https://blog.jcoglan.com/2017/02/12/the-myers-diff-algorithm... https://keleshev.com/abstract-syntax-tree-an-example-in-c/ https://keleshev.com/abstract-syntax-tree-an-example-in-c/ I don't want to add more work to people who are already working more than everyone else. But when you write software or code that is truly good, I want people to write lots of examples and descriptions of their mental model and how to think of the software. I'm still trying to understand what the difference between a poller and an awaiter in Rust async. I use Flask because I find Flask easier to understand than Django. There's even a simple example on the Flask homepage. But Django has a very large tutorial which still doesn't really explain how each component fits together. I don't understand the mental model behind Django but I do with Flask. For example, I'm still trying to understand C++ coroutines. And I have some code that kind of works and some code someone provided on Stackoverflow I cannot get to work with GCC. There's not large amounts of documentation on C++ coroutines. I see people post fascinating awesome GitHub projects and have sparse README.md and no screenshots The code doesnt speak for itself. You can write the perfect code at a company and that code never flourishes because nobody wrote about it. Or you can write the perfect code at home but it doesn't get used. I would rather read your documentation of the inner workings of your software than your code itself. Code is harder to read and understand. This article essentially explains how to write a extremely fast query engine for columnular data, row data and exact match search: https://rockset.com/blog/converged-indexing-the-secret-sauce-behind-rocksets-fast-queries/ https://rockset.com/blog/converged-indexing-the-secret-sauce... I prefer a whitepaper + code than just code or just whitepaper. I learned from whitepapers and Wikipedia descriptions of algorithms more than I read people's code. I find it easier to understand people's descriptions of things and mental model. I hope people shall stop saying code IS the documentation and start documenting their software.