[–] LeFantome 1 day ago
[–] simonask 1 day ago
It’ll still take weeks with AI in the picture, but for some reason management is more willing to plan it when they also have the additional token bills to pay.
[–] 1123581321 1 day ago
Now, you can make enough progress with one developer’s quiet afternoon to be confident and finishing the work also takes less time.
The technical grasp of the legacy codebase was a factor, but often not the largest.
[–] sick_of_slop 1 day ago
I despise AI but the thought of doing something the “old way” just makes me wince at how long it would take me to do anything that would take minutes with agents that I despise.
I touch grass whenever I can now.
[–] llama_drama 1 day ago
[–] brabel 21 hours ago
[–] vtjeng 1 day ago
[–] sgt101 19 hours ago
But its a lot less effort that when we didn't have LLM's.
Interestingly it does seem that it's still enough effort to prevent most folks from making that step though.
[–] erikus 1 day ago
[–] wolfinterval 19 hours ago
More and more, I am using half finished as a polished product, but pragmatically very useful software I have built myself.
More importantly, I see no reason to polish this into a product. It is more useful in this half finished, easily moldable state.
Like it use to make sense to bake the clay and sell the hardened output but now I want to keep the soft clay so it can be molded to my changing needs. I keep adding to a collection of these moldable states.
[–] jack_pp 1 day ago
[–] sodapopcan 1 day ago
[–] furyofantares 1 day ago
I mean, I have finished more side projects than before. So they do change it. Just not as dramatically.
[–] anonymous908213 1 day ago
[–] StilesCrisis 1 day ago
[–] brabel 21 hours ago
[–] anonymous908213 1 day ago
We would be using LLM-generated compilers, an LLM-generated OS, an LLM-generated browser, LLM-generated databases, etc. etc. etc. etc, and not only are we not using all of those things, we're not using a single one of those things. Nobody is buying LLM-generated games, nobody is using LLM-generated consumer applications that replace Photoshop or Final Cut or Blender or Unity ("PhotoCraft" is itself an admitted scam from its own prompter, who outright confessed here that he lied about its capabilities on Reddit to build hype), nobody is accomplishing anything of economic value. LLMs are obviously hundreds of times more "productive" than humans, so the moment they can reach 100, all of these things would happen basically overnight, and yet none of them have happened. Curious, isn't it?
[–] StilesCrisis 1 day ago
[–] anonymous908213 1 day ago
> how PostgreSQL is having dozens of bugs discovered and fixed via LLMs
The PostgreSQL article was specifically about how the LLMs were incapable of fixing bugs, meaning they had to delay their next major version because humans were unable to deal with the volume of issues reported. I did not make a claim that LLMs are useless, could not help review code, etc, but there is a difference between a useful tool and something that generates production-ready software wholesale.
This is what "100" looks like if you try to generate a DB from scratch: https://jepsen.io/analyses/particledb-1.1.4 - written in Rust, ""formally verified"", scammed AI-pilled investors out of $90 million for a database that fundamentally doesn't work in any capacity whatsoever.
[–] drivebyhooting 1 day ago
You have the perfect verifier.
[–] anonymous908213 1 day ago
[–] ChickeNES 22 hours ago
Speak for yourself :)
[–] jopsen 1 day ago
At work, they mostly let me increase quality, because it's easy to say find all parsers in my code base and fuzz them.
[–] switchbak 1 day ago
Of course, you can make a giant pile of doggy-doo-doo, but that was always true, just you can now make an epic Giza-sized pile.
[–] Seattle3503 1 day ago
Yeah but were more likely to learn how bad your code was in the process. I see people oblivious to their slop putting pressure on others to merge it.
The other place they are amazing is in working with legacy code bases. I mean, the kind the dev team always wants to throw away. First, even if you do want to throw it away, you can first find out what it does and realize it does more than you think it does. You can also create integrations to more modern components which can be used to extend it. You can also create a pretty decent test suite if you do not have one. And, once the behaviour has good test coverage, you can re-write it into something more modern. You can even completely change the architecture while ensuring compatible external behaviour. Remember, this is all in place of “throw it away and start over from scratch, only to discover that the scope is much larger than expected”.