I disagree, the only real issue with UBI is the amount of inflation it will cause. Germany has something nearly approaching UBI and they are doing fine.

Would Germany's UBI work if there were no jobs at all?

Nobody knows, because we have never before had no jobs for any reason, let alone specifically due to all labour being fully automated.

Would Syncthing fulfill your requirements?

I think it might! Definitely checks enough boxes for me to try out, anyway.

The UI is a little cumbersome for me, personally, but it does seem at least straightforward enough for me to understand what the intentions are.

ETA: Welp, that didn't last long. A service running in the background that exposes an "insecure" url for a browser to then open as the only means for GUI interaction with the app is not a great recommendation for everyday users. It looks like it has all the features, but I'm looking for a user experience. CLIs provide the features. I'd like an app, not a service running a webserver. Shudder the thought of just shoving the front end in an electron app, but even that would be better than this for casual users.

You could create an app that has a tray status icon, that launches a tauri app connected to the same web service (assuming it's only listening on localhost, it's fine).

I think it's a good comment, given that the best agents seem to hallucinate something like 10% on a simple task and more than 70% on complex ones.

Probably something blue collar like electrician, plumbing or auto repair.

I became a union electrician specifically to get away from tech and then found myself spending most of my apprenticeship wiring data centers.

Can't seem to escape from the tech gods.

Unfortunately blue collar labor takes its toll on bodies — probably best-left to hobby grunt work (and not full-time) unless you like back/knee/hip pain =D

I'm currently attempting to transition back into white collar tech (early 40s) but we all know how that's going (in this economy). Fortunately twisting wires together for decades has allowed me to stack enough savings that I'm not in a rush / desperate for re-training/employment.

Nah it's very apt and perfectly encapsulates output that looks plausible but is in fact factually incorrect or made up.

Also just peacocking, being that skid on the forums that took down PlayStation on Christmas will get you cred.

It's funny to think that the C-suite would ever give up their massive compensation packages.

They arent a monolith. They would gladly sacrifice n number of c-suites they dont know, if it increased their networth by 1%.

> My leadership is currently promoting "better to ask forgiveness", or put another way: "a bias towards action"

lol, that works well until a big issue occurs in production

But then it also works. Managers can scapegoat engineer who is asking for forgiveness.

It's a total win for the management: they take credits if initiative is successful but blame someone else for failure.

Which brings it full circle to engineers saying no to product releases after being burned too harshly by being scapegoated

That assume big issue don't occur in production otherwise, with everything having gone through 5 layer of approvals.

In that case at least 6 people are responsible so nobody is.

Many companies will roll out to slices of production and monitor error rates. It is part of SRE and I would eat my hat if that wasn't the case here.

The big events that shatter everything to smithereens aren't that common or really dangerous: most of the time you can lose something, revert and move on from such an event.

The real unmitigated danger of unchecked push to production is the velocity with which this generates technical debt. Shipping something implicitly promises the user that that feature will live on for some time, and that removal will be gradual and may require substitute or compensation. So, if you keep shipping half-baked product over and over, you'll be drowning in features that you wish you never shipped, and your support team will be overloaded, and, eventually, the product will become such a mess that developing it further will become too expensive or just too difficult, and then you'll have to spend a lot of money and time doing it all over... and it's also possible you won't have that much money and time.

Yes, I was SRE at Google (Ads) for several years and that influences my work today. SRE was the first time I was on an ops team that actually was completely empowered to push back against intrusive external changes.

I suppose that's a consequence of having to A/B test everything in order to develop a product

Have we learned nothing from Cambridge Analytica?

We learned not to publish as much information about contracts and to have huge networks of third party data sharing so that any actually concerning ones get buried in noise.

Also, if you're trying to run lean and cheap you can go very far with just a simple VPS like Hetzner.

As a start there should be common-sense gun control, like, if you get any kind of mental illness or violence on your record you lose your guns. Secondly, if a kid does get access to your gun in any circumstances you should also be charged with manslaughter.

Then you perform the mental health evaluation before you are allowed to even own a gun in the first place. Along with regular evaluations thereafter to continue to be legally qualified to own a gun.