Or if you want compare vibe coding with any technology, like electricity. Sure, that one person got electrocuted or their house burned down. But it's just so useful, and "somehow civilization continues to function". I guess they should've known better.

I'm personally not comfortable hyping up the benefits whilst ignoring the risks, especially for lay people.

The system you describe is hardly unique to Germany, so this just reads like hyperbole or inexperience travelling.

> Classic example of government run workflows

This I can agree with.

You'll want a dev board, which has the chip plus some supporting components on it. The Raspberry Pi Pico is a good choice because it's so widely used and well documented.

If you care about Rust, you'll also want to get the Debug Probe. Worth the money.

If you don't care about Rust, any Adafruit dev board should run CircuitPython, have good documentation, and likely some projects you can start with. The reason I don't recommend these for Rust is because many of their dev boards do not "break out"/make available the connections for a debug probe.

Edit: Having a project you want to do is good, but just making an LED blink can be magical, too, especially if you haven't done anything with hardware.

That's for occupants.

> Furthermore, the NHTSA doesn't do most testing.

Which is why I quoted IIHS and other non-US testing.

> NHTSA standards

Which standards are for e.g. pedestrian safety? The hood ornament thing?

> That's misleading. They don't test for pedestrian safety as part of the normal tests. But they test for it generally

No, it isn't and no they didn't/don't. E.g. GAO report from 2020 [0]:

> NHTSA’s last substantial update of NCAP was in July 2008 (with changes effective for model year 2011 vehicles). This update established additional crash tests and technical standards to protect vehicle occupants, but did not include pedestrian safety tests.

Or from NHTSA itself in 2022 [1], although note this is a "proposal" and "recommendations":

> For the first time ever, NCAP includes technology recommendations not only for drivers and passengers but for road users outside the vehicle, like pedestrians. The proposal [...]. We look forward to reviewing the comments we receive and considering them as we complete this important work.”

They will/might, by adopting Euro NCAP [2]:

> This final decision notice adds a crashworthiness pedestrian protection program to the New Car Assessment Program (NCAP) to evaluate new model year vehicles’ abilities to mitigate pedestrian injuries. Based on its previous research, NHTSA concurs with and adopts most of the European New Car Assessment Programme’s (Euro NCAP) pedestrian crashworthiness assessment methods [...]

> These changes to the New Car Assessment Program are effective for the 2026 model year.

But as of yet, this does not appear on their NCAP ratings: https://www.nhtsa.gov/ratings/resources-related-nhtsas-new-c...

[0]: https://www.gao.gov/assets/gao-20-419.pdf

[1]: https://www.nhtsa.gov/press-releases/five-star-safety-rating...

[2]: https://www.nhtsa.gov/sites/nhtsa.gov/files/2024-11/NCAP-Fin...

> NHTSA conducts frontal, side and rollover tests because these types account for the majority of crashes on America's roadways.

> IIHS tests evaluate two aspects of safety: crashworthiness — how well a vehicle protects its occupants in a crash — and crash avoidance and mitigation — technology that can prevent a crash or lessen its severity.

> As well as assessing how well cars protect their occupants, Euro NCAP tests how well they protect those vulnerable road users – pedestrians and cyclists – with whom they might collide.

> It is completely normal for staff to have to work 24/7 for critical services.

> Not only is it normal, it is essential and required.

Now you come with the weak "you don't have to take the job" and this gem:

> An employee’s lack of boundaries is not an employer’s fault.

As if there isn't a power imbalance, or employers always disclose everything or chance their mind. But of course, let's blame those entitled employees!

But to parent's points: if you call a plumber or HVAC tech at 3am, you'll pay for the privilege.

And doctors and nurses have shifts/rotas. At some tech places, you are expected to do your day job plus on-call. For no overtime pay. "Salaried" in the US or something like that.

And that's assuming the codebase and all dependencies have correct type annotations.

Comparing privacy laws by example is beyond ridiculous. And there are big cultural differences what "privacy" entails.

Are they? More so than usual? This rhetorical device or similar seems to be always used, no matter the situation or time.

"Criminals are so sophisticated, our jobs are so hard, we need more power" - every police force ever.

"We actually need fewer capabilities and more checks and balances" - no police force ever.

> Now they are facing a situation where not just virtually all communications are encrypted

No, they aren't. Phone is unencrypted. Email is unencrypted. SMS is unencrypted. Some messengers are unencrypted.

Communications can be encrypted; I guess only criminals do that. Or banks. Or businesses. Or the government.

> but virtually all forms of evidence that document a crime are encrypted.

No, they aren't. Etc

This thread started by parent telling you how it is in Germany. Meanwhile, you have provided zero data or objective criteria yourself...

If by "my country" you mean the US, it's perfectly happy with taxation without representation. Current examples include the District of Columbia, certain situations in U.S. territories, and permanent residents. Past examples e.g. women.

Nit: You mentioned it can be used "everywhere". That would be a useful feature! But while it's kinda true, there's some quite big limitations IMO