SQL was explicitly designed to allow "normal humans" to query the database. Nowadays even "normal developers" aren't able to use it properly.
tias
joined 1 year ago
Oracle has a product called Oracle Policy Automation (OPA) that it sells as "you can write the rules in plain English in MS Word documents, you don't need developers". I worked for an insurance organization where the business side bought OPA without consulting IT, hoping they wouldn't have to deal with developers. It totally failed because it doesn't matter that they get to write "plain English" in Word documents. They still lack the structured, formal thinking to deal with anything except the happiest of happy paths.
The important difference between a developer and a non-developer isn't the ability to understand the syntax of a programming language. It's the willingness and ability to formalize and crystallize requirements and think about all the edge cases. As an architect/programmer when I talk to the business side, they get bored and lose interest from all my questions about what they actually want.
I want something that runs a small local LLM for text prediction, but there's no proprietary alternative for that either.
This has to be a joke
Unfortunately the license agreement for .Net forbids publishing any kind of benchmark results.
WASM? Are you talking about WebAssembly?
No argument there. But apparently there's a market for it.
More like, the devs already knew but some middle manager promised they would remove it without understanding the ramifications, and now they've been schooled.
Is it really too much to ask that apps/devices are made secure from the ground up?
In a way, yes. They can and should definitely be made with security in mind from the ground up. But they will never be totally secure, and a necessary part of what constitutes a "secure product" is to continuously and quickly patch security issues as they become known.
Surely that’s just a secure end-to-end encrypted connection?
I would bet it's still a bit more than that. But even if it's just a secure end-to-end encrypted connection, here is the list of vulnerabilities fixed in OpenSSL (which is probably what they use for secure encrypted connections). It's five so far in 2024. Then there's some OS kernel below that which can have security issues as well. The Thermomix probably also has user authorization components and payment methods, plus various personal information that has to be protected under GDPR.
They hate engineers because the engineers ask difficult questions that somebody needs to answer in order to really automate a process, and they take the time necessary to do so.