With Microsoft's Copilot Code letting any employee build governed apps, I'm wondering if I can still be competitive with this activity.
I don't really get either how is microsoft gonna unsure long-term maintenance. Unlike low-code Power Apps, these are real code apps with dependencies that age. Who updates them, fixes them when a dependency breaks, or takes over when the person who built the app leaves ?
If anyone has an input on this I would gladly hear it.
bemeeker•51m ago
When someone at a company builds an app, they become the owner/maintainer of that app, and it can be transferred to someone else when leaving, or to a group/team for shared ownership. Or, it can just be decommissioned.
I think it’s important to treat internal tools built by non-technical employees essentially as drive data. It should be shared with those who need it, and if it needs to be kept forever, it should be owned by a group or “shared drive”.
With that said, I also think that as a developer building internal tools, you fall into a bit of a different bucket. When contracting with these companies, I imagine the expectation is that you will build something high quality and maintainable, which can be passed off to a platform team. This is functionally different from non-technical users building their own tools.