"Im not even sure we will need maintain software" (sic) - I'm not sure what your specific background is, but with a statement like that you lose all legitimacy to me.
Yes, I'd like to hear more of their background, because they seem very naive about writing software, adding to it, testing it, etc.
You can't just whip up a replacement for salesforce using claude code. Who's going to fix the bugs, who is going to have tests, manage performance testing? People will still pay for software that is tested and performant. I could get a replacement for an online spreadsheet, google docs like thing. Suppose you tell it to copy the google docs or whatever programming language. You won't know if it's buggy because you won't haev the same test coverage. You'll never know about bugs that took a long time to reveal in some combination of features.
You can create a new system with a few features together to do something. Again, not tested, not perf tested, isn't away of a compiler bug you had to work around.
But lots of simple things can be claude coded and replaced. Say something that took a photo of a person, centered it, then say put some kind of log on the pic. Something you paid $5 a month to do.
Writings on the wall, it is true, tech debt will no longer be a thing to care about.
"but who will maintain it?" massive massive question, rapidly becoming completely irrelevant
"but who will review it?" humans sure, with the assistance of ai, writing is also on the wall: AI will soon become more adept at code review than any human
I can understand "losing all legitimacy" being a thing, but to me that is an obvious knee jerk reaction to someone who is not quite understanding how this trend curve is going.
And the human downstream of this random reorganization of things at will, how do they manage it?
If its AI agents all the way down its commoditization all the way down, if humans have to deal with it there's some sort of cost for change even if its 0 for code.
Agile hasn't been insisting that specs are impossible to get from a customer. They have been insisting that getting specs from a customer is best performed as a dynamic process. In my opinion, that's one of agile's most significant contributions. It lines up with a learning process that doesn't assume the programmer or the customer knows the best course ahead of time.
I have found that it works well as an open-endlessly dynamic process when you are doing the kind of work that the people who came up with Scrum did as their bread and butter: limited-term contract jobs that were small enough to be handled by a single pizza-sized team and whose design challenges mostly don’t stray too far outside the Cynefn clear domain.
The less any of those applies, the more costly it is to figure it out as you go along, because accounting for design changes can become something of a game of crack the whip. Iterative design is still important under such circumstances, but it may need to be a more thoughtful form of iteration that’s actively mindful about which kinds of design decisions should be front-loaded and which ones can be delayed.
You definitely need limits around it. Especially as a consulting team. It's not for open ended projects, and if you use it for open ended projects as a consultant you're in for a world of hurt. On the consultant side, hard scope limits are a must.
And I completely agree that requirement proximity estimation is a critical skill. I do think estimation of requirement proximity is a much easier task than time estimates.
And good luck when getting misaligned specs (communication issues customer side, docs that are not aligned with the product,...). Drafting specs and investigating failure will require both a diplomat hat and a detective hat. Maybe with the developer hat, we will get DDD being meaningful again.
The point is, the name of the DoD is still the Department of Defense. Just like his dumb ass calling the Gulf of Mexico the Gulf of America didn't change the fact that it's still the Gulf of Mexico. All it meant is him wasting money on new letterhead to sooth his fragile ego.
He can make the executive branch call it The Dumpty Bowl if he wants. That doesn't mean he has renamed it. He has zero power outside the executive branch. Fortunately the United States isn't yet ruled by decree.
The names are decided by the United States Board on Geographic Names, which is under the Department of the Interior, which is part of the executive branch. So yeah, he can make them rename it for the US. Sure, you can pedantically say that he can only force the entirety of the federal government to respect the name, and the State governments could refuse to abide by that, but what would be the point? AFAIK none have outright refused. And obviously private citizens can call things whatever the heck they want, though if they get too creative they may have trouble expressing themselves in a way that others will understand.
The point is accuracy. He literally can only mandate the federal government. Everyone else knows it's the Gulf of Mexico in every state in the US and every English speaking country in the world.
I haven't heard of any states bothering to reprint maps. They all know his whole clown show charade will be over in the blink of an eye.
You could pretend he has more power than he does, but what would be the point?
Exactly representative of the single anecdotal examples designed to equate all immigrants to criminally illegal villains. You may have a point if this was the typical example of the kind of people Dumpty is rounding up. But they are pulling people from their immigration hearings. You know, the ones "doing it the right way" they promised wouldn't be rounded up. That is the majority of people being rounded up in Dumpty's domestic immigration attack.
The collapse happened when we elected a power drunk fool with a Project 2025 playbook to completely strip the separation of powers in favor of the Executive branch.
Now the war fool is trying to start as many conflicts as possible inside and outside the US to distract from his disturbingly heavy Epstein involvement to give him an excuse to take over polling sites in the US. No more wars my rear.
We have a chance to recover in the November elections by voting out his puppets and tools in congress. The question is whether or not we will take it.
Current LLMs are nowhere near qualified to be autonomous without a human in the loop. They just aren't rigorous enough. Especially the "scientist throwing a swarm to deal with common ML exploratory tasks." The judgement of most steps in the exploratory task require human feedback based on the domain of study.
> Many of the recommendations will feel too much or too little complexity for what people need and the fundamentals get lost: intent for design, control, the ability to collaborate if necessary, fast iteration due to an easy feedback loop.
Completely agreed. This is because LLMs are atrocious at judgement and guiding the sequence of exploration is critically dependent on judgement.
Most places that ask for a phone number refuse to accept Google Voice or Twilio phone numbers. It's specifically to guarantee you have a cell-phone assigned number. Can anyone confirm whether Anthropic allows Google Voice or Twilio numbers?
reply