2,113 karma · joined September 25, 2022
You can see in these pictures, where every input and output is a real physical thing, just how much density of information was required for Operators to process. As we moved to computer screens representing the same, those original screens would represent these control room layouts faithfully (and you can understand why, training an operator must have taken ages; retraining is not palatable).
Over time, multiple “control rooms” coalesced into one room of computer screens with fewer operators and yet an exponential increase in information to process. So how on earth can a person keep track of it all? Intervene promptly when things go wrong? Determine what needs attention right now vs something that can wait? As a problem space, the seemingly simply world of designing SCADA UI is quite fascinating.
Paracetamol/acetaminophen has a therapeutic dose that is uncomfortably close to the fatal dose, but is otherwise as safe as any drug can possibly be. So long as you don’t take too much.
Ibuprofen is also relatively safe, but it has a number of ways that it can do damage even at the therapeutic dose, if you are taking it all the time.
The main one is that it depletes your mucus lining in your stomach, which can lead to bleeding and death (used to be a big problem here in Aus when codeine combined pills were available without prescription). It’s also harder on your kidneys and liver.
Completely fine at therapeutic doses taken as per instructions and not mixed with alcohol. But having it every day is going to be much worse for you than the paracetamol and almost certainly lead to health problems.
To a point. Plenty of people from previous generations with missing digits and hands thanks to play with commonly available fireworks of the area (Australia based, so no idea how common that remains in the US).
My own experiments from my youth also one time resulted in some shrapnel punching through a 5 inch thick concrete tile very close to someone’s head (thought we were safe behind said tiles).
Get involved with the kids blowing stuff up so the danger is within reasonable bounds.
However, you need to remember that these simpler tools were a product of a much simpler set of requirements. Fixed themes, fixed screen size, fixed aspect ratios. I imagine a wysiwyg editor that gives you all the power of, say, CSS, and yet remains simple for simple things, sounds like a much more difficult task. I haven’t worked on UI in 20 years, so maybe such tools do exist.
This made me laugh so hard! I am gen x, and we used to say exactly the same thing about you spoiled, entitled, narcissistic, gritless millennials!
You should have seen what it was like when I first started! You should have seen what I was like!
You’ve got it all wrong! It’s not the generational differences that are the problem, it’s these darn young people are too darn young! (And some of them are a completely useless waste of space, as I was until life slapped a bit of sense into me). It’s a bit over the top, but I really love Musashi (novel) for this representation of the worthless youth who needs to be tied to a tree and suffering to the point of death before finally breaking and getting his crap together (become a human being; not just an animal). Feels like an (exaggerated) representation of the genuine journey all young men must make.
Basically, if what you are tinkering needs precise control over the bits and bytes, Zig (or C) are designed for it.
In the real world we are looking at things like RPO (recovery point objective) and RTO (recovery time objective). You need to consider HA and DR. It’s in these areas where SQLite does not scale.
That’s why I struggle to see the fit for SQLite in any sort of multi-user server environment. If you need the data to be durable, then the bigger DB’s have the tools. If you don’t need the data to be durable, just keep it in memory. I’m sure there are niches I am missing.
If you have 200 WF’s/sec each with 200 events, it sounds to me that you have a sizeable amount of work flowing through this system. 17 million workflows per day? Can I call these transactions?
Do these transactions add value to your business? Do you need durable execution for all these workloads?
Temporal is just a tool; and like any tool it can be misused. For the classic “book a hotel + airline, handle the partial failures” case, 17 million bookings a day would imply you should be thrilled with Temporal.
If you are using it to perform WAF in a firewall; you would be less thrilled. The scale you are describing, and that you aren’t super excited about the incredible amount of money pouring in, makes me question if the use-cases are fitting the tool.
Where are the “millions” on infra going? It’s a handful of services and a Postgres?
> Their sales team is also absolutely appalling and desperate.
You said “on-prem”. It’s open source; why are you dealing with their sales team?
> If you're doing anything non-trivial (say, 200+ events/workflow) and you need to run only a couple hundred of them concurrently all day…
If “millions” were required to obtain such tiny scale, I’d agree there’d be a massive problem. No one would use Temporal; it would be a complete waste of resource. If this were true.
The same is true of SQL query planners. You can perform basic queries without understanding how your SQL engine of choice works under the hood, but if you want performance, you must understand how your DB works. SQL is just the interface.
This is different in kind from imperative programming languages (which are much closer in abstraction to the underlying machine architecture), but we rub along with SQL ok; why not Prolog?
Great. Now we are going to get “secure cables” for mouse and keyboard and bluetooth device attestation.
The old adage that the people elect the governance they deserve; comes to mind. The concepts of Virtue, Honour, Duty, and Justice have been declining in the West over a very long period (this is not a US specific thing). The rotting head reflects the rotting society.
> It's a sucker's game to aspire to selflessly serve the greater good when the most powerful people in the land are brazenly corrupt
You don’t act honourably because that will “get you ahead”. You act honourably because it is right.
1. Install a culture of honour/virtue/accountability. Rely on duty and moral justice to keep the majority in-line.
2. An arms race to prevent ever more sophisticated methods of cheating, and the reduction in human dignity this implies. (E.g. the proctor must follow you into the toilet).
We all want the systems to be fair and just; but we also all want to be treated with dignity. No easy answers.
Edit: Because an RCE in a open-source dependency means you are just as vulnerable when the security patch lands? I don’t see the controversy.
It naturally trains your memory as you use it. Definitely a language of choice for getting into array languages in my opinion.
Well, there’s your problem. Get back to making the hotdogs!
Kerberos, OAuth, Basic Auth (username/password), PKI. MCP can be a wrapper (like any middleware).
> But that's not the point. The agent calls CLI tools, which reads secrets from somewhere where the agent cannot even access. How can agent leak the keys it does not have access to?
If the cli can access the secrets, the agent can just reverse it and get the secret itself.
> You ARE running your agents in containers, right?
Do you inject your keys into the container?
What about auth? Authn and authz. Agent should be you always? If not, every API supports keys? If so, no fears about context poisoned agents leaking those keys?
One thing an MCP (server) gives you is a middleware layer to control agent access. Whether you need that is use-case dependent.
The mitigation is to keep what it can do to “just the things I want it to do” (e.g. branch protection and the like, whitelisted domains/paths). And to keep all the credentials off its box and inject them inline as needed via a proxy/gateway.
I mean, that’s already something you can do for humans also.
Look at the political system of Switzerland and you will see a radically different setup.
And I think that’s the horse. The rest is cart. Yes they are rich but why? Yes they are relatively stable socially but why? Decentralised Canton government structure + direct democracy (referendums all the time for things that matter). That, I think, is why all the rest.
This story is more interesting, in my opinion, in how quickly things devolved and also how unwilling the more senior layers of the org were to address it. At a whole company level, the rot really sets in when you start to lose the key people that built and know the system. That seems to be what’s happening here, and it does not bode well for MS in the medium term.