How to achieve reusability with React components

Five years out, curious if this is still being used. Search results show goose eggs for walmart archetypes for the past year.

For people who say working at Walmart isn’t a good job

very nice, we are transiting from monolithic to component driven development for existing products. Got a question, are you using managed CI/CD tools/pipelines? or self-hosted? Would also like to know rational on your decision. Super thanks and stay awesome

Brilliant! Business wants reusability/efficiency across the organization. This is a great goal, but I think you hit the nail on the head. It's not just a technical challenge but a philosophical change which requires organizational commitment. Not only is this change philosophical in nature, it's a fundamental cultural shift. Very difficult to change/align different cultures across different departments/silos, in effort to create efficiencies. It seems you've done an excellent job and I'm glad I ran across this video you've put together. Much thanks!

glad to hear insight from this philosophy. But I want to hear the statistics on how much time are these "Meta meetings" are consuming in the dev workflow. I want to know the insight of how cost-effective this philosophy is compared on just letting each organization use the framework they decided, avoiding these seemingly unnecessary workflow. Letting each organization just use and code on however and whichever they want breeds innovation.

If the concept they want is "to make everyone stay on the same platform," then I think that they should had built a first class API or an SDK, instead of a reusable components. This still keeps all the organization on the same page, and let each organization choose which JS library or frontend tools they should use. That challenge he discussed at the end about innovation is not actually a "challenge" but the main limitation of this philosophy. This philosophy will just be breeding legacy software nobody wants to use. I also want to hear the insight of the developers working on this workflow, are they feeling innovative? or they think they are stuck on a system they can't use in the future.

Nice speech