The thing to look for is how they go about solving a problem. That's the key. Coding is easy. Figuring out what the problem is and how to go about solving it, that's the hard part. Especially given that the problem the user says they need solved is often not the problem they actually have.
There have been some interesting threads on Twitter recently where they discovered that by flipping two bits in a local AI model they could convert it to full "KILL ALL HUMANS!" mode where everything it generates looks like posts from the deep, dark depths of Reddit.
My employer announced that AI costs will be billed back to departments. Token use (almost entirely among developers) was cut in half without affecting productivity, and perhaps even enhancing productivity because they had to think a bit about the best use of what they had instead of trying random things.
I've only been paying attention since 1990 but every single time a feature they don't offer "is stupid" until they offer it.
Even when I liked the company this Cluster B behavior always bothered me.
If there's an example of "that's a really nice feature our competitor has but we don't offer it yet" I haven't seen it.
The closest I can think of was offering WebObjects for Solaris. Not sure if that ever shipped or we just had a beta. I bailed from that Healthcare IT team when the CIO pulled funding for two-phase commit among disparate patient medication systems with the rationale "even if medication errors kill someone it'll be cheaper to settle the lawsuits than pay for the license." Enough people left that they outsourced and everybody still hates that replacement system.
I learned too late that MBA's don't care about quality.
> everything you do has fucked the consumers
Say more
Let them do their thing.
I remember in High School the Camaro guys couldn't stop talking about how their Camaros were better than Mustangs but the Mustang guys never felt the need to denigrate the Camaros.
It's a matter of nature.
unrelated: Tailscale is so fooked today:
https://www.bleepingcomputer.c...
Some people here may need to panic right about now.
You missed the point.
A friend of mine made a tea-timer app for the iPhone. Where you enter what tea you are making and it sets the correct number of minutes. Today, people would ask ChatGPT before they go on the App Store to search for something like that. That's the point. Not what YOU would do, but what the general public does. And for Jane Doe, ChatGPT has replaced a lot of these specialty apps.
Skills are great until they aren't. The problem is exactly what you say: You can literally create a skill by telling the LLM to create a skill. Which is... why the f do I need to make a skill if the AI already knows how to do it?
Properly created skills, that include reference material, specific instructions, and expert knowledge the LLM doesn't have or that's buried somewhere under 10 layers of reddit posts is genuinely useful. But most skills aren't. I'm constantly underwhelmed by hyped-up skills that, when I look at them, turn out to be bland, basic instructions.
The right way to do this is to hire a group of developers and have test volunteers report workflow problems - then FIX them - then iterate. That's the point of choosing an open source solution.
Eventually there would be no problems remaining.
But so many possible scenarios exist that it's impossible to guess what happened here.
PS _NSA_KEY
There are apparently other unpatched vulnerabilities that are known but 'too busy':
It sounds like this fix got done because it was 'accidentally' posted as a public PR.
Yeah, the threat actor would need a foothold on the PXE network, which is a private VLAN (or better) in the competent case.
That's why we worry about APT's and such.
Granted, you'll find people on certain cloud providers who do far too much on a public IP.
Ignore network traffic until security self-defenses are in place.
Yeah, you can have a buffer overflow anytime, and they can be bad, but the situation explicitly pointed out an "invaders not recognized as evil before armed guards are posted" situation.
If this had been a bad buffer overflow that occurred AFTER the defenses were in place, maybe it would've resulted in a compromise, or maybe the defenses would've rendered it ineffective.
... the machine can be affected by outside input before it's security/self-defense system is ready?
Oops.
There is very little future in being right when your boss is wrong.
