TL;DR: We wanted a new look and feel for our Component Dashboard. So, instead of tons of PRs getting rejected, we let our UI Design and Product team build it for us with AI in an isolated Myop component. As devs, we made sure the props and architecture for data flow was pristine and just handed them the reins to build the component itself.
In the first part of this series, we discussed the gatekeeping dilemma for devs and how non-devs have access to code already. And we went through the better approach devs should take to democratize code but with good governance. So how do we actually implement that and what does it mean for you the developer?
In my previous blog post on this topic, I wrote in short about this. In short, constant UI change requests disrupt front-end developers' focus and slow overall progress.