I have a confession to make. In the past several years I've implemented 'DevOps' automation tools for a number of startup companies without having a clue what their business was about. That's more than a little scary when you think about it.
Should we use a single GitHub repository for Chef cookbooks? Or one GitHub repository per cookbook? Why choose one or the other approach in a give situation? What are the potential benefits and tradeoffs? Does anybody really know? Are we over-thinking this issue? Maybe we all should take a deep breath, tear our hair out, throw Chef under the bus and just write fu#king shell scripts!
Speaking simplistically, organizations tend to move towards DevOps in either of two ways...
Job titles are important because they describe what we do, which shapes our identity and guides our activity. It's important that job titles are rational and make sense. If they don't, it causes confusion and stress for individuals, teams, and organizations.
We built Bitlancer Strings originally to run on Rackspace Cloud. While we can support customers running in other cloud environments, Strings is more ideal for a persistent environment like Rackspace.