2 ms·
Let's say you offer a custom built UX design system with components. Most of it is written. At some point, you need a big component that doesn't exist yet, but
by koonsolo 3y ago
Let's say you offer a custom built UX design system with components. Most of it is written. At some point, you need a big component that doesn't exist yet, but other teams could benefit from that.
This is such a situation, and it happens all the time in internal products.
Either you over invest, you under invest, or the solution proposed here: jit developments where you can allocate resources as you need them.
> These developers don’t really care about the platform
They care as much as it helps them. The overall vision is steered by the architect responible for that internal product/platform, as said by OP.
- CraigJPerry 3y ago>> jit developments where you can allocate resources as you need them Again there’s just no free lunch here, you’ve got a generalist writing a specialist component. In your example, how confident are you that the full stack product team developer is acutely aware of, i don’t know , let’s say accessibility practices or maybe performance tradeoffs for constructing this component? The specialist in the platform team member knows this intimately, it’s their specialism.
- koonsolo 3y agoYou discuss the developments with the architect before development, and then have your code reviewed afterwards. But hey, if you want some experts to sit idle until some real work comes in, that's all fine by me.