[busterarm]

Everyone has gaps in experience.

I've worked in both of these kinds of domains and different kinds of people thrive at doing each. The kind of problems you face are different.

Most of the backend C++ types I've worked with aren't so great at "design for failure" types of environments whereas on the web development side of things I've found people are much more receptive.

I'm working with a few hundred backend engineers who all have a hard time with thinking infrastructure is always available and can handle infinite throughput. They absolutely stink at reasoning about the network. And these aren't dummies -- they're all MIT/Waterloo/etc grads.

[pedrosorio]

> I'm working with a few hundred backend engineers who all have a hard time with thinking infrastructure is always available and can handle infinite throughput.

Could you clarify this statement? Are you saying you work with hundreds of backend engineers:

- who all believe infra is always available and can handle infinite throughput (???)

or

- who can't wrap their head around an environment where infra is so scalable / high availability that it might as well be "infinite" and so they are always looking designing for tradeoffs that don't exist in your environment?

If the former, where do these people work? If the latter, where do these people work?

[busterarm]

You don't have to look hard to find stories of people running up huge cloud infrastructure bills by using it improperly.

Engineers in general poorly understand the connection between their code and resources consumed. Until something bites them and they learn.

I'd say that this is pretty widespread throughout the industry.

[pedrosorio]

I know there are plenty of engineers with those gaps, and they learn from experience, as one does.

My issue was with the statement that all backend engineers you work with (hundreds of them!) have this weakness. Does not match my experience, so I was wondering where you work.

[busterarm]

A mid-sized, already-public SaaS company.