nhtsamera

Yeah, it's actually one of the last sentences in the New Testament - Revelations 22:18.

Jesus did his best to tone down the fire and brimstone, but the Abrahamic god is not a particularly forgiving one.

When it comes to producing things, there's a whole world out there. You aren't competing with your neighbor, and materials/labor are vastly cheaper in other parts of the globe.

Before you suggest boycotting the rest of the world, protectionism rarely works over the long term because it tends to stifle innovation and provoke trade wars. The US is already courting this with its recent green energy legislation which aims to promote domestic industries in a way that inconveniences Western Europe, for example.

Another big challenge is the punishment for getting it wrong, which the article doesn't even mention.

>For I testify unto every man that heareth the words of the prophecy of this book, If any man shall add unto these things, God shall add unto him the plagues that are written in this book: And if any man shall take away from the words of the book of this prophecy, God shall take away his part out of the book of life, and out of the holy city, and from the things which are written in this book.

Personally, I wish more people would include curse clauses in important documents. Legal contracts, government constitutions...why not tack on a few lines threatening a dire curse for any party who reneges on their responsibilities?

Rail travel is one of the last places that you still see this in the US.

I took a cross-country Amtrak trip right before the pandemic, and most of the conductor's announcements were just to tell us when the next smoke break would be.

When the train got stuck waiting for cross traffic at a freight yard in rural North Dakota, an incipient passenger mutiny forced them to break the rules and let everyone pop out for some light trespassing and nicotine consumption.

It felt strange in a similar, but opposite way to what you're describing.

It seems pretty popular in big software-centric companies like the FAANGs. IME the turnover is usually every couple of months, as the sacrificial lamb gets tired of it and other team members start to feel like it might be time to take a turn in the bilges.

I can understand why the idea of hiring someone to handle that role would be appealing, but it really isn't a full-time job.

Plus, the last thing that BigCo engineering teams need is more politics; they have more than enough of that between the overlapping layers of engineering, project, and product managers.

And to think, Office Space came out 24 years ago. Funny how things come full-circle.

>And here's something else, Bob: I have eight different bosses right now.

>I beg your pardon?

>Eight bosses.

>Eight?

>Eight, Bob. So that means that when I make a mistake, I have eight different people coming by to tell me about it. That's my only real motivation, is not to be hassled. That, and the fear of losing my job. But you know, Bob, that will only make someone work just hard enough not to get fired.

Cue some discussion about kids these days and "quiet quitting".

That would be unusual, so you could probably report them for being a bot.

After all, Meta's TOS stipulates that you must provide accurate information about yourself, and that you cannot share anything that is misleading.

It also prohibits making groundless reports or appeals, so maybe you could take an eye for an eye it you get unfairly targeted.

Ex post facto, as usual.

What are the odds that this whole imbroglio happened because their third-party APIs broke and they can't figure out how to fix them?

It's static, until a contractor ignores the post-it note on their monitor that says, "IMPORTANT: ALWAYS add an extra newline BEFORE saving the file".

Once that happens, you have to hope that your backups work - why bother having disaster recovery drills for a static system?

Once you realize that your backups are hosed, you may experience a creeping suspicion that software is never truly static when human operators are involved.

Not particularly surprising to hear that HoloLens may have moved into the "oh well, dump it on Uncle Sam" phase of product development.

It's good to hear that the government is demanding fixes to the eyestrain/nausea/headache issues before they commit to deploying them at scale.

This is quite easy to do, but the results can be off in funny ways. For example, try putting this into SD with Euler a sampling and a cfg scale of 10:

"The Night Watch, a painting made by Rembrandt in 1642"

It generates a convincing low-res imitation about half the time, but it also has a tendency to make the triband flag into an American flag, or put an old ship in the background, or replace the dark city arch with a sunset...

If you keep refining the prompt, you can get closer, but at that point you're just describing what the painting should look like, rather than asking the model to recall an original work.