The incredible improvements have only been over the last 9 months or so. Business, especially disrupting entire job functions, takes much longer than that. As is typical with this type of change, it'll be slow until a tipping point, then FOMO will hit.
If I were to count the number of times you all have said "incredible improvements" here on this site over the last 7 years, what number do you think I'd come up with, and would that change your tune? I'll do it, if I must, to show you all how un-serious is this claim.
If anything the expectation of incredible improvements just over the horizon makes an argument for not adopting AI or at least doing so very judiciously.
Why would you spend dollars on tokens today if you expect the same tokens will get you something vastly superior in a few months, or that they'll do the same job for nickels on the dollar? Do you just hate having money or what is the problem?
Weird, AI enjoyers have been calling the game for years. We're already supposed to have achieved AGI and already be in the midst of the technological singularity. The tipping point was when AI solved the Navier-Stokes problem. All human created art, media and software development has been declared dead a dozen times over.
Firearms are capable of being used for legal purposes, as they are in the overwhelming number of cases. A radio that transmits on a restricted frequency is illegal. The ruling doesn't say legal frequency transmitters can't be sold, just that the broker (ebay) is responsible for ensuring it's not facilitating the sale of illegal radio equipment. Ebay is the one choosing not to sell most radio equipment (even if legal), because they don't want to deal with it.
Firearms used to be widely available at big-box stores, as they were legal (and still are), provided the store prevented illegal purchases. Most box stores/locations no longer sell firearms, because they don't want to deal with it.
I do the same with Home Assistant and my many EspHome devices. HA works well, and it has a lot of nice features and extensive community-built integrations, but configuring and laying out the UI is a disaster. You can choose between WYSIWYG UI tools that are limited and cumbersome, or you can deal with raw YAML that stretches far beyond what YAML should be used for with deep nesting, and it's poorly documented to boot. It feels like a proprietary workflow engine, where you'd rather just write it in a real programming language.
Agents cut through all that crap and allow me to make changes without learning a new overwrought configuration language that thrashes syntax every few months. The fact that it is open and fully modifiable redeems it, because I can ignore all the annoying parts while achieving what all that was envisioned to allow.
Don't forget (at least in the US), artificial scarcity intentionally created by licensure requirements and/or unions. If I wanted to be an electrician tomorrow, even given my experience and knowledge of the subject, I'd still need 8,000 hours of apprenticeship and other verified instruction/classes. Finding someone to apprentice under, being paid slave wages, tends to be the biggest blocker.
You're probably not counting all the overhead, particularly from heavy equipment. Skidsteers, dump trailers, stump grinders, as well as all the oversized/towing capable trucks to haul those machines around. All of that equipment needs maintenance and fuel, as well.
The expensive part is usually just showing up ready to work, with a marginal cost for each additional tree. If you had 15 trees taken down in one day, the cost per tree would work out to seem much more reasonable.
My neighbors were having a bunch of tree work done, and I asked the supervisor what it would cost to take a big dead one down on my property. I planned to do it myself, so I had a strong haggling position, and I got him to $400, which felt worth it to save me a day's worth of hard labor. If they weren't already onsite with all the gear, that would've been $2K+ easy.
I thought for sure this was going to talk about the non-scientific IARC classifications. Even group 1, the doozies, doesn't consider dose or actual risk, leading to ludicrous adjacency like processed meats and asbestos. Scientists that aren't politically motivated wouldn't classify things on a list with terms like 'probably' or 'possibly'.
DBFs tend to be the easy part, in my experience in a similar company (not as much revenue.) The spec is simple enough that one can write a reader/writer in an afternoon, even before AI.
My biggest challenge is the speed at which calculation heavy business logic can operate in FP, even on network shares, as long as they're optimized for IOPs not bandwidth. Trying to adapt similar data access patterns to a networked RDBMS will kill you with round trip and connection overhead. Converting that logic to set-based operations or stored procedures means altering logic and all the risks that entails.
I'll add that it's my favorite podcast to listen to while falling asleep - if you do that with podcasts. Sean uses high quality audio gear (and he ships/loans similar to his guests), so the audio is almost always top notch. He also must do what I would consider to be the bare minimum of editing to normalize volumes.
So many podcasts are unlistenable to me for bedtime, because of mismatched volume levels of host/guest or poor quality audio for the guest (through zoom or whatever). He also tends to speak in a smooth tone, with obvious inflection for emphasis (i.e. not monotone), but not irritatingly chipper or fake sounding like some other physics podcasters.
one of my biggest pet peeves is podcasts/youtube videos that would be perfect to listen to while resting, if not for some loud and obnoxious intro/outro music. Or a too-loud background muzak track. If I want muzak I'll go to the supermarket or stand in an elevator.
Is your unit one of the ubiquitous Midea rebadges? Or at least one where the remote does 'follow me' type periodic, remote temp reporting?
If so, you're right, the easiest way is to build/buy an IR blaster module for a microcontroller (ESP32 if you want wifi) and connect a temperature sensor. HA/EspHome is overkill for this, but can be useful for the large catalog of pre built integrations. Most of them are built using/on IR libraries for 'Arduino' anyway, so you can easily roll your own with a half dozen lines of C++.
Mapping out your own PID correction algorithm (esp says the room is 72 F when it's really 70 F to get it to cool sooner), but usually just having the remote room temp sensor near where you'd be sitting instead of near the ceiling or in the return air stream gets you close enough.
Thanks for this. Yeah, it has the follow me mode that sends temperature from the remote control every 3 minutes. I think it's a Senville from Home Depot. The remote control sensor only seems to read at 1 C resolution, so it seems like using the follow me mode with the stock remote is right out of the question.
My biggest worry is the heat from the microcontroller affecting the temperature on the temperature sensor. I want to use a Sensirion SHT45, it has 0.01 degree temperature resolution and is supposed to be accurate to 0.1 C. But I need to locate the temp sensor far enough away from the microcontroller to make the overall remote controller form factor awkward. I have a Raspberry Pi 4 that does the temperature data logging and web server, but that runs pretty hot.
I want to do this but I'm worried about stressing the compressor with extra start/stop cycles would shorten its lifespan. Maybe they are programmed to overshoot/undershoot the set temp to prolong lifespan?
Disclaimer: I know next to nothing about how ACs work beyond the very basics.
Yeah, you can cause it to short cycle for sure. But you can also get better control without excessive short cycling. If you're worried about short cycling, just include that in the control algorithm.
Short cycling would be bad in the sense that the motor frequently turns on. The maximum current is during motor start and the maximum motor coil cooling is when the fan is running at high speed steadily. So if it starts a lot and doesn't run much at high speed you might tend to overheat, sure. That would definitely drastically reduce the motor lifespan.
If you are still starting periodically and running for awhile, you can see where this goes.
I think it's not overshoot/undershoot that is happening so much as delayed kick on.
One of the biggest benefits of modern minisplits over conventional split systems (like are still common in America) is that their compressors are variable speed inverter types. This allows them to slowly ramp up to speed without the massive inrush of current.
That said, it's still a mechanical device that can experience stresses caused by cycles. Refrigerant systems also deal with gas/liquid phase changes and high pressures, so most units I've worked with do have a compressor lockout timer that allows a few minutes for temps/pressures to stabilize before kicking the compressor back on.
Not just storm water, but also things like maintenance of 'common areas', roads, and snow removal. Many small municipalities are budget strapped and don't want to be responsible for plowing/surfacing the new little 1/8 of a mile culdesac the developer created to build their 'neighborhood'.
In carving up the 5 acres the developer purchased, the 30 houses they squeezed in left some remainder that wasn't buildable or odd shaped, so this now becomes a lame 'park' or some other space that requires maintenance.
I read all my local municipal meeting minutes, and at least around here, permitting and ordinances control all the environmental/nuisance stuff, so I can't really explain why HOAs go beyond the collective expenses into the draconian rules.
>so I can't really explain why HOAs go beyond the collective expenses into the draconian rules.
Grass is really good at filtering/absorbing/treating stormwater so you might have to force everyone to keep their lawns lawn because the way you've got the lots graded you need that little bit of extra because it lets you make your "shit parcel" where the basin will go a little smaller and squeeze one extra house into the development.
Beyond that I think what a lot of it comes down to is that local governments are invariably run by a lot of the same kinds of busybodies that HOAs attract and the way rules are written these days the "normal permitting process" exists only to let the useful idiots think that just about everything isn't discretionary. There's always some gotcha or twistable phrase so everything goes through a special permit or variance of some sort. That opens up all sorts of off the record dealing wherein the developer agrees to throw everything and the kitchen sink into the initial HOA rules and the Karens in government make sure those things are in there before deciding how to exercise their discretionary approval.
The incredible improvements have only been over the last 9 months or so. Business, especially disrupting entire job functions, takes much longer than that. As is typical with this type of change, it'll be slow until a tipping point, then FOMO will hit.
reply