> Candidates should be able to pass or nearly pass normal dev hiring bar, and may have some additional skills that are rare among devs (e.g., L1 - L3 networking or UNIX system internals).
They hire devs with ops experience.
They hire devs with ops experience.
I've enjoyed what I've read so far in the book and I get it that there is an opportunity here for Google to market the SRE role b/c they are apparently hard to fill but why didn't they put a chapter in the book of what that dev skill set is?
Or else what dev skill are expected of someone working in this capacity.
Seems like lifting the shroud of mystery would do wonders for marketing a role that is hard to fill.
Literally nothing at Google except third-party code (like Linux kernel) is written in straight C. C++ is very common, though.
Python sucks and is useless. Most things that were written in python are now written with Go.
I guess your question is about what happens if a C++ expert ends up on a Java team, but I don't really know. I happen to have landed in C++ world, which suited me.
This is simply not true in any way.
The reason Python tends to suck is not all really nice libraries are ported to it in any reasonable amount of time. (If you need it, you end up doing the work). Go sucks in new and totally different ways.