I mean, this was the whole promise of vibe coding. Is it just creating more issues?
caleb-bb
Zurga
Well yeah, because if you have a department that needs to deliver some form of standardized output to the outside world (like citizens or customers), it is not desireable for everyone to create their own IT system or part of it. There needs to be some standardization to allow for inter-colleague, inter-departmental collaboration/communication.
If you have some unaudited program that was vibcoded interact with an exchange server and it starts sending emails that make no sense, that is bad. If you have PII data that gets exfiltrated by accident or on purpose to an external service, that is also bad. If multiple employees need to collaborate on a dossier and each has their own bespoke software suite this will just create chaos. I could go on, but I think you get the point.
Mind you, if you work in government and handle sensitive information you are not allowed to use that information in a prompt to an LLM for example. Should you do so, that data is now considered to be in the LLM vendor and you have a privacy issue.
dkx
This is very relatable. Plenty of vibecoding initiatives in public administration right now. For some reason, almost none of the initiatives seem to involve developers or technicians… Then when you really dig into it, 95% of the ideas and needs that come up are just dashboards that would be perfectly covered by a BI system like Superset - no need for the vibecoding can of worms.