wmtthrowaway
Reason #1: They did a horrible job, this post reads like a list of things not to do.
Reason #2: They still did a much better job than my company. We had a similar rewrite from a reasonably well performing system to a dog slow monstrosity. However instead of acknowledging it was slow, we put on our doublethink hats and deployed anyways. "We" picked a couple metrics that were easier to game (time to first byte) and then we threw up our mission accomplished flag and moved on. We also wrote posts like this bragging about the performance improvements we'd made.
I hate the sort of "techcrunch driven development" that's so big in wanna-be facebook companies. Instead of solving business and customer needs, directors and vps are mostly focused on splashy articles and speaking engagements that make their resume look good.
I wasn't directly impacted by this, but from the few instances I've seen, the people being ousted seem to be those that had questioned tech. decisions. They were people who did badly during our review process.
For instance we have a brand new react server side rendering based platform. I think the performance of that framework is somewhere around 2 concurrent requests per virtual machine. And we're bragging about our performance chops publicly: https://medium.com/walmartlabs/using-electrode-to-improve-re...
Wal-Mart has many problems, I don't think too many experienced engineers is one of them.