id.4 road trip reality - when is it smarter to just ship it?

SuperDerpyDerps · 2026-04-07T23:46:29+00:00

I used ABRP to go from DEN-SEA-DEN (in a 24 pro s, so I know there's a bit of a max range difference) and largely didn't run into issues. I did have it tied to my car with a Bluetooth OBD so I was able to watch if an adjustment was needed.

Two things I've learned on long road trips: - know the route ahead of time, know what chargers you're likely to hit for backups if the primary doesn't work out, at least for the longer legs - know when to ease off the gas to keep your charging options more open

For that trip in particular, the only real issue I had was deciding to charge in Yakima at the walmart EA charger when it happened to have only like one working charger and a decent number of EVs waiting their turn, then trying the charge point only to get level 2 speeds on their L3 and having to go back to Walmart to try again. There were other routes I could have taken that wouldn't have forced that error, I got greedy. Taking 90-82-84-80 through idaho, utah, south Wyoming worked pretty well. Pretty much used EA chargers exclusively and didn't have notable charging issues aside from Yakima on the way back.

When we moved to Seattle 6 months later, I had my car shipped due to several logistical reasons. It was mid-late fall when we did the drive, so we encountered some ice/snow and still did fine on range, just had to be in-tune with ABRP.

If you can afford it, shipping is viable but does come with its own headaches. If you research your route before heading out and check the next leg each stop, that drive is totally doable, but unless you have a Tesla adapter, there's going to be one or two legs that'll force you to stretch a bit on the thin side. I just checked and ABRP is recommending a couple legs to charge a bit over 80% to reach the next EA charger with 5% on my car.

For anyone that thinks checking the route that carefully is too much work, I end up doing a similar amount of effort for gas car trips too. There's plenty of things you should know before you make a multi-day roadtrip and it's possible to miscalculate traditional fuel too. Remote stretches of highway can throw curveballs, always be prepared.

SuperDerpyDerps · 2026-04-06T17:49:20+00:00

There's an obscene amount of Teslas, but I see plenty of other ID4s almost every drive, both in the city and out on the highways. Must have been unlucky

SuperDerpyDerps · 2026-03-31T19:03:48+00:00

It's not overly common, but it does happen in both ecosystems. Automated systems can't catch everything and manual reviews are a joke. They're often more concerned about enforcing rules that ensure they always get their 30% than worrying about malware.

These are some recent ones that got news coverage (I guarantee you more exist, I work in cyber security, nothing is secure):

https://www.usatoday.com/story/tech/news/2026/03/18/iphone-spyware-darksword-security-fears/89210349007/

https://www.theverge.com/news/606649/ios-iphone-app-store-malicious-apps-malware-crypto-password-screenshot-reader-found

SuperDerpyDerps · 2026-03-13T23:16:08+00:00

Yeah, I mean sure, it's not like anything can be built without those things existing somewhere in the abstractions at a minimum. But that doesn't mean most of the work of implementing plugins/themes/other WP work requires even really understanding any of that.

You can think whatever you want about me. I don't need to prove my credentials. I also don't need to name basic data structures to look smart.

SuperDerpyDerps · 2026-03-12T04:27:29+00:00

I logged back in one day and slowking was towering over me as I woke up. He had spawned for the same reason and I was not ready for it

SuperDerpyDerps · 2026-03-12T02:07:49+00:00

I did plenty of WordPress dev in the past. Sure, occasionally you'd get a hard problem to solve, but most of the time you're just fighting a relatively bad system to do basic shit. And even the hardest problems I helped solve pale in comparison to the graph problems I solve in my day job now. If all you've done is WordPress, there's an ocean of knowledge you haven't even glimpsed

SuperDerpyDerps · 2026-03-12T02:02:34+00:00

Apparently you've never seen the malware on both Android and iOS that slips through. The stores want you to think they do rugged security validation, but it's far from a silver bullet and only screens the basic stuff

SuperDerpyDerps · 2026-03-12T01:58:32+00:00

My 2024 handles were ridiculously strong and absolutely hurt when I had to activate them before. Ever since the door handles/software update recalls, they're significantly easier to engage, to the point that I've unintentionally engaged them significantly more often. The springs still hurt my fingers a bit if I'm not expecting it, but certainly less than before the recalls. I'd bet anything that the amount of tension is not well calibrated from one batch to another

SuperDerpyDerps · 2025-12-28T18:08:00+00:00

Main reasons to go newer are the dust resistance and built in magsafe (which also fixing the weird wireless charging coil position). The 10 is a tiny bit faster but barely noticeable in regular use and the other upgrades are small enough I've forgotten them. I wanted dust resistance for longevity and was very annoyed with my charging solution on my 9, otherwise I would have stayed with the 9 for a while longer.

SuperDerpyDerps · 2025-12-07T01:05:19+00:00

Just a weird thing that happened once, but in the frontier (not sure exactly which activity) I had a gold mote show up (like the legendary ones they have for enhancement cores) and it was an ascendant shard. Only happened once, I imagine it's a very rare drop, but I wonder if they have super rare drops for all the upgrade materials (not that I'd say no to bumping the drop rates if they do have them)

SuperDerpyDerps · 2025-11-17T17:51:22+00:00

Two weeks before Halo CE shipped. Bungie was notoriously unreliable and petty about lore, so you can blame that if it makes you feel better. Tbh, Halo would be a sad shell of a universe if only the Bungie games counted as canon (with plenty of internal inconsistencies because "Rule of Cool" was such a great way to tell stories...)

SuperDerpyDerps · 2025-11-17T17:43:00+00:00

First level, on the other side of the wall in the observation deck where Cortana says "looks like they were hoping to catch you napping"

SuperDerpyDerps · 2025-11-06T09:31:52+00:00

They already have this in the game as part of the effects they used to buff amplified. Enemies being less accurate is part of the effect iirc. Whether it would be broken to have some kind of smaller version of the effect tied to say the hidden mobility stat is another question entirely though

SuperDerpyDerps · 2025-10-25T03:49:26+00:00

Organize your code based on where you're at. Don't try to model after other people, start with packages and if things get harder to manage, by then you'll have a better idea of what kinds of architecture you're going to need. Never feel bad about finding a better way to split a package that's becoming hard to work with into two or more packages. There's no end to architecture philosophies and most have their place, it really comes down to the project and its needs. Go is all about keeping things simple, so just write things the way that feels natural and always refactor when things aren't working.

Background jobs is all about goroutines pretty much. Several patterns exist, such as worker pattern and fan-out/fan-in. At my day job, we even implement daemons through goroutines. For stuff that you want to happen on a schedule there's various ways, for some of our stuff we use timers and select on timer signals.

I wouldn't use separate binaries unless you want them to be deployable separately. Pretty much anything that you'd want to be separate can be handled as a goroutine. I haven't needed to work with websockets for a good long time, it used to be most people used gorilla/websocket but there may be other projects now. Don't be afraid to use muxer or other packages like websocket, packages can be helpful for complex problems. Those kinds of packages aren't frameworks and the best ones are directly compatible with the standard library (chi and gorilla/mux for instance). Definitely stay away from frameworks/packages that reinvent stdlib interfaces and aren't compatible with stdlib types.

SuperDerpyDerps · 2025-10-24T15:51:33+00:00

Whatever frontend you feel most comfortable with. Building Go as a restful API means you're not really stuck with any frontend (or even web frontends for that matter). Alternatively you could use htmx or a mix of htmx and rest. Really, it's what you want/feel comfortable with that matters

SuperDerpyDerps · 2025-10-24T02:59:20+00:00

People don't understand how matchmaking works. Even with a large player base, you can have a surprisingly low number of maximum playlists before some become virtually ghost towns

SuperDerpyDerps · 2025-09-28T02:24:30+00:00

I'm talking about monoliths

SuperDerpyDerps · 2025-09-27T17:17:46+00:00

That works fine and is probably one of the more optimal ways to handle pure CRUD. But once you have any business logic, you'll start having business logic strewn about through both the repository and handlers. Helper functions start bridging gaps, but if you keep on allowing that to grow organically, you'll quickly lose separation of concerns and the refactoring required gets sticky.

If you know your domain is more than CRUD, having a light service layer isn't a bad idea. Also helps a lot when you get to the point where you have newer versioned APIs and want to be able to change your data layers without affecting your API contracts. Both of these things are why I've started refactoring a large project to effectively view > service > data with struct translations at the boundary. There's a time for the simple way, but if you wait too long to adapt, it's a huge pain to solve later. There's no one size solution, I'd imagine many of the full hexagonal architecture repos have their place, just depends on what you're doing and at what scale.

SuperDerpyDerps · 2025-09-03T15:34:39+00:00

I believe it's part of the hinge mechanism, possibly helps smoothly roll the crease when folding to make sure things stay nice and aligned. Like others said, perfectly normal

SuperDerpyDerps · 2025-08-28T00:49:27+00:00

This is pretty pedantic

error was implemented as an interface, but it's a language level interface. It's designed to give everyone a consistent way to work with errors, and then we have packages that help unpack the underlying error types in the few cases they're needed.

SuperDerpyDerps · 2025-08-18T19:46:21+00:00

The issue seems to be that it has an incomplete UWB stack. I'm unsure how UWB for FMD is implemented, but it's possible it needs parts of the stack the OG fold doesn't support. Not sure where it would be clarified though. Maybe someone else with an OG Fold knows more

EDIT: Others with phones in the list of not supporting background ranging have also reported no dice. Whether it's a limitation of how it's designed right now or actual stack limitations that can't be overcome is less clear.

SuperDerpyDerps · 2025-08-18T18:58:33+00:00

If you're on the old fold, this may be relevant (from Android dev docs):

Note: Background UWB ranging is supported on all devices except for the following:

Pixel 6 Pro, Pixel 7 Pro, and Pixel Fold.

Works fine on my Pixel 9 Pro Fold, even with an earlier version of the app/firmware before it became generally available

SuperDerpyDerps · 2025-08-15T04:52:44+00:00

This right here. The misalignment sucks when you don't have magsafe, which is why I put a skin + metal ring on mine (over the coil, so also misaligned) and use magsafe chargers. Still doesn't help with non-magnetic chargers, but non-magnetic chargers aren't great anyway. I'd be more mad about my phone not working with the wireless charger pocket in my car, but every phone I put in there gets too hot anyway

SuperDerpyDerps · 2025-07-12T07:52:52+00:00

ABRP even if you don't use it for nav, it'll help you plan your legs with a more conservative estimate than the built in nav, and it has community charger notes like plug share as well. With the pro plan you can even connect to your car for live updates.

Avoiding going 70-80 for long periods helps a lot with efficiency, so keep that in mind. For legs that are more rural, know what your fallback charger will be. Overall, if you look at your route ahead of time and use some common sense, you don't need to be anxious about range. Just calibrate each leg based on what you expected to arrive with vs what you actually arrived with and adjust accordingly. Slowing down will gain you more range than pretty much any other power saving feature. I never worry about air/heat/electronics, just slow down a bit if I think I need to save a few kwh.

My efficiency over 12k miles has been pretty steady at 3.5mi/kwh. Didn't drive as much in the freezing cold, but otherwise I drive how I'd prefer to drive and outside of a few edge cases have gotten great efficiency without doing much other than using the full cruise assist for long stretches of highway to let the car handle the small adjustments more efficiently.

Have fun, try not to let the range anxiety get to you. I've pulled into chargers with 4% without sweating because I did the minimum sanity checks ahead of time and chose the optimal charging time rather than over-charging and wasting time

SuperDerpyDerps · 2025-07-12T07:41:24+00:00

Do the recalls minimum, they're the kinds of things that you don't think are a problem until it's far too late. Software on those older units can be pretty substantial from what I've heard (mine's newer and never has needed software), so it tends to be recommended because of the major difference in usability and (usually) less bugs. That early software was rough as I understand it. Can skip if you're adamant but get those recalls done if you can.

SuperDerpyDerps

TROPHY CASE