memo_ree

Great points - also, reading between the lines of his tweets, it sounds like the bug was pushed by a team he doesn't lead, so the best he can do is ask them "Please fix this, people are really pissed (at my team) because of this". But to the Image Search team, it's like, why should they do a costly rollback? It's easier for them to just sit back and say nothing, and let AMP soak up the blame on HN. Then they can fix the bug on their normal schedule, without their deadlines being affected.

This most recent change is just a bug in Image Search, at least based on the tweets I read. The extension seems to inspect the AMP article's URL and HTML, both of which are outside the scope of Image Search: https://github.com/da2x/amp2html

> I hate that there is no way for me to disable it as a user

Yeah, seems like you should be able to. Just curious, where would you want that option to appear, and how would you want to see the search experience change as a result?

> AMP is fast because it's incompatible with 99% of the bullshit client cpu heavy tracking and ad libraries, so they don't get included inside AMP pages. > We could have just had that, without all this stupid bullshit CDN redirection/misdirection bullshit.

I agree the world could have faster pages without AMP. What would that take though? Would it take web developers across the world pushing back against including megabytes of extra JavaScript for ads/tracking, at all the companies who are currently using AMP?

Seriously, I just don't get these hateful comments on Hacker News regarding AMP. It helps websites load fast on mobile, and users really appreciate when websites load fast.

So that refrain seems to imply the 20% project must be done as additional work after spending 40 hours a week on the 100% project. My point was you actually can spend roughly 32 hours a week on your main project, if you are performing well, and then roughly 8 hours a week on your 20% project, and still get high performance ratings.

Google has an internal system which allows engineers to transfer to other teams. If what you described happened to me, I would secure a transfer and then report the situation to higher ups.

If you are a $race $gender, Google will hire you. The diverse candidate pool just means you need to work harder on your resume, interviewing skills, etc - since there's more competition.

Exactly, two engineers could have an entirely different experience based on their team. Engineers can transfer to different teams too, though that team will obviously look at the engineer's history of performance.

20% projects have been cut? I wish someone told me that before I started a 20% project which spanned multiple quarters, and still did well in my last performance review.

If an engineer isn't doing well on their 80% project, a 20% project might be frowned upon, that is true.