| > The difference is that it's actually working this time. Non-programmers are writing full apps You can say this about every step along the way. C programmers replaced assembly programmers. Python programmers replaced C programmers. low code tools replaced interal tools teams. > I'm criticizing you for misrepresenting what claim was made in the first place. No where in your evidence have you shown anyone "walking the claim back". The claim is that SWES will have their work done by models in 6-12 motnhs. We are _nowhere near_ that 9 months on to it. That's all there is to say it. > If anything, TFA is claiming evidence of an LLM doing "most" of what SWEs do "end to end" three months ahead of schedule. TFA based on a model that is so good that it has to be kept from us? from the company that literally can't keep their app up? From the company who shipped an update that didn't launch? > be my guess, but don't tell falsehoods about the evidence you are presenting. I mean, I literally posted a quote from the CEO of one of the two major companies saying that SWEs are 6-12 months away from being replaced. This is fantasy talk from a guy who is incentivised to have you believe this. If the claims are that software is changing, and how we're building/deploying software is adapting to that new world then yeah that's fair enough. But the current models, harnesses and tooling are not replacing an SWE unless there's a paradigm shift in the next 3 months. And my point is that we appear t be going backwards, not forwards. > didn't make GLP1s fake just because they had the same type of hype. No, GLPs work and that's the difference. |
Even ignoring the other ways you're misrepresenting the, there's a huge difference between "might be" and "are going to be".
I'm sorry if English isn't your first language, but we're going to have to agree on basic grammar or else it's not going to be productive for me to continue responding to the flaws in your argument.