yellow_mixer

Writing a tickets is usually not owned by engineering. Some engineering managers may do this work, but it’s usually owned by Product while Engineering helps refine and turn tickets into actionable work. Engineering also doesn't negotiate features. Engineerings job is to help product determine LOE and help Product prioritize requirements for a future release. Again, strong engineering leads can do this work, but I believe Product Owner should hold these responsibilities.

What you are describing sounds like a Technical Product Manager, not a tech lead. The minute you have them “run a team”, you are combining both roles into one.

If you’re looking for a good read, pick up a copy of Tony Fadell’s “Build”. There are a few interesting chapters where he writes about the process of selling Nest to Google.

One issue I see with your example. You say “had the IT guy chosen to work”. This statement assumes OP can just pickup more hours easily. That is not the reality. If it’s a salary based position, OP can’t put in more hours just to earn additional income. If it’s a hourly job, OP all can’t put in more hours. Usually anything outside 40 hours is considered overtime and would need to budgeted and approved by the employer. OP could use his IT skills to find more work at that rate for a different company, but now we are back to the passive income example. TLDR. The math makes sense, but the example falls flat in reality.

May I ask what you are using for endpoint management? Are you using JAMF, Intune, something else? Are you using an always on VPN to all users? All cloud based or on-prem infra? DNS security? Endpoint protection?

Thanks for posting the guide!

That title is both misleading and untrue. Infrastructure as Code is exactly that, a way to define your infrastructure definitions code. There is nothing cloud specific about that concept. You can easily write Terrform to work with VMware instances on-prem.

Sumo Logic sales once sent me a targeted email asking if I needed help getting the most out of my AWS S3 Load Balancer logs. The creepy part is I just created an S3 bucket the previous day that had the strings “load balancer” and “logs”. They must be scanning S3 bucket names for key words and maintain or pay for a list of AWS account id mappings to likely owners.

The increase in price is well worth it for our team to not have to manage any servers.

How does this not burn his legs off?

What else do you think it needs. I’ve been playing around with v1.5 the past few days in Grafana and I like it’s simplicity. Grafana now has a Loki datasource which is nice.

It’s also much easier to hire engineers to develop and maintain theses platforms.

How much data are you sending and ingesting?

How are you running it? On AWS? What’s your infra look like.