cole murray

having a centralized skill repo in the company solves a lot of otherwise annoying problems: - visibility on which skills are actually being used, in which use cases - duplication / needing to copy same skills into a repo - allows non-technicals to use and create - version control - eval the skills the common approach to this is to throw everything into a shared GitHub repo, butit creates a poor user experience and misses a lot of the observability benefits

12,348 görüntüleme