Depends what quality of work they want? Hopefully they've learned their lessons in the first outsourcing craze, before AI lured them to another ride on the same carousel.
from my experience, offshore talent was for boilerplate coding. and the new bar for quality is now . so I think most LLMs are better than the majority offshore talent nowadays
My feeling is that there's an unlimited amount of work left to do. Software today sucks in so many ways. It's buggy and inflexible and limited in so many ways. My bet is on Jevon's paradox kicking in big-time.
Software tends to be made only good enough to do the job. There is an unlimited amount of work that could be done but not an unlimited amount of work companies are willing to fund, and the bar for "good enough" keeps dropping.
I don't think that that logic follows. For most jobs, even before generative AI, we weren't paying "per work item", we were paying "per person per time". We could conceivably build 4x as much for the same cost, and it would require the same amount of money.
My expectation is that most businesses will decide that they can get by with 1/2 to 1/4 of their staff, making immediate improvements to their bottom line, instead of trying to double or quadruple the work they’re tackling, because one approach is much safer than the other.
Sure but that's a different point than what you were making. You acted like all this increased productivity wouldn't have the money for it, and I was arguing it would cost roughly the same amount of money as it does now since per-person-per-time was typically the cost we were measuring. Now you're saying they're going to want to spend less money.
Yes, more software will be produced more than ever before at an increasing rate by agents as they continue to close their own loop. Remember "prompt engineers"? It didn't last very long.
Judging by the examples you gave, I suspect that your positive experience is mostly with small(ish) greenfield projects (which we know AI excels at), whereas parent is most likely employing agents in a large codebase with lot of preexisting architectural commitments.
> whereas parent is most likely employing agents in a large codebase with lot of preexisting architectural commitments.
From this?
>> I have to beat the GPT and Claude models over the head with a brick every ten seconds for it to even partially code or design as well as me. Despite precise and generous specification, they frequently make horrible architectural decisions.
>> When I read claims like yours, I want to withhold judgement and understand, because it 100% does not line up with my experience and my gut reaction is to question your own capability to either write, read or understand quality code. I code all day long with AI models but it's an extremely frustrating experience at times. And don't even get me started on all the annoying meta behavior outside of coding, such as Sol's obsession with "tests" or competing for world's busiest-yet-least-functional UI
That doesn't follow at all.
Perhaps I should have expanded, since putting a number of examples doesn't tell people how large those codebases are. It's true that some of them are greenfield, but some are coded within large codebases that existed before LLMs arrived. You're also dismissing the smaller projects as if it's a given that LLMs should work for those.
What I'm finding interesting is there seem to be disconnected camps of people who either can get it to work, or not. People seem to have either integrated the LLMs into their daily coding, big or small, and then there's people giving shallow dismissals of its efficacy.
The user you are replying to is completely correct. I am discussing load-bearing codebases with real users and real consequences and architectural commitments, not hobby projects for my friends and I, or "massively" multiplayer online games that I probably haven't actually properly benchmarked for being truly massively multiplayer at scale.
You listed some really cool projects and you're exactly the kind of person I think of when I think of a bright future empowered by AI, where developers still have fun making cool things and technology enhances our lives at the snap of a finger, so I don't mean anything negatively.
You might have a great eye for architecture and foresight for keeping bugs and complexity at a minimum, and might just have a good amount of free time, motivation and creativity. I'm not calling any of that into question, true or not. But I really was discussing a different kind of work, more mission-critical or performance-critical stuff which I work on both professionally and in my free time.
I've also cooked up some really fun little games and apps this year and we'd probably have fun using each other's tools, and little usability complaints could be dealt with quickly. But I wouldn't consider most of those polished, bug-free, safe to use, or even finished. So what you're saying does have merit, I was just discussing a different class of work. And I also recognize that AI is rapidly getting better and in a few years, many of our current concerns might no longer be relevant for a number of reasons.
Yes, but I also have two decades of experience writing substantial code for commercial organizations, writing mission-critical and performance critical code. I've got plenty of contacts in a similar situation.
When I talk to those contacts, they are not so dismissive. They don't think that the AI is making lots of mistakes, despite working on massive code bases that are old and complicated.
AI can actually be a godsend for old, complicated codebases and greatly increase velocity there, and existing architecture can help to guide them. My problem is that the 6-series was a major step backwards and I am back to arguing with these models instead of just working with them. They are really bad at adherence.
Anyway, I'd categorize my feelings not as dismissive, but frustrated. OP said their models code just as well as them, and while there are many parts of my work I'm increasingly deferring to AI, actual programming and architectural design are still lacking heavily for me.
I can trust my AI to research and suggest solutions I'd never even considered. I can't trust it to say, "Finished," not even just because there may be bugs, but because many systems will often be categorically missing, mocked, stubbed, TK'd, etc. or it will invent and bake in bad assumptions we'd never discussed. And I can't trust it to adhere to best practices. This is fine, I can review the code and iterate, but there are some things I still just find these models cannot get a grip on at all.
Smallish greenfield projects where op clearly doesn’t look at the code closely either but only evaluates happy paths of the resulting behavior. Godspeed to op.
In an important way bridges and buildings are indeed proven to be sound by applying the mathematical tools of structural engineering, materials science, etc. Software Engineering also has analogous formal tools at its disposal (Lean is one gaining a lot of exposure these days), but many were being neglected because it wasn't worth the bother. In this new adversarial world, we'll be forced to reach for them more often. Luckily the models are also a big help in making these tools more approachable.
This is a terrible article, both poorly argued and ideologically biased. The other story presented, about a peasant named Peter Stubbe who turns into a werewolf undermines its central premise, tying the phenomenon of imagined werewolfs to certain feminist ideas, or at least shows them to not be gender-specific in any meaningful way. Peter was said to have especially preyed on women. He was a "bad guy" in the same way that the she-werewolves were "bad girls". Plus it's his story which includes, as presented, accusations of sexual (shall we say) misbehaviour, so whence the conclusion at the end?...
The most powerful people in silicon valley are openly aiming to replace the entire species with robots in space. This is their genocidal aim. The fact that bad things haven't happened yet doesn't mean that directionally, they aren't attempting to replace as much human culture as possible.
It sounds silly! That's because they are completely divorced from the human experience, and they have enough power to really make us all suffer.
But those other ones at least have the room to potentially do that, even if most won't. So what GP is saying is that this is a magical stock indeed, but the other way around, in that it's magically capped.
"Incoherent" has a static connotation, "decoherent" OTOH is dynamic and has an associated verb, which is very handy when describing a gradual process which (almost) inevitably occurs as features are added to a system. Since confusion with the usage from quantum physics is unlikely, I too think we can safely and fittingly overload the term like the article does.
Yes, this is the thinking behind using the term. It’s also different from incoherence because decoherent systems can still make sense in some ways. They still work, they can still be iterated upon.
They are decoherent because the work to change them is extremely difficult. This is a different, and much more costly, state to exist within.
reply