Skill loss is real. BUT, I have been complaining about skill loss to my bosses for literally a decade. So AI is just one problem for me. I was coding less and less every year for some reason.
I'm not sure skill loss is such a huge issue, in other words. It might just be a sign that the nature of our work if shifting. Being able to recite the C++ standard and using all the 100s of features correctly will just not be as highly regarded as knowing good architecture instead?
There is an inescapable connection between the two. Knowing that stuff is not _equivalent_ to knowing good architecture, but it's hard to imagine what knowing good architecture would look like without being able to "think in code" through quite a few relatively narrow implementation details. Without that, you won't know the shape of the problem and how to architect around it.
I AM mad, because I just signed up for my private copilot sub. Otoh I do have it at work. I suspect we will start noticing differences there, too, but it all depends on the top users, vs average user since it is now pooled, IF they dont just allow extra usage. Bu that has become more expensive now, so not sure what they will do. I am hopeful that very few actually even use it. In my and surrounding teams, only maybe 1 out of 3 people really use it much.
Ive also had huge problems with copilot and terminals, mostly due to corporate antivirus which makes it impossible to install clink for example. So the Shell integration never really worked. It has been fixed for a couple of months though now, and its working, maybe not great but at least very good.
The only sad thing is trying to use tools in a VS developer prompt (and how could this not have been fixed ages ago, its literall YOUR OWN flagship product). It knows how to launch the .cmd for it, but thats incredibly slow for single commands. Would be nice if I could tell it to just use an open terminal.
Most of the major vendors are already assembling x86 laptops for the far larger Windows market, it's cheaper to just reuse those models for ChromeOS instead of designing a special ARM design, which in turn due to lack of scale are priced similarly to their x86 counterpart. Price sensitive customers thus don't see that much saving.
Battery life is nice, but I doubt there's that much market yearning for a cheap laptop with long battery life. People who really need large screen for long work without wall power either go at x64 (which can reach 12 hours on mid range now), or change their workflow to use Android tablet. The ubiquity of USB charging port that can power the laptop (or at least top it up while standing by on lunch) also means even if an x86 laptop may not last an entire day, the owner don't have to suffer the inconvenience of carrying around the power brick.
There won't be that much saving due to the lack of scale. The mentality of (normal, well adjusted) people around me is to dismiss laptop entirely as a personal computing device, they have their phones and tablets that are far easier to use. For them to get a laptop would imply they're forced to, because there are Windows apps unavailable for Android/iOS. A cheap Arm notebook is useless for them (unless Microsoft somehow decide to work with Mediatek and the rest for cheap WoA devices). Chromebook never gained popularity in my country with lack of reliable and affordable internet access so the realistic OS would be either one of those Linux distro that support ARM (but in turn, most people don't care about Linux), or Android, in which case it's still far more natural to just get a tablet with a keyboard attachment because Android desktop experience and the apps ecosystem aren't there yet.
Is Opus nerfed somehow in Copilot? Ive tried it numerous times, it has never reallt woved me. They seem to have awfully small context windows, but still. Its mostly their reasoning which has been off
Codex is just so much better, or the genera GPT models.
reply