Thank you. Yeah I looked at a few, another one is air.dev. The problem is they are recreating the actualy coding pane. Switchboard runs terminal directly.
Video is from the official Mexican congress YouTube page. Body analysis is shown around 2h:52m into the video. Currently only in Spanish. There are translations floating around on Reddit, albeit, in overly sensationalized subreddits.
In short, McDonald's continues to use these frequently malfunctioning ice cream machines due to their long-standing exclusive partnership with Taylor. The cost of repairs fall on the local franchise owners, not McD Corp.
They require Taylor machines for product consistency. Same reason they sell Coca Cola (legend has it this was a handshake agreement made by Ray Kroc and still is) and a franchisee can't decide he's going to serve Pepsi.
No, they require everyone use THE SAME MACHINE for consistency. Nothing about that requires them to use an ancient machine that is constantly broken with an abysmal service contract.
McDonalds has Walmart level bargaining powers with vendors. The current setup, where a machine breaks and you have to call a specific technician for insane rates is not an accident. McDonalds could change that tomorrow if they felt like it. No business relationship at McDonald's scale will ever be tilted away from their benefit.
The ancient machines were more reliable. I worked at a McDonalds for about 5 years in the 1980s and cannot recall one day when the Taylor machines didn't work.
The old machines had higher training and labor costs though, and over thousands of stores this was an issue. Presumably the newer machines are overall less expensive, even accounting for the lost sales on days where they are offline, and the associated repair costs. They may also be necessary for the newer ice cream products. In my day we only had vanilla soft-serve (cones or sundaes) and shakes with three flavors.
McDonald's isn't in business to keep Taylor repair techs employed. If it was costing them more than the alternatives, they would make a change.
For those looking for a code - I found a valid code in 10 mins by looking up 'bsky-social-' on Twitter and refreshing the 'Latest' tab every few secs. Got to be quick and swift, but works.
I can't speak on older BlueLink cars (article is from 2017), but my 2021 Elantra has GSM built-in and the commands are sent/received through the web - no bluetooth at all.
I build this for a cron script that queries my car's odometer and then queries CarFax to log my cars price over time on YNAB[1], but it has many uses.
Been thinking - lately - to perhaps also use this package with Google Home, but haven't gotten around to it. Might come in handy fellow Hyundai owners.
Wrote this module after getting annoyed at having to constantly pass `Config` objects left and right in my personal projects. Not planning on using this in any production systems but though it would be fun to package and share it.
aconf is a module for in-memory configuration. Create your configuration by doing the following:
from aconf import make_config
make_config(hello="world")
And then in any file inside your project access the configuration:
from aconf import conf
print(conf().hello)
# >>> world
That's literally it. The configuration will live in memory for as long as the Python runtime exists, and can be accessed by any file/class/module that calls the `conf` or `config` function (more details on Github). The `make_config` function can take any Python type; objects, functions, etc. should have no issue being passed around.
[1] https://t3.codes
[2] https://www.conductor.build
[3] https://github.com/imbue-ai/sculptor
[4] https://www.omnara.com