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.

This is how I’ve always used hardware. Y’all out here buying up new parts each year they release?!?

It’s like iPhone crowd energy, but for PC parts I suppose.

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

I work remote (Going on 9 years now) and I miss a sense of community. Do I want to stop working remotely? Hell no, screw that. But two things can be true the same time, I can enjoy and encourage them at work, dnd I can also miss a sense of community.

I think it’s okay to hold this opinion because it’s individual to everyone.

This just comes across as propaganda

Being dismissive and pulling the rhetoric that this is propaganda is toxic as fuck.

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.

Practice practice practice, always challenge and improve on your foundational skills. Everything else gets easier. Write code and solve problems, struggle through it in whatever way works for you. There’s not really a shortcut to getting more experience than to put in the work.

It’s especially important to try and do things the “right way” as a learning/growth tool. It will take longer, and you’ll rewrite your code multiple times, but the next time you encounter a similar problem you suddenly know exactly what to do and the constraints around the problem.

Do this often enough and you’ll find yourself having a general idea of how to solve just about any problem you come across, and how to do it elegantly.