←back to thread

1114 points namuorg | 1 comments | | HN request time: 0.21s | source
Show context
azangru ◴[] No.43679631[source]
I've skimmed through the comments; and seen that most people have commented on the cog in the machine thing, or on layoffs in general and how they suck.

To me, the shock from this blog post was about seeing a Chrome developer relations engineer whom I have grown to admire and who has been doing a stellar job educating web developers on new html and css features, get the sack. He was one of the best remaining speakers on web topics at the Chrome team (I am still sad about the departure of Paul Lewis and Jake Archibald); and produced a lot of top-notch educational materials (the CSS podcast; the conference talks; the demos).

What does this say about Google's attitude to web and to Chrome? What does this say about Google's commitment to developer excellence?

I understand that this is a personal tragedy for Adam; but for me personally, this is also a huge disillusionment in Google.

replies(13): >>43679884 #>>43679890 #>>43679922 #>>43679964 #>>43680265 #>>43680397 #>>43680859 #>>43681914 #>>43682871 #>>43683096 #>>43683779 #>>43684115 #>>43684150 #
gtirloni ◴[] No.43679884[source]
It says they are getting ready for the future when some govt agency splits them up and they are shedding the load now (the areas they will have to sell).
replies(1): >>43684709 #
supportengineer ◴[] No.43684709[source]
If you're being forced to sell something, wouldn't you want to maximize its value? Wouldn't you retain the most valuable people?
replies(2): >>43692890 #>>43692989 #
1. FromOmelas ◴[] No.43692989[source]
Not if they might become a competitor, or thrive (proving that the sale was a good idea). Better to keep them weak and likely to fail.