guitarbill

Sure, we can ignore that specific example, and that software has an effect on the world, and that people have been trained to expect software to be deterministic and accurate.

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.

One counter-example is the Horizon IT scandal. Obviously, you didn't say this directly, but "only a few people died/were affected, somehow civilization continues to function" maybe isn't the best argument.

> Germany has a very sad and weak airport security story.

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.

I'm a fan of the RP2040 chip. It's a good trade-off between being simple and capable. There are more powerful chips like the STM32's, but frankly there are too many variants and their data-sheets are nightmarish. And there are simpler chips like the Atmel AVRs, but the tooling sucks. ESP chips are also good, but I haven't kept up with them so can't give much advice.

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.

I really like the idea... but I have to admit my first visceral reaction was "I hate this". I think it's because the tone and style is quite infantile/childish. A good experiment nonetheless. Maybe there's a middle ground somewhere?

You aren't wrong on either; Germany's tax law is insanely complex but also many people don't want to change the tax law as they can deduct a million and one things.

Downvote or not, it's true:

> 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.

First, you try to normalise it:

> 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!

Nice try at guilt-tripping people doing on-call, and doing it for free.

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.

As far as I can tell, the author isn't claiming e.g. all of Usenet or IRC was affected. Only that this issue has been happening to communities for a long time in many different online places.

Sorry, it's not even close to Rust. Or even C# or Java. It can't provide the same "fearless refactoring". It is better than being blind/having to infer everything manually. That's not saying much.

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