Tried to link to the specific timestamp in the video, where the p99 lie is discussed. Core takeaway for me was that most users of a page will experience the p99 latency of the system: https://youtu.be/lJ8ydIuPFeU?si=HasLt5QBsB1tzww_&t=648
> Amazon is using math to help solve one of artificial intelligence’s most intractable problems
Seems like pretty bad way to start this article off. AI is math at the end of the day how is this special.
Generally the article seems to lack a lot of substance or specifics on what or how effective automated reasoning is at improving results. Actual substantive studies/papers might be more interesting...
I liked how many of these solutions were pretty "simple" and easily applicable to many engineering teams. Our team similarly saved a ton by just "right-scaling" our AWS resources, applying TTL where possible.
Nice article, but was looking forward to more of the "in production" angle (e.g. more operations, monitoring, performance). Instead this seemed to more focus on the the maintainability, developer experience using Rust and the ecosystem.
Thanks. Could you expand more, what specifically would you like to know? I'm happy to try and explore different angles of Rust in production, I'm just not sure that setting up open-telemetry is that different from other languages.
Sorry, yeah I was a bit unclear. I was curious if there was any metrics to show how maybe server CPU/Memory or client-side latency changed after moving your app to Rust and running for a year.
But that's fair, if adding open-telemetry is maybe overkill to add to the application it might not apply as much to your use-case.
I love CarPlay/AA, and maybe this is hyperbole but not doing CarPlay/AA isn't that crazy of a decision. Tesla, GM, other big automakers have done this too.
It's not always about that. AA and Car play are a very common reason for service visits and it's not uncommon for customers to get their entire head unit replaced because of frozen screens or whatever. GM hired a lead dev from CarPlay to help lead their replacement. When they work it's great but my touchscreen freezes regularly and it's extremely annoying.
So basically, automakers can't make a robust console to simply display the streamed content. What makes you think that their software will be any better?
It’s the natural result when software (and sometimes hardware) is treated as a line item to be contracted out to the lowest bidder. Infotainment is a core feature that shouldn’t be cheaped out on, but many automakers haven’t realized that.
It’s also just more lucrative to drive people to use the built in stuff instead of mirroring their phone, both for easier data mining and for pushing users into subscriptions.
Tesla also started doing their "iPad with a car attached" thing before CarPlay was released in 2014.
Arguably they could have switched over at some time, but they're doing well enough that they haven't felt the need.
But I'd be surprised if there isn't a Tesla somewhere in the bowels of Musk's volcano lair that has CarPlay running, just waiting for the right time to release it as a software upgrade option (only $1000!).
Address book syncing is the main issue. I want my contacts on my phone. So taking phone calls gets a bit awkward, though with Siri getting a little better it’s sort of doable.
Other than that it’s the constant re-typing of destinations from the calendar.
Here’s a fun tip I learned recently - you can press the share button on your phone and send the location to Tesla. This makes copying addresses from calendar or anywhere super easy
reply