IMHO, this whole thing could be read with "human" instread of "agent" and would make the exact same amount of sense.

"We put 200 human in a room and gave them instructions how to build a browser. They coded for hours, resolving merge conflicts and producing code that did not build in the end without intervention of seniors []. We think, giving them better instructions leads to better results"

So they actually invented humans? And will it come down to either "managing humans" or "managing agents"? One of both will be more reliable, more predictable and more convenient to work with. And my guess is, it is not an agent...

As it seemed in the git log, something is weird.

> Sometimes, uninstalling Copilot doesn't take it off the list of startup apps, so when you reboot your computer, it may come back.

It is not yours anymore if you can't uninstall stuff. You may own hardware, but you do not own anything on it.

> It is not yours anymore if you can't uninstall stuff.

But the article is literally instructions on how to uninstall it…also you can just uninstall Windows entirely.

Like I get where you’re coming from, but let’s not pretend that Windows PCs are iPhones now just because of Microsoft’s annoying dark patterns (patterns they’ve been following for years before Copilot came out).

There is really no need to split hairs here, Windows is definitely to be compared to iphones when it comes to how much you are in control.

The instructions described in the article will stop working with the next Windows update, as copilot usage is tied to middle manager #78's KPIs at Microsoft.

Suppose you don't use Windows though. What's Microsoft going to do then?

I think they would do the same thing that Apple does when you buy an android phone, to continue the metaphor

It _does_, but I guess (and it would not be the first time) Microsoft will find a way to even undo that and reinstall Copilot with the next update.

They could - and some of the 3rd party vendors did: There is a 1Password 7 and a 1Password 8. There was also a Things 1/2, which is now a Things 3. it usually works by creating a new app, and not updating the old one anymore.

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.

I have at least 10 neighbours on each 2.4GHz channel.

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.

As I get older (more experienced) I really write less code, but more of the code I write is correct. Am I doing something wrong?

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.

No, you are doing it exactly right. Code is a liability not an asset, hence, technical debt.

> [...] 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.

Regardless, I think the font is somewhat nice.

> 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.

The title shows correctly but the text is static and looks like an example unrelated to the title.

Yeah, it's just a placeholder.

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.