If you’re just simulating the temperature there’s pretty much just three options:

• The thermostat will simply command the HVAC system to maximum cooling, just like with any temperature well above the setpoint.
• The thermostat will treat that value as a faulty sensor, report “error faulty sensor”, and not do much in particular.
• The thermostat will crash due to an overflow of some sort as its software was never tested with inputs like that.

Personally, I’d go with, “error faulty sensor” as the most likely outcome.

(Edit: you can stimulate the temperature by setting your house on fire. Better to just simulate it)

This is entirely the wrong community for this answer, but I’ve used the pro version of Textra for 10 years now. One time payment (10 years ago), updates every few months, lots of features, but they don’t get in your way if you don’t need them.

The main feature I use is “delay send for 5 seconds” to allow me to catch all my spelling and grammatical errors after I hit send , but the rest of the UI is pretty well thought out.

One of the very few commercial Android apps that I’d recommend to someone.

Fossify Messages is your trusted messaging companion

I hate this kind of advertising language.

Don’t sell this as some fait accompli , done deal thing. It’s not anything to me at the moment. It doesn’t need to be my “messaging companion”. It needs to be a program, that I use to send and receive SMS/MMS messages. That’s it.

And “trusted”? I’ll be the judge of that.

It straight made up a powershell module, and method call. Completely made up, non existent.

Counterpoint 1:

I gave Copilot a couple of XML files that described a map and a route, and told it to make a program in C# that could create artificial maps and routes using those as a guideline.

After about 20 minutes of back and forth, mainly me describing what I wanted in the map (eg walls that were +/- 3m from the routes, points in the routes should be 1m apart, etc) it spat out a program that could successfully build xml files that worked in the real-world device that needed them.

Counterpoint 2: I gave Copilot a python program that I’d written about 8 years ago that connected to a Mikrotik router using its vendor specific API and compiled some data to push out to websocket clients that connected. I told it to make a C# equivalent that could be installed and run as a windows service, and it created something that worked on the very first pass using third party .NET libraries for Mikrotik API access.

Counterpoint 3: I had a SQL query in a PowerShell script that took some reporting data from a database and mangled it heavily to get shift-by-shift reports. Again I asked it to take the query and business logic from the script and create a command line C# application that could populate a new table with the shift report data. It created something that worked immediately and fixed a corner case in the query that was causing me some grumbles as well.

These were things that I’ve done in the past month. Each one would have taken a week for me to do myself, and with some general discussion with this particular LLM each one took about an hour instead, with it giving me a complete zipped up project folder with multiple source files that I could just open in Visual Studio and press “build” to get what I want.

In all these cases however, I was well versed in the area it was working in, and I knew how to phrase things precisely enough that it could generate something useful. It did try and tack on a lot of not-particularly-useful things, particularly options for the command line reporting program.

And I HATE the oh-so-agreeable tone it takes with everything. I’m not “absolutely right” when I correct it or steer it along a different path. I don’t really want all this extra stuff that it’s so happy to tack on, “it won’t take a minute”.

I want the LLM to tell me that’s an awful idea, or that it can’t do it. A constant yes-man agreeing with everything I say doesn’t help me get shit done.

It’s really more about the overall flavor of the spreadsheet than how “right” any individual field is.

Just like the Xerox copier/scanners that helpfully kept scanned images small by reusing parts of the image elsewhere. Like, all these 6s on your scanned invoices can totally be replaced with 8s. There’s just a tiny degradation in the overall image, it shouldn’t be a problem!

Xerox should have just called it AI compression and people would have been throwing money at them.

Some 3:1 glue lined heat shrink on the backs of each connector might do the job.

The glue melts during heating and with a 3:1 ratio you get quite a bit of glue forced in around the wires as it shrinks. It then sets pretty robustly once you get down towards room temperature.

You could try shrinking maybe some 6 or 10mm heatshrink over approx 25-50mm either side of the connector (with a bit of overlap on the connector) and see how it goes. Fully shrunk it’s pretty chunky but it won’t be any bigger than the connector.

Dear article writers:

PLEASE STOP ANTHROPOMORPHISING CORPORATE ENTITIES.

They can’t feel terror, or anger, or ‘slam’ some other corporate opponent.

As an entity, they can make decisions and take actions. Assigning them emotional range gives too much credibility to soulless money making machines whose sole purpose is to create value for their investors.

But how can all the techbros say that AI is the future and everyone is using it if they don’t forcefully cram it down everyone’s throats at every opportunity?

And somehow this Futurama line feels painfully close to the truth:

Leela: Didn’t you have ads AI in the 20th century?

Fry: Well, sure, but not in our dreams. Only on TV and radio, and in magazines, and movies, and at ball games, and on buses, and milk cartons, and T-shirts, and bananas, and written on the sky… But not in dreams.

• Algorithm shows a preview of a chaotic scene where the content isn’t easily identified.
• You open / interact / linger on it to figure out what is happening before identifying it as something you don’t want to look at.
• Algorithm detects increased interaction and happily serves up more.

I play a little game with Instagram sometimes. I click on one (1) thirst trap bikini girl post in the search reel. Then I see how many times I have to press the little 3 dot menu and pick “not interested” on allllll the other thirst trap bikini girl posts that immediately appear.

I generally have to press “not interested” about 15 times before my feed reverts to only having bikini girl thirst traps once every 20 or so posts.

English readily absorbs both the best and worst of all the other languages. If some other language has a word that really hits the mood of even just a small amount of English speakers - bam! - it’s English now, motherfucker!

Add to this, it’s chock-full of complicated and often hidden rules that can - or absolutely cannot - be broken, depending on context. No wonder people learning it as a second language have that permanently confused look on their face.

The thing about the English language is that you can verb any noun you like and get away with it. Just like I did in the previous sentence.

There’s a nice 6502 assembly intro + Sim here :

https://skilldrick.github.io/easy6502/

Added edit: I mean, it’s not PET-specific, but it’s cool to have a little sim with a little chunk of display memory to play with.

Also you’ll quickly find that assembly is extremely verbose. Learn how to load registers and jump to (and return from) subroutines as quick as you can to prevent endless amounts of repetitive assembly.

You missed a thorn in your reply there in your first paragraph.

And as an aside, sprinkling them throughout your reply heavily reduces the impact of your message. It’s a decoding stumble for most English readers who look at word shapes when parsing sentences.

So while it might be your thang - or perhaps you’re Icelandic and they’re just leaking through - it’s probably better to stick with th if you want to get your point across.

Cs-137 is used in industrial density gauges. You want to measure the density of a liquid in a pipe? A radioactive source on one side, a detector on the other, easy-peasy.

Now how the fuck a controlled substance escapes from its highly encapsulated and supposedly-well-tested-and-regularly-inspected compartment and gets into your food, well that’s something else to ponder.

If you want to recharge a full 300-mile Li-Ion battery in 5 minutes, you need to supply 1200 kW (1.2 MW) of power.

Which is why cloning the traditional centralised ICE refuelling station concept doesn’t work with EVs.

The United States struggles with 4.8 kW home chargers and 150 kW superchargers.

With an average daily usage of 20kWh for a 60 mile commute in a mix of stop and go and highway traffic, a 4.8 kW charger can top off your EV battery at home in 4 hours. A 2kW charger can do it in 10 hours.

That’s the mindset that needs to change. You shouldn’t have to visit an external charging station every few days to cram another 100kWh of power into your battery. You put a charge into your battery at home every night. It’s fully charged again every morning for your commute. The mega charging stations are then only used for long distance travel.

So, just like we built ICE refuelling stations dotted all over the place, we need to put in the infrastructure for localised EV charging at homes. Colder climates have the advantage already, as parking lots are already full of engine block heater connections and in a lot of euro countries they’re used for EV charging. It can be done, it’s just a change.

Have a look at EasyEDA. Browser UI, schematic and PCB design, linked to JLCPCB for ridiculously easy board creation, and if you take care to use components they have in stock out of their design libraries you can also do fully populated boards ready to go.

Here’s a post I made about a solar hot water system controller using easyEDA with a few images of the board and schematic at the bottom.

I was talking more about unwrap causing a panic rather than calling the actual panic macro directly. Rust forces the programmer to deal with bad or ambiguous results, and what that is exactly is entirely decided by the function you are calling. If a function decides to return None when (system timer mod 2 == 0), then you’d better check for None in your code. Edit: otherwise your code is ending now with a panic, as opposed to your code merrily trotting down the path of undefined behaviour and a segfault or similar later on.

Once you get to a point where we are doing the actual panic, well, that is starting to just be semantics.

causing the program to crash if it actually was an error, restoring the more unsafe behavior of other languages.

Wellllll it’s more of an abrupt exit rather than a crash, which is still better than eg. silently accessing beyond the end of an array, or ending up with a pointer to nowhere when you thought you had a sane memory reference.

wut

Seconded.

I test drove the Kona and Ionic models in Australia a couple of months ago. I also drive numerous different hire cars for work and I can say Hyundai has the most intrusive driver alert system out of the lot of them.

Constant and loud pings and bings from the safety system. Infotainment on the Kona was also very slow to respond.

Yes, I am doing 103km/hr in a 100 zone, thank you, Hyundai.

Yes, I am again doing 103km/hr after briefly dipping to 98km/hr thank you, Hyundai.

Yes, I am nearly on the edge of the lane, mainly because a large semi is coming towards me in the opposite direction and they’re looking a little loosey-goosey on this two-way highway, thank you Hyundai.

Yes, I am looking at the dash wondering what is causing the noises instead of watching the road, thank you, Hyundai.

Yes, I am now actively poking around in the menus trying to turn this shit off instead of keeping my eyes on the road, thank you, Hyundai.

After those test drives, I bought a Volvo instead. It has very low key warnings (or a buzz from the steering wheel like a mild ripple strip if it thinks you are leaving your lane). Just like Hyundai , you can’t permanently turn the speed limit warnings off, but you can adjust them to be up to 20km/hr above or below the speed limit.