I think the twitter-hate was usually because Twitter started with a naive Rails approach on Joyent and would fail whale constantly in the early years.
Just recently they blogged how they finally completed a rewrite that improved per node performance to 100,000 messages per second instead of a few hundred - a better than expected result. Its just a bit OCD inducing how they had to solve problems of their own creation for a long time instead of "doing it right from the start".
I offer no opinion whether or not they were being smart and pragmatic or incompetent hipsters in the beginning.
Its just a bit OCD inducing how they had to solve problems of their own creation for a long time instead of "doing it right from the start"
That's a really, really silly thing to get annoyed about, and flies straight in the face of lean, agile and MVP. I'd wager that if Twitter had "done it right from the start" then they wouldn't be around at all today.
> and flies straight in the face of lean, agile and MVP
It all depends on how complex is doing something right from the start, and how right must it be done for you to stay out of trouble. Twitter had a really naïve approach when it started. Had they started with a slightly better (not necessarily harder) approach, they'd have had far less problems at a much later time.
MVP has a "V" in the middle. Twitter only survived because their V was extremely flexible.
Just recently they blogged how they finally completed a rewrite that improved per node performance to 100,000 messages per second instead of a few hundred - a better than expected result. Its just a bit OCD inducing how they had to solve problems of their own creation for a long time instead of "doing it right from the start".
I offer no opinion whether or not they were being smart and pragmatic or incompetent hipsters in the beginning.
Edit - Found it, here's the post: https://blog.twitter.com/2013/new-tweets-per-second-record-a...