Codeboot

  Teaching Smart People How to Learn by Chris Argyris From the Magazine (May–June 1991)     Any company that aspires to succeed in the tougher business environment of the 1990s must first resolve a basic dilemma: success in the marketplace increasingly depends on learning, yet most people don’t know how to learn. What’s more, those members of the organization that many assume to be the best at learning are, in fact, not very good at it. I am talking about the well-educated, high-powered, high-commitment professionals who occupy key leadership positions in the modern corporation. Most companies not only have tremendous difficulty addressing this learning dilemma; they aren’t even aware that it exists. The reason: they misunderstand what learning is and how to bring it about. As a result, they tend to make two mistakes in their efforts to become a learning organizatio

 12 Factors of a Scalable Microservice . I. Codebase One codebase tracked in revision control, many deploys A twelve-factor app is always tracked in a version control system, such as Git , Mercurial , or Subversion . A copy of the revision tracking database is known as a code repository , often shortened to code repo or just repo . A codebase is any single repo (in a centralized revision control system like Subversion), or any set of repos who share a root commit (in a decentralized revision control system like Git). There is always a one-to-one correlation between the codebase and the app: If there are multiple codebases, it’s not an app – it’s a distributed system. Each component in a distributed system is an app, and each can individually comply with twelve-factor. Multiple apps sharing the same code is a violation of twelve-factor. The solution here is to factor shared code into libraries which can be included through the dependency manager . There is