Fot at home, I tend to stick with 2.4 GHz. It is slower, but with a <100 Mbit uplink to the internet, local speed does not matter. 2.4 does just work better with less APs and thicker walls.
2.4 GHz is unreliable for me these days due to interference from bluetooth headphones and hearing aids that other people are using. The issues tend to only show up during extended periods of video streaming, and having looked at a bunch of traffic captures over the holidays, it seems to be limited to certain streaming services sending very large bursts of traffic at extremely high rates (likely from servers with 100+ Gbps interfaces using TSO to reduce CPU usage). That makes me think that the regularly paced bluetooth interference from real time audio streams limits the maximum viable burst size of a 2.4 GHz wifi radio.
Yes, this happened a bunch more over the Christmas holiday when we had an extra 3 or 4 younger family members all listening to music and videos over their bluetooth ear buds and headphones, which made it much easier to track down as it was quite a rare intermittent failure with only a single bluetooth device being active.
This also only works if you're not living in an apartment building. Even then, there's Bluetooth and other things that don't share spectrum nicely with 802.11.
No, that sounds right. First you don't know how to write something, then you know one way, then you know multiple ways, then later you know multiple ways and have the instinct to pick the best one first.
> [...] will change your lice when you learn how to program with it.
But how (honest question) do you learn hoe to peogram with it. All I see is people using it to program and stop thinking about all the steps required between start and goal. That's not learning, that's assisted doing and that will only get you as far as the tooling (the assistent) goes. I've yet so see someone that learned coding with AI and was then able to do the same job without it.
I can feel you. I tend to ignore WhatsApp messages at all or take up to 2-3 weeks to respond (as soon as I'm in the mood for it). People around me know that and mostly just call if they want something. Problem solved (IMHO).
As an owner of a Volco Electric, I am happy that they are focusing on fonts and adding nicknames to cars instead of fixing the countless bugs and issues these cars have regarding software.
/s
Issues I encountered:
- The schedule for AC charging moves by 1 hour when DST changes. So someone thought let's ignore daylight saving times for that.
- The app randomly says "could not start heating/cooling", but still started it.
- The last few times, AC schedule and power limit were ignored by the car (so charged 16 A but the car said only 14 A allowed)
- Randomly, the AC schedule is in a random timezone (like 7-9h lff), but just for one day.
- Sound sometimes does not work, like at all. Reboot the center display helps, but takes a couple of minutes.
Most days, it feels like they don't drive their own cars.
> Sound sometimes does not work, like at all. Reboot the center display helps, but takes a couple of minutes.
This one is really bad because it turns out that the turn signal clicks play through the sound system. So when this bug happens, you lose a key bit of feedback from the car until you pull over and restart the system.
Agreed. The software situation seems to be getting more confusing by the month. AAOS builds have suddenly jumped from 3.x to 4.x and the release notes say "various fixes". Um, like what? Was there a major update to something or not?
I'm still on a AAOS 2.x release from 2023 and will not upgrade at this point.
AFAIK, high-voltage and high-power cables are usually over-ground for two reasons: (1) less losses with air as coolant and (2) repairs are so much easier.
Not having an accessible way to the cable is somethibg you don't want if you don't know exaclty where and what is broken (because you can't see it).
That's why you usually lay them under roads - then you can dig a broken bit up with just a few hours notice.
Generally you do know where things are broken - there are tools to identify the exact location of both broken conductors and broken insulation by reflecting high frequency signals down the cable.
It annoys me so much when developers think they can do it better and link with JavaScript. Interactions (like opening a dialog) witj JS - yes. Navigating to sites/positions in-site - that is just dumb. So many pages break the "open in new tab" behaviour with this implementation.
Gitlab enters the room, where self-hosted runners are as free as in free beer (maintenance yes, but no limit on runners and no pricing expect on a per-user basis).
Yes, gitlab does still have free self-hosted runners. OTOH, github has a free organisation plan and gitlab doesn't. So yes, strictly speaking self-hosted runners are free, but you're paying for the dev-seats.
> But then I mentioned I had credits on Fly.io, was eligible for Vercel's free tier, had a Cloudflare account, and a Neon database.
I miss the days where deploying an app was just uploading some files. Maybe we need AI to understand this artificial complexity we introduced ourselves?
Right there with you. I’m working on fixing an app deployment this weekend myself and dreading picking my way through GitHub actions, ansible scripts, container configs, and deployment APIs to figure how why the thing stopped deploying. Thank goodness it’s just deploying to VMs and not Kube, or I’d probably lose a week.
reply