Due to the nuances of my vehicle, the built-in hands-on-wheel nag was still active and required (small) driver wheel inputs every 10 seconds to prevent the beeps. Just keeping both hands on the wheel was enough to pacify the nag. But this forced me to keep attention on the vehicle, more than OpenPilot's face direction detector. Anecdotally I am certain this kept me more engaged than if I could have gone hands off.

The net effect was I had more capacity to be aware of what was going on around me on the road, AND I didn't feel nearly as fatigued at the end of the drive. Keeping the car between the lines consumes a little bit of cognitive energy constantly, which compounds over a long drive. Freeing up that load allowed me to pay more attention to what was happening on the rest of the road. And the mental burden was still half as much--I felt like I had driven maybe 4-5 hours instead of 9.

I have some ideas for how I might disable the built-in nag, but I'm pretty sure doing so would make my car less safe. The current configuration might already achieve the safety maximum for ADAS based on front-facing cameras only.

It increases situational awareness while reducing fatigue, and I think that anything further I try to do will adversely affect one or both of those effects.

On the Renegade, the adaptive cruise control activation and control signals are on a separate bus from the steering control signals, and the ACC signals don’t get up to the lane assist camera at all. OpenPilot support on this vehicle will require tapping CAN buses in two spots on the vehicle, and this is not a Comma-supported configuration. They want to be able to make a single interposer cable that plugs in between the lane assist camera and your car, and if that’s not possible they will never support your vehicle.

To attempt to support my car I am working on a gateway device that will bridge information from the powertrain bus to the fusion bus so it will be available at the camera (which is on the fusion bus and the chassis bus). But this implementation, which may not actually work but even if it does, will never be accepted upstream. And safety-wise, that’s probably the right choice for the project.

The sad part is I think the only signal that I need that I don’t have at the camera right now to make a safe implementation is ACC engagement. I’ve scrutinized every bit of every message on the chassis and fusion buses available at the camera and there is simply no signal that indicates if ACC is engaged.

One bit is all I need to get lateral control working. Well, assuming that once I start injecting control signals there aren’t other issues, that is. And that is not probably a safe assumption.

Direct link: https://chatgpt.com/codex/cloud/security

By giving the agent its own isolated computer, I don’t have to care about how the project gets started and stored, I just say “I want ____” and ____ shows up. It’s not that it can do stuff that I can’t. It’s that it can do stuff that I would like but just couldn’t be bothered with.

A restart fixed all of the problems including the hanging Cowork tab.

Deleting vm_bundles lets me open Claude Desktop and switch tabs. Then it hangs again, I delete vm_bundles again, and open it again. This time it opens on the Chat tab and I know not to click the Cowork tab...

The people who lose their jobs prove this was always the case. No job comes with a guarantee, even ones that say or imply they do. Folks who believe their job is guaranteed to be there tomorrow are deceiving themselves.

Looks like that would do the one thing I need, and I’m finding the grass to be just as brown with Razer Synapse is it is with LogiOptions.

I enjoyed my trip to Micro Center today to finally ditch Logitech after those buttons stopped working. Put up with Options for over a decade because at least it did the one thing I needed.

Comments URL: https://news.ycombinator.com/item?id=46454950

Points: 2

# Comments: 1

I’ve seen the pursuit of disambiguation employed to deadlock a project. Sometimes that’s the right thing to do—the project sponsor doesn’t know what they want. But many times the senior needs to document some assumptions and ship something rather than frustrating the calendars of 15 people trying to nail down some exact spec. Knowing whether to step on the brake or the gas for the benefit of the team and company is a key senior trait.

This is a yes, and to the article; building without understanding the problem usually will increase chaos—though sometimes the least effort way through it is to build a prototype, and a senior would know when to do that and how to scope it.