You want workflows where the human gates are properly placed, not a "software factory" that you never place eyes on.
1,277 karma · joined February 5, 2024
You want workflows where the human gates are properly placed, not a "software factory" that you never place eyes on.
I do not believe Zuck, Musk, or any of the other boogeyman in Silicon Valley are capable of that level of deception and manipulation.
I find it much more plausible that when trying to build world-changing businesses and products you squish, displace, and flip tables when you didn't really intend to.
We'll need a few more of "him" to dig us out of this situation I reckon, but overall I still hope it's possible.
(Anyone asking antagonistic questions can go ahead and save their fingers, I won't respond to the petty comments.)
What if there's always been two general buckets (or more)? One bucket are large systems that must perform to spec, and the rest are "good enough" systems to at must simply not blow up enough to be useful (see: almost every enterprise software ever written)
I'm likely wrong. But it's an interesting thought experiment. Humans have produced shit code for a long time, and it's not clear that clueless humans + shit AI code is something the market will reject.
Like Omakase.
And I sat here struggling for 5 minutes to think of a single instance. I couldn't come up with one.
So maybe the underlying problem is that journalism isn't nearly as valuable as it thinks it should be.
The sum of ALL of these classes of bugs is such that our clients haven't complained about the software being particularly faulty. It's impossible to tell if it's more or less buggy than it would've been written entirely by hand, but I suspect it's less buggy than it would be if written by hand.
It is getting worse, faster. That's objectively true.
Why would this person be more skilled? And more importantly, what does it mean to be "skilled" in the era of AI?
I'm trying to be open-minded to both sides, but I have senior engineers on my team with a fleet of agents, shipping code they don't fully understand, and... everything is fine. Stuff still breaks, we fix it. Clients ask "How does XYZ work?" and we say, "Not sure, let us get back to you." And they're totally fine with that answer.
Everything within me screams that this is wrong and we should have intimate familiarity with the system, but I cannot find any evidence that the path of "running a team" instead of "building engineering skill" is not going to work out fine in the long-run. (Yes, my comparison between "team" and "engineering skill" is a bit rough but I'm not interested in the semantics.)
All the evidence that I'm seeing in my own business, with senior engineers meeting clients' needs with autonomous agentic teams is that it's all fine, and while there are gaps, it's actually okay. Clients are happy. Software works 80-90% of the team exactly as it should. Bugs are fixed quickly. We ship more in 3 months than we previously could've shipped in a year. I'm baffled and frankly not as advanced as my devs (I still ask questions one by one to my agent, like a Real Caveman!)
It makes me wildly uncomfortable so I'm trying to wrestle with this. I want your statement to be true, but I just don't see evidence of that.
I am not convinced that "cheating", being a moral issue, is a solvable problem with LLMs.
As the old saying goes (especially in military training), "If you ain't cheatin', you ain't tryin'"
We've made the models really good at persistently trying.
I have no problem with vibe coded software.
The recent sprawl of viruses, worms, and malware should give everyone pause when installing fresh software.
This is an app. Not a protocol, not a platform, an app.
It's just... a way to remember stuff? You're handing all this data to a company, relying on "trust me bro, we'll be responsible" as a promise to be ethical?
This is beyond perplexing.
My company is still on GitHub... for now. But incidents like this are becoming more common and I'm becoming less tolerant of it. I suspect many feel the same, but it takes time to persuade the masses.
Where did anyone advocate for "large scale code generation"? LLMs are a fantastic way to go from, "We thought this this feature" to "It's shipped and in people's hands". That could've been 100 lines or 1,000 lines but that's not the point.
Solve the leadership problem and the AI thing becomes an advantage instead of a problem.
Assuming of course everything else stays the same (quality, etc.)
So AI isn't really doing anything but giving sharper tools to both groups.
So, as it was before, we simply need to set expectations and remove those who cannot adapt and meet expectations... You know, the way it's always been.
So why is AI the problem here?
While it is tempting view all of human progress as some heroic feat of raging against the machine, it seems much more likely to me that progress came from accepting reality, and then working within the bounds of physics.
The latter half of your comment is rather smug, but I wouldn't look down on people who have peacefully accepted reality. Time is fleeting and we are but flowers in a field—briefly brightly bloomed and then withered.
I hold our politicians in no high regard, but I do hold myself to some standard in that I won't accuse someone of corrupt conduct unless I actually have evidence.
The point being, it's laughable to slander someone else's morality while you lie to posture your own.
Or is this one of those, "I don't like that person, so I'll just make stuff up" things?
It is also a place where the next generation can learn the wonder and beauty of nature.
They also tend to work closely with conservation efforts worldwide.
So... yeahhh, no. Not at all the same.
I'm not joking. This is the reason I heard for them making it smaller.
That seems like quite the accusation and I haven't heard anything about that.