4,851 karma · joined April 28, 2009
[ my public key: https://keybase.io/cmiles74; my proof: https://keybase.io/cmiles74/sigs/vgamM-P-kP6khsKwIPdnT2ZwFYhbUi4VCPNyLF3rJYk ]
IMHO, at the end of the day it's been about the same amount of time, the cost is a little higher and I don't feel as confident in the end product. I suspect that I am not the only one that feels this way!
Does Cursor have some process that just scrapes Microsoft’s extension catalog and lists them in their own? If that’s hostile works then it’s broken and needs to be fixed.
Indeed, we have seen many instances of software that are well regarded as being works of art. Is the source code for that software somehow not art?
My distaste for vibe coded apps aside, I wish them the best of luck.
IMHO, I haven’t been super impressed with the security measures I’ve had to work with. Often they are simplistic and bolted on at the very end. If it comes to light that this is the attitude OpenAI has been taking, I would not be surprised.
On the risk management angle, for sure it’s a spectrum. I don’t agree that the far end of the safe side of that spectrum for AI models is “entirely safe and entirely useless”, there is a lot of work you can do with a model that has zero risk of hurting anyone (aside from your wallet). If someone chooses a more dangerous spot on that spectrum, I believe they should be held responsible.
> An AI given the same exact instructions and tools can go and complete a task you wanted it to. Or it can get sidetracked into breaking out of your sandbox and hacking Pentagon. No way to know in advance.
This has not been my experience. I’ve been getting a lot of good work done and, as of today, have been involved in zero Pentagon hacking incidents. ;-)
This all seems like a way to try to avoid taking responsibility for the model’s actions. Someone puts the tools in place, someone provides the instruction and, sometimes, someone decides not to monitor the model’s output.
IMHO, if the model breaks a law, apply the law to the operator.
Maybe LLM tooling can help people demystify some of that. I think that would be a good thing.
In my experience, LLM tools are not infallible and I've seen them introduce changes in one place that causes defects in two or three other places. They write code that I find difficult to read and that can make diagnosing these bugs harder than it needs to be. People have brought me code that LLM tools have written because they are surprised that it doesn't work and are wondering if somehow they, the human, just doesn't understand something.
Maybe this is just another bump and these tools will continue to improve. Until these things aren't a problem. As it stands today, I think there's still a place for a people in commercial software development.