Wow what an opener comment thread. One thing is for sure, this is a very contentious topic lol. I have had this opinion since way before this ai boom; someone who pushes code to prod is responsible for what happens in prod with that code. This blogpost is very relatable
Is your llm force pushing to main? If so, why are you allowing that?
No LLM will destroy any code base in any time frame without permission from an human operator. That person is responsible for allowing the code base being destroyed.
My manager expects stuff to be done 10 times quicker than 2 years ago, and that can't happen if I spend time understanding and fixing all code being pushed. At that point I might as well write it myself.
That’s a you problem, not the AI. Stand up to your manager and explain to them how the situation is their fault. Or take responsibility for your complicity from not quitting. But don’t blame the AI for process failures that it did not impose on you.
No, it doesn't. Nobody would go do this just to report it to Sony for a few pennies. That is a non-existent motivation for people in the know, who understand the opportunity cost.
Sounds like the same issue as with Mastodon. The vast majority of people are not interested in a 'protocol' (or even know what that is), they do not care what protocol powers their _app_, they just care about their app
Because it makes them money and for some reason people (and governments) have accepted their lie that they can't police this.
Comparison to the olden days; if a paper magazine knowingly allowed scammers to advertise they 110% would've been prosecuted. It is really weird that we let google (and others suchs as meta!) get away with this.
Some comments make it seem like this is a new thing, it's not, this has been going on for at least 10 years now.
Over the past 3 months we've been using it a LOT. I made one for our admins so they can work with the CMS and get statistics in their client, the statistics part has been a huge unlock. The big advantage here is that a normal API, direct tool integration or CLI are unpractical to set up for my less technical coworkers.
Other then that I've been building MCP's in pretty much all (personal) tools I'm making now, it's very useful to have a central way for an agent to look at production data without having to ssh into a server.
reply