798 karma · joined April 28, 2020
An amazing critique. I've never read anything with so many "wtf?" and "omg!" moments.
That would definitely keep the story from being all-hat-and-no-cattle. I can't recall reading something with so many alternate versions of how to implement something but with zero benchmarks.
Formatting can be tough. See Knuth's extensive bug list for TEX from 1987 at https://yurichev.com/mirrors/knuth1989.pdf to see the kind of tarpit one can get trapped in.
More details should eventually arrive at https://azure.status.microsoft/en-us/status/history/
Consider investing your time, not just your money. In other words, do careful research, start a business, then put your labor into offering a product or service that fills a need, instead of simply working for someone else. If you fail, you'll still learn a lot for another try. And if you succeed, the payoff can be much larger and faster than anything else you might attempt.
I wish you started out by telling me how many customers you have to serve, how many transactions they generate, how much I/O there is.
Now I can't seem to write anything that doesn't generate hundreds of megabytes from untold number of dependencies nested who knows how deep that would take me a lifetime to fully explore.
Sigh.