Hey VirusNewbie, thank you for your response! A few more questions if you don't mind.

Did you read the SRE handbook before applying?

How do you decide who gets alerts (or are devs never on call)?

>Did you read the SRE handbook before applying?

Yes, but it wasn't really necessary. Google isn't trying to hire SREs, they're trying to hire SWEs and specialists who they can turn into SREs, if that makes sense. Though I'm sure SRE experience elsewhere helps, they are still expecting SWE level coding/algorithms etc.

>How do you decide who gets alerts

SREs will be assigned to a team that has a rapidly growing service or essential service (or both), and they will be the primary team that takes the alerts, while the developers have a slower SLO (though still oncall rotations for them).

That makes sense to me, honestly. It's probably easier to take a SWE with good CS fundamentals and mold them into an SRE than the other way around. It also means more optionality if the SWE turns out not to take to the role.

Persona do not seem to be competent guardians of such a trove of private information.

https://vmfunc.re/blog/persona

You can follow the discussions between that blogger and the CEO btw - https://x.com/rickcsong/status/2025038040599810385

    Persona was not hacked. No database was breached.  Frontend code source maps were leaked, 
    which means unminified variable names were exposed revealing all the names of our features. 
    These names are already publicly listed in @Persona_IDV's help center and API documentation.

Thank you so much for sharing this. Not only is it a great post, but the site invokes such warm feelings of an internet long lost.

True, I love the little cat chasing the mouse in particular.

That's Neko! https://en.wikipedia.org/wiki/Neko_%28software%29

just a warning: when you press "continue" it starts blasting music

as much as I like the design and the post, that website causes a massive memory leak in Firefox for Mac

"reveals", not "causes". The memory leak, if it truly exists, was already present. It's not a website's fault for triggering it.

I initially thought this was by David Beazley, the python/rust guy.

Linking to a screenshot posted on twitter is a terrible way to share code.

Unrelated to the article, and I can't seem to reply to the comment, but clicking on the archive.today link while I'm on holiday in Italy gives me a warning that it contains child pornography.

https://imgur.com/a/PXNY7vp

I'm not sure if it's related, but the operator of archive.today has done odd things with DNS in the past, such as blocking DNS requests from cloudflare because they don't forward edns information.

It's an archiving site. Probably someone archived some child pornography there, and the Italian authorities decided the sensible thing was to block the whole domain.

When managing large numbers of Dell rack mounted servers, a flea power drain is something you become very familiar with.

Growing up, people with the surname Campbell often got the nickname soup or soupy.

Perhaps Augury.

In case you haven't read it - https://folklore.org/Round_Rects_Are_Everywhere.html

Desktop browser might be smoothing things over here, but I tried to load this on my android tablet and had to add www to get the domain to resolve.

This is brilliant, thanks!

Unless you have some information you're not sharing, this is a pretty horrible thing to say.

I don’t feel like it’s horrible. If one of your founding members is focused on getting rich quick while the rest are trying to invest in the company long-term, then his departure very well could have helped the company ultimately succeed.

Is it horrible to suppose that someone might not be well-suited to the task of driving a business from nothing to a national concern? Because I personally suspect that of most people, including myself, and don't think of myself as particularly mean-spirited.

Also, the offspring of the man in question identifies an aspect of his temperament that led to things turning out the way they did.