←back to thread

1114 points namuorg | 1 comments | | HN request time: 0.294s | 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 #
weatherlite ◴[] No.43680397[source]
It probably just didn't have enough economic value for the company, from your explanation of the role I'm not sure I see the value either. The guy probably earned enough money in a few years that would take me 15 years of work, I'm not sure this as a "personal tragedy".
replies(2): >>43680852 #>>43681152 #
azangru ◴[] No.43681152[source]
> from your explanation of the role I'm not sure I see the value either

Google has traditionally had a fair number of developer relations engineers. Chrome team alone has several. The current devrels include Una Kravets, Bramus van Damme, Rachel Andrew, possibly Jecelyn Yeen, Oliver Dunk, Matthias Rohmer, probably some others... They help prioritise new browser features through developer feedback, document new features, maintain documentation at web.dev, spec up new features and represent Google at various standardizing bodies, write walkthroughs and tutorials, build demos to showcase new browser features, make explanatory videos, give conference talks, and generally keep us, web developers, up to date with modern browser best practices.

Their value to web developers is immense. Their value to Google is possibly in that good devrels are a living advertisement of web technologies in general, and Chromium-based web browsers in particular. The better developers know browser features, the more attractive and capable UIs they can build for the web, the more consumers will be attracted to the web (including Chrome), and the more money Google will ultimately make via advertisements.

Adam has been so great in this role that it does not make sense to me that Google decided to cut specifically his position.

replies(1): >>43681301 #
1. weatherlite ◴[] No.43681301[source]
> Google has traditionally had a fair number of developer relations engineers

I wish them all well, but things can change fast depending on how the economy is doing and where the company is headed priority wise.