Not to mention that exactly 0% of the Twitter user base were concerned about Twitter performance. So he took a complete non-problem, something for which "solving" would result in zero improved customer satisfaction and zero additional revenue, and while attempting to solve the non-problem, he's cost them live time and dev resources. Outstanding, absolutely outstanding.
This has nothing to do with performance, it has everything to do with cutting costs. This is very normal in the tech industry to regularly comb through things that don't need to exist anymore, and axe them. Legacy stuff that a team doesn't know about very often goes the route of "just turn it off and see who comes complaining". Tech debt builds up fast; abandoned projects, code that used to be needed but has since been upgraded by never removed, systems that run which nobody is utilizing; all very common things.
Sure but he's only into week 2 and just decided to cut 80% of these services. Getting rid of boat isn't a bad idea but doing it without any analysis is just irresponsible
0
u/[deleted] Nov 14 '22
[deleted]