agounaris

Where's the AI stuff? :D

This model seems super expensive! I interpret it as traces on steroids which will make query complex and slow!

A lot of businesses haven't even nailed simple histograms with prometheus. I wouldn't like observability to become a full set of problems on its own!

Also timeseries is powerfull in observability because a lot of issues can be represented as cheap counters, gauges and distributions. I want to see a paradigm complimentary to this simple principle instead of producing nested documents with nested objects.

a 2-9% improvement at global scale is insane! This is not a small number by any means.

Starting with the example, I find it counterproductive because our brains are always going for the condition first. (or my brain)

Waiting on a traffic light the thinking is "if light is red/green, then wait/cross" its not like "don't cross unless its green".

Also if there is only one obvious way to do things it's a productivity boost! I cannot stress enough how many times we have debated coding styles, wasting precious development time! No customer cares of your coding style! If you are an engineering who cares more about the length of a line or the import order instead of a critical feature for the customer, you have to rethink the priorities.

I kind of see this as just another yaml abstraction on top of configuration templates. This is not new or different in any way from what we have now.

What I don't understand with patent trolls is how this will even go a trial? How does this work?

There is a random lawsuit therefore you'll either have to pay or go to a trial? Who accepted the lawsuit in the first place and based on what legal ground?

"I kept freaking out and yelling in chats"

I think the interviewer is the problem....

Terraform could have been stateless if the target provider was stateless as well.

Having said that I don't mind state at all! There is always a storage layer and a schema somewhere storing some kind of information.

I was expecting to find some interesting thoughts on this one, but its the usual rant of the "freelancer" who does not understand what production means!

Yes big companies have productivity issues, however they have to create software which will outlive most engineers working at the business. You cannot reach the SLOs of google by hacking something together in 2 months!

Excuse me but I don't see in there any reference to what made peloton stock "actually" explode which was the enforcement of wfh. This is a VERY biased deck.

Is there any practical example on this? Whats a common use casE?

This could be one of the reasons why tech interviews are awkward. Most of them are "optimised" for tall and fat engineers but what you actually get is "luck of the draw" T shaped engineers on random specialties that you may not even need, with the assumption that the T shaped engineer can be transformed on demand to a short and fat or tall and skinny.

The author is very cynical on this series for businesses but I think there is a lot of truth in those writings. There is something fundamentally broken in the way we govern software products. From the interview process to the evaluation of the individual.

No engineering organisation can survive with just engineers. For many reasons. This limitation requires some roles to be there to support this process.

I think that most businesses practice process management. A person is there to make sure the team is compliant with the way the CEO, the board, the VPs etc, want to run the business.

What if we ban the term "manager" completely and instead focus on self organising teams and naturally elected leaders. Those leaders will go down with the team or be rewarded with the team. What if we treat product development like a well organised heist! The mastermind, the hacker, the explosives expert etc. will equally split the profits if this is job done well.