Amazing, thank you for writing all of this out. I can see the passion for Goldratt!

These improved your career, I'm assuming? The Phoenix Project really helped me understand 'DevOps', before I never fully grasped the difference between Dev & Ops ( I am still in university and have little practical experience ). Now with my chest puffed out like a bird, I constantly talk about whether I am doing operations or dev work.

I hope the 'The Goal' which I will purchase first will have similar effect, especially since I work on my own startup with a few friends where we struggle with this stuff all the time.

Thanks for this.

Could you explain how kubernetes makes it cloud agnostic? I assume it's a managed kubernetes, but you just have a list of the helm charts and how to re-deploy it exactly like that again?

How do you make sure you are cloud agnostic? Through using HashiCorp vault for example for secrets etc?

I haven't read any of this books yet - I have read the phoenix project where he is mentioned. What book would you recommend starting with?

How does leaving your consulting offer work? Was it just over email, do you have a company set up for it etc?

Yeah so I guess an SRE set up the pipeline, and then the network analysts are simply watching it here.

What have you been learning already? In this specific domain?

It's called DevOps now, but it is primarily operations

I completely agree with it being logic. But obviously skin in the game is what triumphs :)

What were your responsibilities & how did you manage to get the respect of the SWE & Operations teams without experience in neither?

Interesting, is this answer from experience?

Hiring your first full stack is more of a business problem IMO. It is very, very hard.

How are you starting out as an SRE? This is a very senior role imo

DevOps is Development + Operations. Development is SWE, Operations is setting up hardware, maintaining it, monitoring it & automating it.

Choose either Operations or Development to go into first. This 'DevOps' role has been watered down so much IMO. Same way that 25% of the staff at Goldman Sachs are vice presidents.

This is amazing! Slightly unrelated, but how do you guys manage environmental variables for your frontend? Asking since I assume you manage this, do you send each new frontend dev a list of env variables for them to store on their desktops?

How do juniors not know this? Are they not coming from years of experience doing side-projects in uni?

I don't know too much about lazy loading - How important is this?

Do you guys use the file structure in the react handbook as well? I think it's called feature-based structure

Interesting, so designer quickly checks it on mobile, tablet and laptop

render optimisation, how is this typically done?

<div> creates containers.

Having source of truth as a Figma design is great.

Why do you guys hire contractors?

For the last point, why do you want to remove useEffects? I have them for drop-downs from the navbar, so that if the user clicks anywhere else they are turned off.