Unfortunately, sometimes over a 45 minute freeway commute, dropping back repeatedly means arriving 15 minutes or more later. Again, no big deal now, but it was somehow unacceptable when I was younger.
Unfortunately, sometimes over a 45 minute freeway commute, dropping back repeatedly means arriving 15 minutes or more later. Again, no big deal now, but it was somehow unacceptable when I was younger.
I was a bad driver. It would frequently beep at me to let me know that I had braked too hard. I was mystified. "What should I have done differently," I'd think, as I raged at the objective machine that judged me so.
The next time my brother came to visit, he called mom. "Oh, and presidentender is a good driver now." I didn't put the pieces together right away, but it turned out that the dongle had actually trained me, like a dog's shock collar.
The reason for my too-frequent hard-braking events wasn't speed, although that would be a contributing factor. It was a lack of appropriate following distance. Because I'd follow the drivers in front of me too closely I'd have to brake hard if they did... Or if they drive normally and happened to have a turn coming up.
Over the period I had the insurance spy box in my truck I learned without thinking about it to increase my following distance, which meant that riding with me as a passenger was more comfortable and it beeped less often. Of course since I'd been so naughty early during the evaluation they didn't decrease my rates, but I think the training probably did make me statistically less likely to crash.
Incredibly frustrating, and I've driven all over North America - there's practically no major city where this doesn't happen. If you're not maintaining a safe following distance on city/residential streets, that's a different matter.
The people that could make terminal stuff super fast at low level are retired on an island, dead, or don't have the other specialties required by companies like this, and users don't care as much about 16.7ms on a terminal when the thing is building their app 10x faster so the trade off is obvious.
I think the Internet made 'waiting' for a response completely normalized for many applications. Before then, users flew through screens using muscle memory. Now, when I see how much mouse clicking goes on at service counters, I always think back to those ultra-fast response time standards. I still see a few AS/400 or mainframe terminal windows running 'in the wild' and wonder what new employees think about those systems.
When I don't know what I want to do, I read existing code, think about it, and figure it out. Sometimes I'll sketch out ideas by writing code, then when I have something I like I'll get Claude to take my sketch as an example and having it go forward.
The big mistake I see people make is not knowing when to quit. Even with Opus 4.5 it still does weird things, and I've seen people end up arguing with Claude or trying to prompt engineer their way out of things when it would have been maybe 30 seconds of work to fix things manually. It's like people at shopping malls who spend 15 minutes driving in the parking lot to find a spot close to the door when they could have parked in the first spot they saw and walked to the door in less than a minute.
And as always, every line of code was written by me even if it wasn't written by me. I'm responsible for it, so I review all of it. If I wouldn't have written it on my own without AI assistance I don't commit it.
This is sage advice. I spent the better part of a day trying to steer Gemini into correcting an inconsistency when I likely could have solved it in under an hour. I think persevering with Gemini was due to a number of factors, including novelty, stubbornness, and (unfortunately) not knowing in detail what Gemini had written up to that point.
I eventually studied the resulting code, which ended up having a number of nested 'hacks' and required refactoring - more time wasted, but still much faster overall.
https://www.amazon.com/Breath-New-Science-Lost-Art/dp/B082FP...
Some people who are alone (including my father) have no idea that they have sleep apnea or 'odd' breathing - for apnea, they're obviously asleep, and for other breathing factors, it's usually a slow and unnoticeable progression.
More interestingly, I'm also able to pick out people who have early signs of "decreased health" based on their breathing pattern at rest - I don't think it's overly difficult.
This study appears to cover both aspects - creating a breathing fingerprint and estimating BMI. I certainly wasn't aware of breathing differences associated with cognitive state. Bravo to the researchers for formalizing all of this - hope some positive interventional techniques are driven by these findings.
[0] https://news.ycombinator.com/item?id=37981314 [1] https://airandspace.si.edu/collection-objects/microscope-ast...
Indeed, when someone changes lanes in front of me, I gently let off the accelerator, but as someone else noticed, that can enrage drivers behind me (I don't take it personally), and I'm definitely traveling fast enough to remain in the middle lanes.