4 ms·
I still do not understand why twitter needs one. Fire everyone, bring on a skeleton crew of engineers to fix bugs, and maybe 4 product engineers, a couple manag
by michaelvoz 10y ago
I still do not understand why twitter needs one. Fire everyone, bring on a skeleton crew of engineers to fix bugs, and maybe 4 product engineers, a couple managers and a couple designers. Boom, instantly ultra profitable.
- paulddraper 10y agoAnd no one to work the advertising deals? You're leaving money on the table with zero sales staff.
- MichaelBurge 10y agoYou probably need dedicated account managers too. I imagine the White House Twitter account is willing to pay for support.
- hackaflocka 10y agoIt would make too much sense, and the liberal know-it-all anal-cysts' heads would ass-plode.
- dang 10y agoSince you've ignored our repeated requests to stop posting uncivil, unsubstantive comments, we've banned your account.
- hackaflocka 10y agoDoes that mean I can't be downvoted any more?
- trprog 10y agoLikely part of their valuation is built around expected future growth and innovation. It becomes hard to maintain that story if you cut your engineering too deep.
- flurdy 10y agoLOL. With that amount of users and exposure, they would need a huge legal team to handle all the complaints from users, companies and governments. And an even larger customer service team. So a tiny product team, with legal and CS departments of 200+ is not going to be a well balanced company. You would need quite a few engineers just to handle tweaks requested by legal and CS. Just a few engineers to handle the mature (ie probably spaghetti) ecosphere of systems in their architecture is never going to scale. Nor to just stop it falling apart, never mind progressing any new features. From their talks about their architecture, their massive "Source" repository etc its sounds like they had 1000s of commits per day across hundreds of systems. Ie like many larger companies. To keep up that velocity would need a lot of developers and overhead staff. Even if they cut away "nice to have" systems, sunset a lot of apps and projects, and focused only on a lean core that would still be a huge architecture, which needs X amounts of staff to maintain and progress. What X is a I don't know. Maybe 50, maybe 200, maybe 1000.