Who maintains the skill layer?

Adrian Brudaru discusses the evolving landscape of software development in the context of Large Language Models (LLMs) and the implications for skill maintenance. As LLMs enable even those with minimal coding experience to create functional software, there is a growing divide between merely producing code and the deeper engineering required for robust, maintainable systems. The article emphasizes the importance of maintaining the senior craft, which includes handling dependencies, credentials, and iterative improvements—a focus that is often missing in the current narrative centered around the novelty of LLM-generated code. Skills that wrap software are akin to traditional scripts but require rigorous lifecycle management to ensure they adapt to library updates and maintain functionality. The responsibility of maintaining these skills is divided between vendors, who manage the product surface, and users, who customize integrations to fit their environments. This dynamic underlines the necessity for developers to focus on unique business logic rather than duplicating vendor-maintained functionalities, akin to avoiding the maintenance of a divergent library fork.