zlacker

>>deofoo+(OP)
Good, I will with great pleasure now reiterate my point about people now producing their own code, even complex stuff, rather than downloading potentially malicious and foreign code. Which as a tendency threatens ALL clumsy big ERP service providers selling you SAAS.

Go ahead - I'm ready to be down-voted again and again until folks realize it is inevitable, as is inevitable that many companies in the area of business software are going down down down.

>>larodi+eX8
I'm the main dev in a small IT company, my backlog is filled with requests, it's not always easy to prioritize and plan, some of those small projects are ignored for months, yet their business value are sound.

I've observed a new trend, managers who are frequently in the wait list started to use AI to generate small local apps. They still rely on my input when it's complex, or when implementation could generate risks or need resilience and would ask for small code reviews when they are unsure of the generated code quality.

The result is win win, I have more time for high value projects the executives want to prioritize, and managers can innovate faster almost on their own.

>>nkapia+9y9
I have started to notice some similarities to MS Access development, where an SME creates a useful app for themselves and begins to share it.

I wonder if it will have a similar pattern of creating a mess as the app starts to get uptake and the SME can't scale their attention to be an app owner, as well as an SME at the same time.

Also makes me think that an llm-developed-app-friendly shared datastore would be a useful thing to have

>>monkno+ULa
I like your 'llm-developped-app-friendly shared datastore' idea and would pursue it.

While taking ownership of AI slop is not an option for me, I do want to avoid shadow IT.

Might be a moon shot .. could sharing a prompt template with git access to colleagues be a way to enforce it ?