pull down to refresh

Interesting point. Would you use software from a noob to manage your money? Your privacy?

Would I trust a noob with my sats or privacy? No

but I also wouldn't have trusted that same noob before AI

id say the question is whether AI makes them more able than before, clearly it does

The fact that they're still not a full stack dev doesn't change that

reply
100 sats \ 6 replies \ @optimism 20h

How can you tell if an author is "capable enough"?

reply

You don't need to know in advance who's 'capable enough'

I never said that AI makes everyone a fullstack dev

I said that AI makes noobs more capable than they were before

Those are two different arguments

reply
79 sats \ 4 replies \ @optimism 17h

It removes barriers, we agree on that. Capability is a big word though as it depends on the specifics of the goal you're trying to achieve. If we're talking nothing-at-stake, zero-requirements throwaway stuff, then yes, everyone is super capable now. Has been since GPT-2.

I know because I helped a fair share of those "noobs" by completely rewriting the GPT generated prototype code to their ideas into productized software. Back then, not a single line survived. Nowadays, maybe some lines will survive. But more often than not, even the boilerplate is poor.

reply

That's fair, and you've obviously cut your teeth by doing the hard work of turning slop into real software

I just think AI is increasing what noobs can accomplish, remembering that only pro's like yourself can confidently present a project to a paying customer with assurance of reliability

reply
79 sats \ 2 replies \ @optimism 16h

I'm not worried about paid projects. If you mess those up and your customer is half-competent, you'll pay for your own fuckups. Damage clauses are no joke.

In a professional setting, I'm much more worried about FOSS, and specifically, open source libraries that are adapted into everyone's apps by LLMs (also for those paid projects.) Not only is it a cesspool of vulnerability in the delivery mechanism (all those npm malware infections of late) but underlying libraries that were once carefully crafted are now getting sloppy. A minor update can fuck you up. If you don't know what you're doing, you don't know to even ask the bot to assess your dependency.

Now, if anyone vibe-codes something for themselves that solves a problem they have, I have no issues with that at all. I encourage that. But everyone wants to be famous now from the work of an LLM that itself has no fucking clue (because it is not some sentient being, despite what the CEOs claim.) Thus, the slop gets published and marketed. And when you become a user of said product because everyone and their dog was telling you on X and nostr (and SN!) how fucking awesome this new app is, you're at risk too. And if 99% of devs don't check before they install, think about which users are going to get rekt: all of 'em.

reply

Excellently laid out concerns and I do agree with you on those, noobs wouldn't see the shit lurking deep in the trenches like you. Good points well made

reply
79 sats \ 0 replies \ @optimism 15h

The thing is, they could! It's not rocket science! But for that you need to learn. And that's a new barrier.

Therefore, I think that "everything changes, but overall doesn't get better or worse" is the ultimate outcome.