Hacker Newsnew | past | comments | ask | show | jobs | submit | nitwit005's commentslogin

It's usually just that the core product was built a long time ago, and that's 95% of what customers want.

There's always the option of getting rid of all the engineers working on new stuff, and having a small support staff. Often times, customers would even prefer that.


spotify should do this

> First one was uniformity. Every service deploys the same way.

My current company makes this claim, but it's not true. They also have serverless apps, and also have some services running directly on EC2.

They just think of the Kubernetes deployments as the "standard" way.

> Second was shared, hireable knowledge. K8s is basically a lingua franca now.

People were demanding experience with Kubernetes, long before it was reasonable to expect it. Everyone added it to their resume, because they had to.


If all you are using on AWS is EC2, I agree that it has no value. You should switch to a much cheaper option.

A lot of the comments in this thread are down voted. None of them have anything to do with the content of the video people came here to see discussion of.

He's discussing Anthropic struggling to fix an issue with their own product. He's not the one struggling.

The concept of the responsible party bearing the costs is a good one, but if we're honest about who that is, it's often going to be company leadership.

The person who made the breaking change is often diligently following instructions to get it done as soon as possible.


Yep, also meeting rooms for various clubs. My university genuinely had a wine tasting club that met in the library.

The examples of high impact all seem like things unlikely to receive recognition.

If you save a sales deal, they'll cheer the sales staff. And pay them a commission, which you will receive no part of.


And start to build a relationship with sales that, at least in a B2B firm, can be of significant benefit.

The classic pattern is they become a larger company, and either those processes stop working well, or a custom solution becomes worthwhile due to scale.

The row count limit in Excel has been hit many times over the years.


You're both criticizing management for not knowing who's doing important work, and also for spending time talking to engineers to understand what's going on.

Most solutions to understand what's going on, in detail, are naturally going to be quite time consuming.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: