> The only way an international business is going to consider investing in French workers, for example, is with relatively low salaries to offset the inability to fire them.

> Strong worker protection? Expect fewer highly paid roles (wage compression)

For European startups it’s different motivation. Lower salaries than in USA are an advantage, but job security isn’t a show stopper. First team is hired in fixed contracts, which may be converted to permanent with growth. In scaling phase you add external support, with e.c. 20% of workforce coming from outstaffing, so that you can react on the market and scale down when needed. If you are big enough to be called international business, you will not hire in one of the most expensive locations in the world (USA) unless you have a good reason. There exist other easy-to-fire tech hubs, and it’s not a big problem in Europe anyway (it’s just some more effort to execute, but even with payouts it’s probably cheaper than in US).

> Make it difficult to evict tenants? Expect more stringent requirements from landlords

In Europe there’s less homeless people. It doesn’t work like that.

>Enact rent control? Initial rents are going up, new builds are disincentivized.

It’s not rent controls that make markets inefficient. They are reaction to NIMBY regulations and disincentivized home ownership like in Germany. Root cause is uncontrolled extraction of scarce resource (land) and the solution is actually to scale down for-profit rental market while aggressively subsidizing ownership and construction.

And the reason is not just rules of engagement - such targets simply have negative value for attacker.

OTOH, Spring Boot is a huge pile of various loosely coupled framework connectors, web, queues, security, databases etc. Some of them are of good quality, some are not so good. It is that uneven mix giving the perception that Spring is a mess.

Looks like you never worked with a decent QA team and do not understand the full scope of quality management. They have plenty of creative tasks not aligned with other roles.

1. Quality management is a continuous process that starts with product discovery and business requirements. Developers often assume that requirements are clear and move on to building the happy path. QA often explore requirements in depth and ask a lot of good questions.

2. QA usually have the best knowledge of the product and help product managers to understand its current behavior, when new requirements suggest to change it.

3. The same applies to product design. Good designer never leaves the team with a few annotated screens, supporting developers until the product is shipped. Design QA - the verification of conformance of implementation to design specs - can be done with QA team, which can assist with automation of design-specific tests.

4. Customer support - QA people are natural partners of customer support organization, with their knowledge of the product, existing bugs and workarounds.

And just a story: on one of my previous jobs recently hired QA engineer spotted number error in an All Hands presentation. That was an immediate buy-in from founders. :)

It happened because Russian empire (and German empire) lacked state security apparatus adequate to the threat. It was fixed by most authoritarian states after that, so e.g. Soviet Union survived for 70 years despite many popular uprisings, which happened almost the whole time of its existence. It went down only when elites in Moscow destroyed it from within.

I have explained already a few times why and what context matters here. Are you struggling to understand it or just avoiding it?