Hey, they could connect the car 'driver attention camera' thing, the OBD car speed stuff, and the in-car GPS to the municipality, the insurance company, and your credit card or bank account.
That way, the minute you look away, go a little over the speed limit, or check your phone message, they just gouge some cash out of your bank account. After three of these, your insurance rate goes up. After the tenth time, your health insurance and employer will be notified.
Fun times! 🎉
Edit: every damn step of this is now available via APIs or Agentic MCPs. There is zero technical barrier for this happening. Sleep tight y'all.
If the student had a PPL, it's likely she was training with him (a commercial pilot) for her IL instrument license, the next step up from PPL. Means she was qualified to land in clear weather.
He wasn't putting her in physical peril. But it's still a terrible mental burden to put on someone else.
This is only my second batch. The first was sauerkraut, with green cabbage and carrots. In vinegar, with whole mustard, dill, black pepper, and coriander seeds. Fermented for 7 days. I researched no-sodium, no cooking recipes and combined a few. Turned out really well.
Trick was using Ball jam jars but with pressure release lids. Definitely trying daikon next time. Thanks!
Just started pickling. Experimenting with cucumber spears, small white onions, garlic cloves, and fresh dill. In vinegar (50/50 white and Apple) instead of salt brine.
Going to try letting it ferment a bit, sauerkraut-style, and see how it turns out. Really easy.
Early iPhones all had unique UDIDs that were SDK accessible. It wasn't long before it was used to connect location data to devices and devices with specific users. Apple's solution was to yank it away from developers and go with an identifier the users could rescind and reset (the ADID). It still let apps track people, but there was always the risk users would reset it and break the chain of data gathering.
The real solution is to limit access to the information as-needed. Like for maintenance, or warranty repairs. Everybody else can go pound sand. In the desktop/laptop world, a lot of hardware vendors just blithely let anyone access unique hardware IDs, which leads to the same privacy outcome.
Spent the day setting up a Windows 11 test device, including Chrome, WSL, and Docker Desktop. Every step of the way involved opt-outs, for privacy, tracking, and larded, unnecessary AI. The defaults were all set to benefit the vendors instead of the user.
It wasn't just Microsoft. Everyone else wanted their pound of flesh.
If you assume Level 5 autonomy exists, you don't really need ANY control surface inside the car. Those just become useless artifacts. Steering wheels, gear shifters, gas/brake pedals, turn-signals, or rear-view mirrors.
Really, even map apps. Those just convert to glorified ToDo apps, where you say where you need to be at what time and the AV figures out how to get you there. Showing your position on a map is just more of a curiosity, like the airplane in-flight scenes, giving you a rough sense of place and calmly reassuring you that you are on your way (instead of, say, plunging into the sea).
You don't really need car windows either. Could be replaced with screens that show idealized imagescapes to enhance the transportation experience, or a movie.
Not requiring brake pedals is just the first logical step, if you want to let a machine drive you.
For those who actually enjoy the driving experience, AVs are stupid wastes of effort and tech.
May want to consider setting up a private, on-prem system. That way, you can reliably enforce privacy/GDPR rules. You can also tweak the system to support local training, RAG, MCPs, etc.
This way, the costs can also be controlled. It's some capital investment in local hardware, plus reasonably fixed power/cooling/maintenaance ongoing expenses.
Another way is to use the major AI services for planning/brainstorming specific features, tell it not to implement or touch anything, but to generate a detailed plan for an implementer LLM. Review that plan manually, and when ready, feed it to your local system for implementation and debugging.
This doesn't work if the goal is one-shot vibe-coding. But it works really well for focused feature enhancements, test coverage, and bugfixing.
Hey, they could connect the car 'driver attention camera' thing, the OBD car speed stuff, and the in-car GPS to the municipality, the insurance company, and your credit card or bank account.
That way, the minute you look away, go a little over the speed limit, or check your phone message, they just gouge some cash out of your bank account. After three of these, your insurance rate goes up. After the tenth time, your health insurance and employer will be notified.
Fun times! 🎉
Edit: every damn step of this is now available via APIs or Agentic MCPs. There is zero technical barrier for this happening. Sleep tight y'all.