How much would you pay for it for lifetime value?
Context: I had built very similar tool myself & can implement a few more features to make it self host possible to sell license.
Google is anyway reducing SRE task force & is planning to completely eliminate SRE role. There has been recent announcement already & have already started the move - https://archive.ph/YWp4O
The archive link is busted for me, but that sounds like a bad move. 90+% of SWEs are bad at and hate SRE work, and vice versa.
The rare ones that can do a mediocre job at both (and that won't burn out and switch jobs if told to do both) are usually not capable of doing an excellent job at either.
Using analogies from pretty much any other field shows how dumb it is to combine SRE and SWE, or fuse DevOps (or, god forbid DevSecOps) into one rule:
- Would you have a surgeon drive an ambulance?
- An expert car mechanic manage fleet scheduling and logistics?
- Tell a salesman to design marketing graphics, and have your graphic designer manage high-value customer accounts?
Google is anyway planning to shut down SRE role & transitioning them to SWE role predominantly. A few months back there has been announcement already & one of the reflections is to start with reducing the numbers - https://archive.ph/YWp4O
It has indeed been a strange time for Google SRE recently. However, they're definitely not planning on shutting down SRE - at least, if you can trust what Google leadership's actual explanation of what that meant.
Supposedly, the ratio of SRE to product eng had been growing slowly over the years. The KR to "readjust" that ratio was to bring it back in line with historical norms, i.e., to ensure that SRE continued to scale sub-linearly with SWE/systems. This had (primarily) two facets.
First, it gave SRE teams an effectively-blank check to reevaluate their existing dev engagements and jettison the ones that weren't working well.
Second, it pushed to eliminate old tools/systems/platforms and converge onto the more modern stuff, like Annealing [1]. Fewer crufty platforms means fewer teams needed to run them, and improvements in those platforms have broad impact.
Anecdotally, my own sub-org (within SRE) is growing at the moment. Not by a huge amount, but growing nonetheless.
This doesn't say SRE is shutting down, it says that they're changing the ratio of SRE to SWE. One thing to realise about Google is that the technology is increasingly unified across the company. 10 years ago everything worked in different ways, but now there are very standard technologies and paths, and naturally this requires fewer SREs to the SWEs developing the products. I don't think this is a bad thing, and in the layoffs SREs have not to my knowledge been hit any harder than SWEs.
I can't read tea leaves but I'm fairly confident they're not shutting down SRE. They want to get back to sublinear scaling and move away from the "devs create crap, bribe SRE (headcount) to babysit it in production". It was a major anti-pattern for the role.
The Builder design pattern is a popular object-oriented programming design pattern that separates the construction of a complex object from its representation.
Budgeting is a crucial aspect of personal finance that can help individuals take control of their money and achieve financial stability. Creating a budget involves understanding your income and expenses, and making a plan to allocate your funds in a way that aligns with your financial goals. A well-constructed budget can help you avoid overspending and debt, and set you on the path to financial independence.
Self-care is often seen as a luxury, something that can be put off until we have more time or energy. But the truth is, self-care is essential for maintaining our physical, mental, and emotional well-being. It is not only about pampering ourselves, but also about taking the necessary steps to ensure that we are able to show up fully in our lives and perform at our best.
