Yeah that’s mostly what I’m referring to.

Backups are pretty easy, but service availability and failovers across cloud providers is stupid difficult. Not really from a compute standpoint but mostly from a data consistency/transactional standpoint.

However, if you are using vendor specific services like AWS connect then you have to build and maintain multiple deep integrations into those services which effectively doubles your engineering efforts.

Good news, they have these, and you even get paid to do it!

Not nearly enough mind you.

Cool 👍

Multi-cloud is a significant amount of effort to pull off.

Being on one cloud provider across multiple regions is often plenty of redundancy.

Being available across multiple cloud providers is really REALLY difficult

Honestly surprised C# isn’t on here? It’s still one of the “big 5” languages, and .Net touts it’s incredible performance on the regular.

The number of new devs who complain about having to write a unit test is too damn high

• Or writing integration tests
• Or passing CI
• Or following repo conventions
• Or following standards
• Or adhering to domain guardrails
• Or in adding monitoring
• Or in not logging everything as info
• Or in actually documenting features
• Or in receiving critical PR review
• Or in addition input validation
• Or in not trusting the client

…etc

Honestly most devs… Kinda suck at their job. This is becoming more evident to me every year

Why would it be on each dev to setup?

Your repo can, and should, include workspace settings for major editors that provide a uniform experience for anyone onboarded to the platform.

I agree that precommit hooks are good for uniformity. But slow pre commit hooks are frustrating, they are also often turned off. Your CI will always be the last gatekeeper for linting/formatting rules regardless.

Making precommit hooks slower means more devs disable them, which is the opposite of what you want. Save them for simple, read, checks and validations that can run in < 1s for even huge changesets.

Or on save even. Slow pre commit hooks suckkkk

That’s not a linting problem that’s a formatting problem.

That project should have automatic formatting on save setup.

Linters are not necessarily formatters they’re solving two different problems and are becoming increasingly separated in their toolset.