Is it though? Engineering is providing the cheapest solution that corresponds to what your customer asked. As it goes: anyone can build a bridge with infinite budget, only an engineer can do it for cheap.
A system that's un-necessarily complex for what it does is over built, and under engineered.
I think it's important beyond semantics, because sometimes you have to propose designs that wouldn't be in books, yet they're the cheap and fit with all requirements, and are thus well engineered.
Now the difficulty is to figure the requirements that are not being expressed. "Allowing an occasional resurfacing" and "don't explode when there's icing" are obvious ones; the hard one for our job are "allow for adding another lane" or "allow support for trains as well"... because you know these might come.
> I have to call MINI at some point and demand they fix this garbage
That would never occur to me. Whenever something produced by a large company breaks, I pretty much assume there's no signal possible back to whomever is responsible for the breakage, and that whatever is broken now is broken forever.
To the author's point, they're A-gile, but forgot that the first step in the process was customer feedback
I'm somewhat knowledgable on privacy topics, pasting my answer to another comment:
The EDPB has explicitly ruled on that, when it comes to age verification^1, you should delete: "Trust models are crucial to prevent data breaches in age assurance contexts [...] once the user's age is verified, no record of the personal data used for the age assurance process is kept".
The EDPB has explicitly ruled on that, when it comes to age verification^1, you should delete: "Trust models are crucial to prevent data breaches in age assurance contexts [...] once the user's age is verified, no record of the personal data used for the age assurance process is kept".
They most likely weren't allowed to keep it past the verification per GDPR art.5. Once the passport has been verified for whatever purpose they needed it ("age verified to be > 18yo on 2026-06-12" or "identity verified to be XXXX YYYY"), there is no legitimate use for the passport photo and details anymore, and they should delete it.
> Zero password protection on document storage systems
>
> No encryption for sensitive identity verification data
>
> Public URL access with no authentication requirements
>
> No access logging or monitoring systems in place
Pretty much the bingo of secure storage, even CTF demos make it less obvious. Storing a document that they have no business keeping in the first place, with no security whatsoever.
This comparison makes no sense. When you buy a ticket to a concert you fully expect to be allowed access to said concert. If it gets cancelled because this or that studio owns some random right you fully expect to be refunded.
> I was already renting stuff when video tapes were a thing
Good for you. These guys also propose rental with a rent button, and a purchase button for what you'd expect be purchasing the movie. Do you still not see what the issue is and why the debate on what word means is anything but sterile?
> Or are you just happy being outraged and will go back to your daily life afterwards ?
Wow, this is gratuitous and extremely belittling. I hope you feel good smelling your own farts.
I sent many an email from [email protected], the veneer of the terminal helping, my friends were quite impressed by how good a hacker I was. Good olde days when many DKIM/SPF weren't a thing yet and SMTP servers weren't even authenticated.