They come to Product from the mountain-top with their holy scriptures (the Google SRE book), prescribing surface solutions to problems with deep roots (pray it away with SLOs).
SRE 2.0 needs to make the embedded model work.
1,546 karma · joined February 23, 2016
They come to Product from the mountain-top with their holy scriptures (the Google SRE book), prescribing surface solutions to problems with deep roots (pray it away with SLOs).
SRE 2.0 needs to make the embedded model work.
Ultimately, the answer ties back into the identity question: what is SRE?
Pay is a rough signal on what a company expects from SRE. If SREs get paid as much or more than Software Engineers, it is a good sign. Yet even that signal is not accurate. I know highly paid SREs stuck in Ops Hell. You could not pay me enough money to do a job like that. It is also not sustainable because eventually the company will fire you and replace you with a lower paid employee who can do that job just as well.
I strongly oppose organizations that have SRE separate from Software Engineers. I strongly believe that SREs must be fully integrated into Software Engineering teams (aka the embedded model), with the same reporting lines as their product colleagues.
Keeping SRE organizationally separate has done a great disservice to SRE. SRE 2.0 needs to tear down the mini empires that SRE 1.0 built and get back to software engineering.
It wasn't clear to me by looking at the pages themselves. I hope usability will not be a huge issue and negate the benefit of this open access!
Launching new products is insanely difficult, if not impossible, in large organizations - even in the most esteemed tech companies. And yet that is how many companies die, because they cannot overcome the internal inertia to launch something new.
Yet when I buy them at the grocery story, I see no sprouts.
Given the time it takes to get from the farm to the grocery store, no doubt these potatoes have been sprouting during their journey. Does the grocery store remove the sprouts before they put them out for sale?
I doubt that there were enough slaveowners or slaves in charge to contribute anything substantial to the management profession. It is an interesting tale in today's sentiment of antiwork.
On the Internet, you have Google, Amazon, Reddit, Facebook, Twitter. Much of the good content is hidden in their secret gardens (Facebook, Twitter, and increasingly Reddit).
Discovery needs to be reimagined. Google search directs traffic but now everyone has a SEO manager to get their site to the top. If we want to see the Internet like before, original content needs to be prioritized over content like Pinterest, without needing to do anything special.
I tried that calendaring system a few times. It did not work for me. To-do lists are easy, comfortable, familiar. They may not work for millionaires. They work for me.
I guess most technologies are like that. Once it is written, once the major bugs are caught, few revisit the code anymore.
Looking at the front page, most links are produced as part some commercial effort. I miss the old non-profit part of the internet.
I personally view the old IRC (Efnet!), BBS, chat rooms, ICQ as the earliest form of social media. And just as addictive - I couldn't wait to get home from school and jump into a chat room. I checked it as often as I did Facebook later on.
I do a lot of things that are unhealthy, in moderation. Certain TV shows I watch are toxic to some extent, but I still watch them.
Reddit, arguably, is more toxic than my version of Facebook - but it is strangers being toxic, and zero FOMO (Fear of Missing Out) which is prevalent on Facebook and Instagram.
This was pre-2013. So perhaps the proprietary connector was a reaction to the cable?
I hate the soldering, too. I'm just offering an explanation that may make some sense given the context.
A few years ago, Netflix had a reputation of paying very well to lower level senior employees (think L5 and L6), but not as competitively for higher level employees (L7+).
If we had to absolutely deliver by a fixed date - a rarity - we broke the task down in parts that could be estimated, identified the dependencies between tasks, and kept management informed if those dates could slip.
This lightweight process worked pretty well if we had to implement it. There was a lot of trust put in the engineers.
The companies that do not do that are exposing themselves to unnecessary legal risk in the future.
Thank you for eloquently stating this. I've thought a lot about this as well.