11–20 of 36 posts
It would be very hard not to die in a traffic accident while debugging in this way.
Welcome to hell, developer!
I found this really hard to read due to the Claude-isms. "Classic" chicken and egg problem? 39 em-dashes, random numbered lists, etc. If you're not going to even bother to take the time to write an article, why should I waste my time reading it?
I can't help imagining someone trying to debug this rigging their laptop to their bicycle handlebars, connecting to the ride computer and then going for a ride to get live data for the debug session. It would be very hard not to die in a traffic accident while debugging in this way. Welcome to hell, developer!
It’s frustrating that this isn’t completely typical. As the writeup pointed out, this “exploit” can only be performed by the device owner anyway, so nobody is harmed by the unlockability. But 95% of devices that are sold, besides non-Mac PCs, and SBCs, are locked down completely, prohibiting anyone from using the device as they like.
I imagine the companies making the devices think they are “protecting” their secrets from competitors, though now it might be easier to ask an LLM for whatever feature they want to copy.
I found this really hard to read due to the Claude-isms. "Classic" chicken and egg problem? 39 em-dashes, random numbered lists, etc. If you're not going to even bother to take the time to write an article, why should I waste my time reading it?
(I liked the article, personally.)
I can't help imagining someone trying to debug this rigging their laptop to their bicycle handlebars, connecting to the ride computer and then going for a ride to get live data for the debug session. It would be very hard not to die in a traffic accident while debugging in this way. Welcome to hell, developer!
I’m a Garmin user and it blows my mind that the interface was chosen. Buttons and touch screen and confusion.
Not helped by both Garmin and Strava not putting enough arrows on the path of travel on their maps.
If you have a route the uses the same road in both directions (eg you ride to somewhere then back along the same path) it isn’t possible to tell when to turn off. Why can’t there be arrows indicating direction of travel?
And that’s when it’s working. Garmin seem to break shit on software updates and then sync stops working, the radar disconnects, it won’t lock on a satellite etc.
Can Apple make a bike computer please? Or at least play nice and sync their watch with Garmin properly?
I found this really hard to read due to the Claude-isms. "Classic" chicken and egg problem? 39 em-dashes, random numbered lists, etc. If you're not going to even bother to take the time to write an article, why should I waste my time reading it?