Hacker News Reader

Comment by MisterPea | Hacker News Reader

I agree, but is Twitter really suffering with any engineering problems? I generally would like to see a CTO come in charge but here's a unique case where someone from product might be more suitable.

View on HN

Their web video player is still horrendously bad and still haven't fix their buffering problem for years.

If I had a dollar for every pixel I see in twitter videos I'd have two dollars which isn't a lot but it's weird that they still somehow call them videos.

yes, Twitter is crawling with bugs and problems of scale (with an obvious lack of user support).

see /r/twitter for a summary of issues people see on a day to day basis.

In that case, why would it make any sense to promote the person who was ostensibly most responsible for curing those ills?

you ever hear the theory about failing upwards?

https://en.wikipedia.org/wiki/Peter_principle

edit: I think I got it wrong. maybe this is a closer fit:

https://en.wikipedia.org/wiki/Putt%27s_Law_and_the_Successfu...

Using their API is still a nightmare.

That's still fundamentally a product problem unless you're having issues with the API's behavior (vs its design)

I agree, just think that a developer-first culture would not allow it to happen.

Twitter recently rolled out full support for their v2 API along with improvements to the usage policy, and the ability to get started quickly with essential access. What issues do you have with the API?

Reply on news.ycombinator.com