> On Monday 24th August at 8PM EST, we received at letter from X Corp. asking to cease and desist the service XCancel. The service XCancel is stopped until further notice. We are seeking legal advice and won't share more details for now. Thank you for the trust you have put in these two years of XCancel.

I was involved in a project that made such a twin for a warehouse. It was simpler in theory because there was no manufacturing process. Just moving objects from one place to another. It was still expensive and took a long time. We tracked traffic heatmap but also collected data on and modelled luminosity for safety. On top of that there was a standard warehouse space optimization.

You're going to run into similar problems as with testing and documenting code. Eventually something will change - a process, a machine, a sensor. You have to stay on top of things and update your model too. Otherwise they will drift apart and not be as useful.

4 out of 5 were marked as suspicious, mostly citing short punching sentences, negative parallelism, and content duplication.

If you don't have an MCP server the AI agent might try to figure out how to talk to the game using the above ideas. But at this point you might as well ask it to help you write one.

Could be fun - will the AI model get stuck on the same things I did? How does it overcome obstacles? Will it try to break the game to power through?

Ok but I have to (or rather - I am expected to) vote on those topics. And not just during the elections or referendums, but also figuratively with my wallet and attention. In other words, my actions will be driven by how (mis)informed I am.

And even though I am comfortable with being ignorant, from my experience other people aren't comfortable with me being ignorant. Saying "I don't know, I haven't thought about it" is often met with shock if not anger. I don't have the luxury of dropping those people from my life either.

As for the travel, the perspective of a tourist is different from a person who lives there even for a few months, much less a few years. I agree it beats reading third-party summaries, but I don't think it gives you a much better clarity.

> In general, when I talk to software folks about testing, I'm coming from such a different place that they immediately look at me like I'm an alien, so let's talk about how we tested at this hardware company I worked for, Centaur, which informs my biases about how I like to work. Some of the things that we did that were or are unorthodox in the software world are:

> Hired dedicated QA / test engineers, with testing being a first-class career path on par with being a developer - No code review by default - Virtually no hand-written tests - Constant testing via what programmers sometimes called property based testing, randomized testing, fuzzing, etc., although we just called those tests (hand-written tests were called "hand tests"). - Large regeression test suite (3 months wall clock to execute on compute farm) - No unit tests

Anybody here tried that (or a similar) approach? Especially going all-in on property based testing and fuzzing with no unit tests.

I tried that approach somewhere before and the initial results were promising, but ran into political issues so the idea was canned.

https://www.youtube.com/watch?v=PQWpYQm60P4

There were more of them, including some with other celebrities.

The context was that technology should evolve to fit the humans [not the other way around]. And if contemporary technology didn't have limitations, it would be correct.

But it did and humans had to adapt to the computers. Humans had to develop and learn special languages so they could communicate with computers to do all those useful things you mentioned. Why? They were limited in understanding (or parsing) human languages. It took us decades before we could talk to computers in human languages. We're getting pretty close - especially in the past few years - but there's still some friction.

We communicate with other humans using voice and three dimensional hand gestures. To use computers and early phones we had to learn to operate new input devices: keyboards and mice. Later with touchscreens we moved to two dimensional hand (finger) gestures. We're barely making voice commands work with our devices just recently.

Then, a large number of humans are figuratively tethered to their desks because the devices need power and stable internet connection. Mobile devices break this relationship a bit but you still need to charge them and be close to some sort of access point. In any case, the devices encourage sitting in one place for hours at time.

And this is just computers and smartphones. Humans adapted their entire lifestyles and transformed the landscape to cater to cars.

That aside, this is a good script you're running. Thanks.

> By default, Black uses existing trailing commas as an indication that short lines should be left separate, as described in the style documentation. If this option is given, the magic trailing comma is ignored.

https://black.readthedocs.io/en/stable/usage_and_configurati...

It should then keep the lines intact, unless they exceed the line length. I have mine set to 120.