I kept reading about how bad Android Auto was for years but we finally bought a more modern used car and I can't believe they would ship that experience to customers. I had a week where I just had to unpair and re-pair Everytime I got in the car.
I would love to read about why that stuff is the way it is from the engineers, hmm that might be a good spelunking. I really must be missing something that makes it harder than I think it really should be.
Maybe they prioritized it low, assigned it to a group of 3 devs, and it functioned the first time they demoed it to management, so it shipped. All other devs would’ve been working on their in-house software.
Not the guy you’re responding to but Quanta articles are invariably horribly written, horribly explained, and constantly do this thing whether they simultaneously are pretentious and over complicate things while also belabouring simple, elementary concepts. Essentially it’s the worst of every world.
Hah same exact setup one brick two ports and it charges everything even my laptop! I've been eyeing some of the ones with built in batteries, but I get a lot of mileage of one brick in the bag.
The steam deck forced me to finally pay attention to the usb-c ecosystem and I can only imagine how some non tech people might get with mysteriously bad or slow charging.
I find it crazy that Apple went back to magsafe in the m4 (maybe earlier but that's the machine I have at work). But at least you can still charge over usb-c.
I can't get myself to do the battery-built-in-to-charger thing. I've always treated portable power banks as semi-disposable since they do eventually get worse and fail, and it feels icky to me to tie ~immortal charging gear to something that will die.
I did have the same feeling about flashlights for camping/hiking with lithium batteries, though, until someone walked me through just how much better they are than lugging around AAs.
When I've been working on stuff that requires a SSO login, I noticed that it makes, what I considered, hostile anti-user choices in defaulting to tracking pieces of information I didn't want to track and hadn't mentioned.
Fair that I didn't instruct it explicitly to make more pro-user choices, it just seemed to think slurping as much information into the backend was an default intention. Wasted a few more tokens to iterate on it to remove things, but it was IMO interesting enough that I finally submitted feedback around what I imagine is an interesting training problem.
I would love to work for NASA so much even at a significant pay cut, but almost everything I've read in the past was they still do drug screenings for a lot of positions I was interested in. Maybe someday they will pull their heads out of the dark ages.
Normally I would agree but I get it with regards to NASA. They do life and death stuff that has like zero margin of error. They probably shouldn't be in the business of hiring people who's edible might be lasting longer than they expected.
I went to see if I had any replies to a comment I left on a video for the first time today and it's really hidden to get back to them if you don't remember the exact video. I wonder if it's purposeful friction or just not a priority.
In my case I have almost all notifications disabled so maybe there's an option somewhere. Generally find those notification badges too powerful for me to not check and then get waylaid doom scrolling/watching, so I've made it a habit to always disable them everywhere.
Somewhat tempted to re-enable it as I only really comment on videos that are for very very niche communities and I'm usually answering or asking questions.
This is one of the first tech waves where I feel like I'm on the very very groundfloor for a lot of exploration and it only feels like people have been paying closer attention in the last year. I can't imagine too many 'standard' standards becoming a standard that quickly.
It's new enough that Google seems to be throwing pasta against the wall and seeing what products and protocols stick. Antigravity for example seems too early to me, I think they just came out with another type of orchestrator, but the whole field seems to be exploring at the same time.
Everyone and their uncle is making an orchestrator now! I take a very cautious approach lately where I haven't been loading up my tools like agents, ides, browsers, phones with too much extra stuff because as soon as I switch something or something new comes out that doesn't support something I built a workflow around the tool either becomes inaccessible to me, or now a bigger learning curve than I have the patience for.
I've been a big proponent of trying to get all these things working locally for myself (I need to bite the bullet on some beefy video cards finally), and even just getting tool calls to work with some qwen models to be so counterintuitive.
Hah! I made this at work, when I started getting Claude to record the replication and demonstration of the fix as gifs on PRs people finally started asking me about the cool things I was doing.
The reproduction has been one of the things I've been struggling with in regards to consistency of bringing up the right envs. At the moment I've been approaching it as a MCP server that holds a few tools to bring up specific versions or branches of my stack to then find where a bug was introduced, build that commit prove that it wasnt in the previous one, and then fix it and run the full stack again with the fix component, then run through our local integration tests.
This is the stuff that makes me feel like I'm on steroids now, my whole dev debug process can be run with a few instructions, game changing.
Yes, GIF in PR is really nice in my view too :) Our reproduction runs in a sandboxed per-repo environment that we re-verify the fix in before opening the PR. Would love to have your thoughts on beta and to see how it goes on real world apps. I'm reachable on support AT neverbreak.ai
I would love to read about why that stuff is the way it is from the engineers, hmm that might be a good spelunking. I really must be missing something that makes it harder than I think it really should be.
reply