<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Shelton Davis on Medium]]></title>
        <description><![CDATA[Stories by Shelton Davis on Medium]]></description>
        <link>https://medium.com/@sheltondavis?source=rss-32ac24ff136f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zpCR6MgsDdWcYWcX.jpeg</url>
            <title>Stories by Shelton Davis on Medium</title>
            <link>https://medium.com/@sheltondavis?source=rss-32ac24ff136f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:01:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sheltondavis/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Personal Reflection: MLK Day, 2018]]></title>
            <link>https://medium.com/@sheltondavis/personal-reflection-mlk-day-2018-ebc35048f4c1?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebc35048f4c1</guid>
            <category><![CDATA[martin-luther-king]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Tue, 16 Jan 2018 11:42:04 GMT</pubDate>
            <atom:updated>2018-01-17T18:53:57.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qgum0T-kanpZJDqMJr6ruA.jpeg" /><figcaption>A visit to Dr. Martin Luther King and Loretta Scott King’s resting place in Atlanta, GA.</figcaption></figure><p>I took yesterday off, Monday, January 15th 2018, in order to observe Dr. Martin Luther King’s birthday. It is the first of many days that will shape the way I think, the way I interact, and the way I am confidently driven to lift up those around me. Yes, my day wasn’t all dedicated to service as I found myself on a roller rink for a 7 year old’s birthday party and at the grocery story getting the week’s fill. Life continues, but a quote from MLK struck me today more than many others.</p><p>“It may well be that we will have to repent in this generation. Not merely for the vitriolic words and the violent actions of the bad people, but for the appalling silence and indifference of the good people who sit around and say, “Wait on time.”</p><p>I’ve heard myself say things like, “Wait on time” and be patient. Patience is a virtue if and only if it is part of directed action. I am now going to check myself hourly to make sure that my silence isn’t a reflection of the fear that is creeps around inside me. I am going to take action with family and take action with friends to lift up an agenda focused on human interaction, inclusion, and social investment.</p><p>Thanks for listening. How can I help you? What social causes are you a part of that I can encourage your continued action?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebc35048f4c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing Cog 1.0]]></title>
            <link>https://medium.com/operable-news/announcing-cog-1-0-c460a4612b5f?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/c460a4612b5f</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cog]]></category>
            <category><![CDATA[releases]]></category>
            <category><![CDATA[chatops]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Thu, 23 Feb 2017 19:50:10 GMT</pubDate>
            <atom:updated>2017-02-23T20:27:48.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*luGqvNXq16xcI6tpjwFpPw.png" /></figure><p>It’s been a long journey, but we’re very happy to announce the release of <a href="https://github.com/operable/cog">Cog 1.0</a>! Relative to previous beta releases, this release is mostly a lot of bug fixes, though we did manage to squeeze in a few new features, like support for Slack’s new <a href="https://slackhq.com/threaded-messaging-comes-to-slack-417ffba054bd#.a4vq9yjvo">Threads</a> feature, as well as a completely rewrittencogctl command line tool! As always, details are in the <a href="https://github.com/operable/cog/blob/df995417850a53602b88bdcff5b7cb5396e277ad/CHANGELOG.md">changelog</a>.</p><p>Everyone here at Operable would like to thank the members of our great community that have helped to make Cog what it is.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c460a4612b5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/operable-news/announcing-cog-1-0-c460a4612b5f">Announcing Cog 1.0</a> was originally published in <a href="https://medium.com/operable-news">Operable News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scared progression into the new]]></title>
            <link>https://medium.com/@sheltondavis/scared-progression-into-the-new-a33fb50ac439?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a33fb50ac439</guid>
            <category><![CDATA[daily-questions]]></category>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[progress]]></category>
            <category><![CDATA[poem]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Tue, 21 Feb 2017 04:28:59 GMT</pubDate>
            <atom:updated>2017-02-21T04:28:59.937Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5QF8U6zoSMy8TSjHPncddA.png" /><figcaption>QDQD — Quick Daily Question Delivery</figcaption></figure><p>Last night’s thought after reading Shel Silverstein’s “Missing Piece Meets the Big O”. I was in a rhyming mood, so bear with me.</p><blockquote>Day in day out, ideas pour from my head,<br>So many things to explore before I drop dead.<br>My to-do list is like yours, extensive yet incomplete,<br>I check one thing off, add four more, zero inbox is quite a feat.<br>The thing that scares me most can make an above average wave,<br>I must lead with my heart, lean forward, and be brave.</blockquote><blockquote>-Shelton</blockquote><h3><strong>Here is me being brave.</strong></h3><p>For the past 50 days, I’ve asked myself and friends a single question a day. I’ve learned a LOT about myself and those around me through a focus on this singular task. With a day full of distractions, it’s nice to talk about something like question #5, <a href="https://qdqd.me/2017/01/05/question-5-bows-and-arrows/">Bows and Arrows</a> or question #39, <a href="https://qdqd.me/2017/02/08/question-39-excavator/">Excavators</a> (#39 was influenced by my son).</p><p>This is where the rubber meets the road and the nervous sweats begin. These daily questions are meant to be asked to more than just those in my personal bubble. Because of this, I’ve built a framework around this thing I call <a href="https://qdqd.me/"><strong>qdqd</strong></a> which stands for <strong>Quick Daily Question Delivery</strong>. By design, I want to give as many people as possible one simple question each day to ponder, answer, and ask each other. I want to help spur conversations, I want to help build understanding, and ultimately, I want to add to our collective empathy. We’ve got a lot to share.</p><h3>Join me and qdqd:</h3><ul><li>Answer questions with me and become an active Contributor through <a href="https://www.patreon.com/qdqd">Patreon</a> (exclusive access to the compiled daily answers)</li><li>Follow qdqd on <a href="https://twitter.com/qdqdme">Twitter</a> / <a href="https://qdqd.me/">Blog</a> / <a href="https://www.facebook.com/qdqdme">Facebook</a>. (You can answer questions there too, but I am only able to tally answers and create responses for the trackable Contributors)</li><li><a href="http://eepurl.com/cC2M4j">Sign Up</a> to get monthly email updates on qdqd</li></ul><p>High fives and hugs when I see you next.</p><p>-Shelton</p><p><em>Originally published at </em><a href="http://sheltondavis.com/"><em>sheltondavis.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a33fb50ac439" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Interview #8: Community Collaboration with Agis (Skroutz)]]></title>
            <link>https://medium.com/operable-news/quick-interview-8-community-collaboration-with-agis-skroutz-b40811226a7e?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b40811226a7e</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[chatops]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Wed, 08 Feb 2017 17:37:00 GMT</pubDate>
            <atom:updated>2017-02-13T15:43:24.034Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0N3Vh0oH4Yynz-54YwVt5g.jpeg" /></figure><p>Thank you Cog’s community! Thank you for committing issues to <a href="http://bit.ly/2lo3nzQ">Cog</a>, making suggestions, asking hard questions, and just following along. If you are in our public Cog Slack community, high fives to you. Feel devoid of high fives and ChatOps in your life? Come <a href="http://slack.operable.io/">join us on Slack</a> and the Operable team + Cog community will virtually slap hands with you through chat, promise!</p><blockquote>Feature-wise, we loved that anyone is able to write their commands in a language of their choice. We also liked that we could compose commands together to solve more complex problems (ie. Pipelines).</blockquote><p>Speaking of Cog’s wonderful community members, <a href="https://medium.com/u/92f3835c13a8">Agis Anastasopoulos</a> has been using Cog for quite some time now. He and his engineering team at <a href="https://www.scrooge.co.uk/">Skroutz</a> expanded Cog’s Ruby capabilities and created <a href="https://github.com/skroutz/cogy">Cogy</a> based on internal needs, how their app was built, and user experience goals. Without stealing anymore thunder, here is my interview with Agis.</p><h4><strong>What’s your name, title, and role at Skroutz?</strong></h4><p>Hello, I’m Agis. I’m an engineer at <a href="https://www.scrooge.co.uk/">Skroutz</a> and I’m leading the Architecture team. In a nutshell, we build and maintain our application-level infrastructure. This includes anything from our <a href="https://engineering.skroutz.gr/blog/optimizing-continuous-integration-at-skroutz/">CI server</a> to making sure developers have the right tools at their disposal in order to work efficiently.</p><h4><strong>What role does ChatOps play with Skroutz?</strong></h4><p>Currently, we use ChatOps mostly as an additional convenient interface to our internal or external services. For example:</p><pre>whois</pre><p>This command returns contact information about a particular co-worker by querying our LDAP server:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*MQ7cLGJYnY46S-qM." /></figure><p>Another one displays graphs from our <a href="http://grafana.org/">Grafana</a> dashboards:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JoLMjaemSIDFKyor." /></figure><p>Our ChatOps commands are targeted at every member of the organization, engineers or not. This means we try to make them as user-friendly as possible (eg. we try to avoid options and make heavy use of aliases), even for non-tech savvy users. That’s a reason for changes like “<a href="https://github.com/operable/cog/issues/1142">Customizable error template</a>” being important to us.</p><h4><strong>Why did you pick Cog vs the other bots?</strong></h4><p>We decided to spend two months before coming down to a ChatOps solution and implementing it. After the initial stage of researching and evaluating the available choices, we concluded that Cog was the most promising choice in the long run. We liked the vision of the Operable team and the fact that they’re devoted to taking ChatOps to the next level. We instinctively felt that Cog was the way to go.</p><p>We also believed that Cog’s architecture was very much on-point. We liked the idea of Relays and Relay Groups, along with the fact that you can control in which machine a command will execute.</p><p>Feature-wise, we loved that anyone is able to write their commands in a language of their choice. We also liked that we could compose commands together to solve more complex problems (ie. Pipelines).</p><p>Generally speaking, I believe ACLs is one of the killer Cog’s features, although we haven’t yet used it since our current commands are read-only.</p><h4><strong>Tell us about `cogy` and what motivated you and your team to build it?</strong></h4><p>One of the initial requirements of the ChatOps project was that every developer should be able to <em>easily</em> create a new command. This, combined with the fact that we’re mostly a big Rails application, led us to create <a href="https://github.com/skroutz/cogy">Cogy</a>.</p><p>So let’s say you have a Rails app and you want to respond to commands from within that app. This typically requires creating a route, writing a new controller and action and maybe some code to handle Cog’s arguments, options and templates. This might be OK if you have one or two commands and a few people working on them, but it becomes a cumbersome, repetitive task when you have tens of commands and 60+ engineers working on that same app.</p><p><a href="https://github.com/skroutz/cogy">Cogy</a> is an opinionated library that takes away all that boilerplate code and lets you focus on your actual commands. It’s essentially a DSL plus some glue stuff (ie. an auxiliary Cog bundle). So defining a command and deploying it becomes as easy as putting the following in a file within your Rails app:</p><pre><strong>#cogy/my_commands.rb</strong></pre><pre>on “foo”, desc: “Echoes a foo bar back at you!” do<br> “@#{handle}: foo bar”`<br>end</pre><p>That way, we reduced the overhead for our devs to a minimum. Now each team can have their own commands defined within their own namespace in a few steps (committing &amp; deploying).</p><p>We’d love to know what people who are looking to integrate their Rails apps with Cog think about <a href="https://github.com/skroutz/cogy">Cogy</a>.</p><h4><strong>What do you want Cog to be able to do for you and your team in the near future?</strong></h4><p>We would love to have graphs with statistics about Cog’s usage within our organization (most/least used commands, slowest commands, channels with the least Cog usage etc.) We would also love if Cog could detect common message patterns in channels and suggest ideas about possible new commands.</p><p>Another feature that we’d love to see (and were thinking to implement) is command auto-completion. We believe this would be a big step forward for Cog’s user experience.</p><p><strong>Is there anything else you would like to tell us?</strong></p><p>ChatOps is a space that’s been explored too little yet has great potential. That’s why I’d like to encourage organizations and individuals reading this post, to jump in and figure out how they can leverage ChatOps and be more effective.</p><p>You should join <a href="http://slack.operable.io/">Cog’s public Slack channel</a> and give Cog (and <a href="https://github.com/skroutz/cogy">Cogy</a>) a try. The Operable team is very helpful and always available.</p><p>I’d also like to congratulate the Operable team for all the great work and responsiveness and I hope you keep it up :)</p><h3>That’s it for now.</h3><p>Thanks Agis!</p><p>Here’s your call to action, if you are thinking of integrating your Rails apps with Cog try out <a href="https://github.com/skroutz/cogy">Cogy</a> and give Agis and the Skroutz engineering team some feedback! Your second call to action, join the community in <a href="http://slack.operable.io/">Slack</a> and see what Cog is all about.</p><h4>Past Interviews:</h4><ol><li><strong>Quick Interview #6</strong>: <a href="https://blog.operable.io/quick-interview-5-building-the-consul-bundle-at-kickstarter-79cd1976eb99#.csuqcnz3j">Building the Consul Bundle at Kickstarter</a></li><li><strong>Quick Interview #3</strong> : <a href="https://blog.operable.io/quick-interview-3-the-cog-book-and-how-to-write-a-command-bundle-3a2c2d1e3720#.bci6q247i">The Cog Book and How to Write A Command Bundle</a></li><li><strong>Quick Interview #4</strong>: <a href="https://blog.operable.io/quick-interview-4-cog-chatops-at-kickstarter-3b2450f7a054#.kmmpbd5ir">Cog + ChatOps at Kickstarter</a></li></ol><h4>Next Interviews:</h4><ol><li>Interview with <a href="https://medium.com/u/a69da0390585">Matthew Walter</a>, the creator of <a href="https://github.com/ohaiwalt/cog-helm">cog_helm</a></li></ol><h3>Stay in Touch:</h3><ol><li>Join our Cog public Slack: <a href="http://slack.operable.io/">slack.operable.io</a></li><li>Follow us on Twitter <a href="https://twitter.com/operableinc">@operableinc</a></li><li>Sign up for our emailed updates via Mailchimp (seldom used and only for BIG announcements) <a href="http://eepurl.com/ce6Sr1">Sign up</a></li><li>Follow this Operable Blog (button somewhere near the top of the page)</li></ol><h4>Interview Topics</h4><p>Have a topic in mind? Contact me, (<a href="https://medium.com/u/32ac24ff136f">Shelton</a>) and we’ll chat about it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b40811226a7e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/operable-news/quick-interview-8-community-collaboration-with-agis-skroutz-b40811226a7e">Quick Interview #8: Community Collaboration with Agis (Skroutz)</a> was originally published in <a href="https://medium.com/operable-news">Operable News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Interview #7: Community Collaboration with Dave Long]]></title>
            <link>https://medium.com/operable-news/quick-interview-7-community-collaboration-with-dave-long-4562305857f?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4562305857f</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[chatops]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Wed, 01 Feb 2017 16:30:29 GMT</pubDate>
            <atom:updated>2017-02-03T19:39:58.569Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TYCQwkhFZ5IUKOkqKKPBLQ.jpeg" /></figure><blockquote>Cog’s approach, enabling developers to write bundles in whatever language they want, is much more friendly to operations engineers and non-JavaScript devs.</blockquote><p>Cog’s public Slack group has an outstanding mix of people. Many individuals come from product companies, a number are DevOps outsiders just discovering ChatOps, and a few are actively trying to integrate Cog into their DevOps consultation practice. This diversity of work backgrounds is very important to Cog and ChatOps in general. This mix brings great ideas and questions to the conversation while subsequently making everyone more knowledgeable and Cog better able to fulfill new and different needs. As a practicing design researcher, I contact as many individuals as possible from these Slack conversations to see where they came from and why they are driven to use a ChatOps platform like Cog. Like many, Dave Long saw the difference that Cog was making and jumped right into the mix. Dave’s participation with <a href="https://medium.com/u/a69da0390585">Matthew Walter</a>, <a href="https://medium.com/u/92f3835c13a8">Agis Anastasopoulos</a>, and <a href="https://medium.com/u/4750906558d2">Vincent De Smet</a> on the Cog on <a href="https://kubernetes.io/">Kubernetes</a> effort is fantastic. Kudos to all these gentlemen! I needed to know more about these guys, so, without giving too much away, here’s my quick interview with Dave Long.</p><h4><strong>What’s your name, title, and role at Cage Data?</strong></h4><p>My name is Dave Long and I am the director of development services here at <a href="https://cagedata.com/blog/">Cage Data</a>.</p><h4><strong>What role does ChatOps play with Cage Data and it’s clients?</strong></h4><p>Cage Data has two facets to our business. We are a DevOps consulting agency, working with clients to build pillars of DevOps into their workflows and cultures, as well as a classical MSP, providing IT support for medium sized companies. ChatOps plays a huge roll into both sides of our business as it helps us to create global knowledge across the team, not just in cluing into what’s being worked on, but also into what’s happening in the background. Whether it’s on-call incidents coming up, builds and deployments completing or clients reaching out through tickets, everything coming together into a single unified chat window helps our team to be able to focus and not search for the answers that they need.</p><h4><strong>Why did you pick Cog vs the other bots?</strong></h4><p>We’ve had a Hubot-based bot in our chat since Cage Data first started working with ChatOps. Hubot’s use of JavaScript as the programming language made it hard for engineers who aren’t familiar with the language to write plugins. Cog’s approach, enabling developers to write bundles in whatever language they want, is much more friendly to operations engineers and non-JavaScript devs.</p><h4><strong>What do you want Cog to be able to do for you and your clients in the near future?</strong></h4><p>I would love to be able to write a bundle for Cog that can run in multiple relays and would pick which relay to run based on arguments of the commands. Working as an MSP we intend to run relays inside of each of our clients to handle tasks such as resetting Windows passwords. We are looking to create a Cog bundle that can have a command which will determine the relay to run on when it’s called, based on which client we are resetting a password for.</p><h4><strong>Is there anything else you would like to tell us? How can we make Cog better?</strong></h4><p>So far, Cog has been a wonderful addition to our team. As the community grows and more bundles are added to the <a href="http://warehouse.operable.io/">warehouse</a>, Cog is only going to get better and better.</p><h3>That’s it for now.</h3><p>Join the Cog conversation on <a href="http://slack.operable.io/">Slack</a>! Add to our diversity, learn more about Cog, and share your thoughts with our friendly community. If, when you come by, talk with Dave about what he’s doing with Kubernetes and <a href="https://medium.com/u/a69da0390585">Matthew Walter</a>’s <a href="https://github.com/ohaiwalt/cog-helm">cog_helm</a> chart. Pretty snazzy stuff.</p><h3>Next Interviews:</h3><ol><li>Interview with <a href="https://medium.com/u/92f3835c13a8">Agis Anastasopoulos</a>, the creator of <a href="https://github.com/skroutz/cogy">Cogy</a></li><li>Interview with <a href="https://medium.com/u/a69da0390585">Matthew Walter</a>, the creator of <a href="https://github.com/ohaiwalt/cog-helm">cog_helm</a></li></ol><h3>Past Interviews:</h3><ol><li><strong>Quick Interview #6</strong>: <a href="https://blog.operable.io/quick-interview-5-building-the-consul-bundle-at-kickstarter-79cd1976eb99#.csuqcnz3j">Building the Consul Bundle at Kickstarter</a></li><li><strong>Quick Interview #3</strong> : <a href="https://blog.operable.io/quick-interview-3-the-cog-book-and-how-to-write-a-command-bundle-3a2c2d1e3720#.bci6q247i">The Cog Book and How to Write A Command Bundle</a></li><li><strong>Quick Interview #4</strong>: <a href="https://blog.operable.io/quick-interview-4-cog-chatops-at-kickstarter-3b2450f7a054#.kmmpbd5ir">Cog + ChatOps at Kickstarter</a></li></ol><h4>More ways to follow Cog:</h4><p><a href="http://operable.io/">Operable</a> | <a href="http://cog-book.operable.io/">Documentation</a> | <a href="http://twitter.com/operableinc">Twitter</a> | <a href="http://slack.operable.io/">Slack</a> | <a href="http://eepurl.com/ce6Sr1">Newsletter</a></p><h4>Interview Topics:</h4><p>Have a topic in mind? Contact me, (<a href="https://medium.com/u/32ac24ff136f">Shelton</a>) and we’ll chat about it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4562305857f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/operable-news/quick-interview-7-community-collaboration-with-dave-long-4562305857f">Quick Interview #7: Community Collaboration with Dave Long</a> was originally published in <a href="https://medium.com/operable-news">Operable News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Interview #6: Building the Consul Bundle at Kickstarter]]></title>
            <link>https://medium.com/operable-news/quick-interview-5-building-the-consul-bundle-at-kickstarter-79cd1976eb99?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/79cd1976eb99</guid>
            <category><![CDATA[chatops]]></category>
            <category><![CDATA[hashicorp]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kickstarter]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Thu, 22 Dec 2016 17:06:01 GMT</pubDate>
            <atom:updated>2017-03-02T21:13:59.854Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_-rJbPe8PEaJIIy4VKcnDA.jpeg" /></figure><blockquote>We could do this by making API calls to the (consul) cluster, but thought it would be good to be able to document the process as we went by testing it in chat.</blockquote><p>As Kickstarter continues to expand team visibility and collaboration through ChatOps practices, they recently found themselves at a familiar fork in the road. They just started using Hashicorp’s <a href="https://www.consul.io/">Consul</a>. SThey recently started using Hashicorp’s Consul; should they manage Consul as individuals using its CLI from their workstations, or should they manage it as a team by bringing it into chat? Since Kickstarter is committed to team collaboration and visibility, they chose to integrate Consul’s basic management into their Slack channels by building a bundle for Cog. <a href="https://medium.com/u/19d8ed3b4370">Logan McDonald</a>, Operations Engineer at Kickstarter, took on the challenge and recently published the <a href="https://bundles.operable.io/bundles/consul/latest">consul</a> bundle in Cog’s <a href="https://bundles.operable.io/">Bundle Warehouse</a>. Fresh off the build, I asked Logan a few question about her bundle build process and what she might want to see next from Cog; here are her responses.</p><h4><strong>What was it like building a bundle of commands for Cog?</strong></h4><p>Fun! I really appreciated the <a href="https://github.com/operable/cog-rb">cog-rb library</a>, which made it easy to interact with Cog in a language close to our own codebase. I also liked the ability to use Docker images to package the bundles. Another plus was the dynamic configuration feature which allows you to set base, channel, and user-specific environment variables. That you can control dynamic configuration using cogctl made this really easy. Furthermore, <a href="https://cog-book.operable.io/">the cog book</a> is a great source of documentation for those starting out with Cog. Beyond documentation, I appreciated that the code for cog-rb, cogctl, all bundles, and much of the Operable stack are open source so if I couldn’t figure out something in the documentation I could go straight to, the code itself.</p><h4><strong>What was your motivation behind creating the consul bundle? </strong>What kind of issues has it helped your team address?</h4><p>Our team has just started to use Hashicorp’s <a href="https://www.consul.io/">Consul</a> and <a href="https://www.vaultproject.io/">Vault</a>. We wanted the ability to test our Consul cluster and specifically our <a href="https://www.consul.io/docs/agent/http/kv.html">Consul key/value store</a>. We could do this by making API calls to the cluster, but thought it would be good to be able to document the process as we went by testing it in chat.</p><h4><strong>What command bundles do you wish Cog had, and how could they help your team?</strong></h4><p>Personally, I’m excited about building/having a Grafana bundle that delivers snapshots from an s3 bucket to chat. This would also be a cool way to have our developers interact with metrics, not just in the browser but in chat as well. It would make the thought process of checking metrics visible. I’m not sure how it’d work, but a postmortem bot would also be a cool way to organize that practice — it could keep the time, record the conversation through chat, point us to logs, etc.</p><h4>What’s the next Cog bundle you’d like to build, and why?</h4><p>Rewrite the entire deployment process as a bundle, incorporating existing ability to deploy Cloud Formation stacks. I’d also build the Grafana bundle. I’d also build out a bundle skeleton and package it in a gem possibly. This would contain a skeleton for the best bundle developing/testing practices. Although the various examples of existing bundles are nice, there are a couple features I’d like to add, like the ability to <a href="https://github.com/kickstarter/cog-consul-oss/pull/2">restrict commands to channels</a>.</p><h4>Where can people go to learn more about the consul bundle<strong>?</strong></h4><p><a href="http://github.com/kickstarter/cog-consul-oss">The repo</a> is a good place to start. To get a sense of how we are using Consul key/value storage and Vault, checkout my <a href="https://kickstarter.engineering/ecs-vault-shhhhh-i-have-a-secret-40e41af42c28#.hepj52o71">coworker Natacha’s recent blog post on the subject</a>.</p><h3>That’s it for now.</h3><p>Navigate your browser over to Cog’s <a href="https://bundles.operable.io/bundles/consul/latest">Bundle Warehouse</a> and pick up Logan’sconsul bundle. Want to read more on how Kickstarter has integrated ChatOps into their daily lives, read, <a href="https://blog.operable.io/quick-interview-4-cog-chatops-at-kickstarter-3b2450f7a054#.kmmpbd5ir">Quick Interview #4: Cog + ChatOps at Kickstarter</a>. Enjoy!</p><h3>Past Interviews:</h3><ol><li><strong>Quick Interview #3</strong> : <a href="https://blog.operable.io/quick-interview-3-the-cog-book-and-how-to-write-a-command-bundle-3a2c2d1e3720#.bci6q247i">The Cog Book and How to Write A Command Bundle</a></li><li><strong>Quick Interview #4</strong>: <a href="https://blog.operable.io/quick-interview-4-cog-chatops-at-kickstarter-3b2450f7a054#.kmmpbd5ir">Cog + ChatOps at Kickstarter</a></li><li><strong>Quick Interview #5</strong>: <a href="https://blog.operable.io/quick-interview-5-warehouse-of-bundles-with-patrick-van-stee-18ff9c13723d#.v32mimkt2">Warehouse of Bundles with Patrick Van Stee</a></li></ol><h3>More ways to follow Cog:</h3><p><a href="http://operable.io/">Operable</a> | <a href="http://cog-book.operable.io/">Documentation</a> | <a href="http://twitter.com/operableinc">Twitter</a> | <a href="http://slack.operable.io/">Slack</a> | <a href="http://eepurl.com/ce6Sr1">Newsletter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79cd1976eb99" width="1" height="1" alt=""><hr><p><a href="https://medium.com/operable-news/quick-interview-5-building-the-consul-bundle-at-kickstarter-79cd1976eb99">Quick Interview #6: Building the Consul Bundle at Kickstarter</a> was originally published in <a href="https://medium.com/operable-news">Operable News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Interview #5 : Warehouse of Bundles with Patrick Van Stee]]></title>
            <link>https://medium.com/operable-news/quick-interview-5-warehouse-of-bundles-with-patrick-van-stee-18ff9c13723d?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/18ff9c13723d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[chatops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Fri, 11 Nov 2016 21:12:56 GMT</pubDate>
            <atom:updated>2016-12-21T17:04:50.891Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pKfHHa9KmfFMNJl0zbNBhw.png" /><figcaption>Cog’s Command Bundle Warehouse Facility</figcaption></figure><p>Cog without bundles is just a cute blue robot that stares at you. Cog with bundles is a cute blue robot that can do wonderful tasks for you. Cog won’t be able to do your laundry (yet), but with the right set of command bundles, it will help your team collaboratively manage your <em>infrastructure. </em>So, if you fear being stared at by Cog, you will need to load it with helpful command bundles. Where do you get these commands? You can now install and upload bundles at <a href="http://bundles.operable.io/">Cog’s Bundle Warehouse</a>. Patrick Van Stee (Operable Software Engineer) directed Cog’s Bundle Warehouse experience, so let’s hear more about what he had in mind for this grand opening.</p><h4>What do you hope to give our users with warehouse.operable.io? (Why was cogcmd in GitHub insufficient?)</h4><p>Warehouse was built with two goals in mind: making it easy to find bundles written by the community, and easily installing those bundles without cloning a repo.</p><p>The first thing everyone wants to do after they install Cog is to try out some command bundles to talk to their existing infrastructure. Over the past few months we wrote bundles for some of the most popular services like Cloud Formation, Heroku and Pagerduty. But, we kept hearing of community members building bundles for things that we either hadn’t thought of or just didn’t have time to build and wanted a place for them to share those bundles with the rest of the community. Giving users a place to both share and find bundles from other users both makes Cog even more useful from day one, but also allows people to more easily collaborate on existing bundles.</p><p>Now that we have a single place for anyone to register a bundle, we can now easily lookup a bundle by name instead of needing to reference an entire config file. This makes it possible to install bundles with a simple chat command, where before you wouldn’t have able able to access a file locally. But, even when using cogctl, it also makes the process of installing a bundle quick and easy.</p><h4>What features are in the Bundle Warehouse’s future?</h4><p>We want to improve our bundle related commands so searching for, upgrading, and finding outdated bundles are all possible from chat. We have plenty more planned for Warehouse, but if there’s anything you’d like us to build please let us know.</p><h4>What bundles do you wish we had for Cog?</h4><p>Most of the bundles we’ve built and seen in the community so far are highly useful, but relatively simple API wrappers for existing services. These bundles are great and I hope we continue to see more and more of these. But, the real power of using Cog comes from composing commands using pipelines. So, I’d love to see more commands that make heavy use of pipelines to do things that we haven’t even thought of yet. One interesting example that we’ve experimented with is a graph generating command that can be used in a pipeline with any other command that simply generates json data, similar to piping a csv file to gnuplot. I’m sure some of the most useful and interesting bundles are things we haven’t even thought of yet and I can’t wait to see what our community comes up with.</p><h3>That’s it for now.</h3><p>The Bundle Warehouse is open for business! Head over to <a href="http://bundles.operable.io/">Cog’s Bundle Warehouse</a> and check out what we have and get inspired to make your own command bundle. The shelves are a bit bare, but we (community + Operable team) are adding and updated bundles frequently. If you are curious about creating a bundle, read our documentation on <a href="http://cog-book.operable.io/#__strong_writing_a_command_bundle_strong">Writing a Command Bundle</a>.</p><h3>Past Interviews:</h3><ol><li><a href="http://bit.ly/Blog_Kickstarter-Cog"><strong>Quick Interview #4 </strong>: Cog + ChatOps at Kickstarter with Aaron Suggs</a></li><li><a href="http://bit.ly/TheCogBook"><strong>Quick Interview #3</strong> : The Cog Book, and How to Write A Command Bundle</a></li><li><a href="http://bit.ly/BlogHumanScale"><strong>Quick Interview #2 </strong>: Human Scale Systems with Mark Imbriaco</a></li><li><a href="http://bit.ly/Blog_Greenbar"><strong>Quick Interview #1 </strong>: Templates + Project Greenbar</a></li></ol><h3>Next Interviews:</h3><ul><li>Quick Interview #6 : Cog for Enterprise Teams with</li><li>Quick Interview #? : Cog’s Favorite Fall Colors</li></ul><h3>Stay in Touch:</h3><ol><li>Join our Cog public Slack: <a href="http://slack.operable.io/">slack.operable.io</a></li><li>Follow us on Twitter <a href="https://twitter.com/operableinc">@operableinc</a></li><li>Sign up for our emailed updates via Mailchimp (seldom used and only for BIG announcements) <a href="http://eepurl.com/ce6Sr1">Sign up</a></li><li>Follow this Operable Blog (button somewhere near the top of the page)</li></ol><h4>Interview Topics</h4><p>Have a topic in mind? Contact me, (<a href="https://medium.com/u/32ac24ff136f">Shelton</a>) and we’ll chat about it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18ff9c13723d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/operable-news/quick-interview-5-warehouse-of-bundles-with-patrick-van-stee-18ff9c13723d">Quick Interview #5 : Warehouse of Bundles with Patrick Van Stee</a> was originally published in <a href="https://medium.com/operable-news">Operable News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Voting.]]></title>
            <link>https://medium.com/@sheltondavis/voting-a74dba84789a?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a74dba84789a</guid>
            <category><![CDATA[note-to-self]]></category>
            <category><![CDATA[vote]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Tue, 08 Nov 2016 14:12:35 GMT</pubDate>
            <atom:updated>2016-11-08T14:12:35.445Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ez5mAbPWS66t8KszSPJfUg.png" /></figure><p>A place where individual voices are truly equal. One vote, one citizen.</p><p>Remember that your voice and civic duty don’t go away once the election is over. Our leaders cannot do it all, get involved. Governing must be a team sport and if you are a citizen, you are a needed member of the team.</p><p><em>Written as a note to myself.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a74dba84789a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Interview #4: Cog + ChatOps at Kickstarter]]></title>
            <link>https://medium.com/operable-news/quick-interview-4-cog-chatops-at-kickstarter-3b2450f7a054?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b2450f7a054</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[chatops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloudformation]]></category>
            <category><![CDATA[kickstarter]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Tue, 25 Oct 2016 17:10:30 GMT</pubDate>
            <atom:updated>2017-01-24T22:07:13.783Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X5HEEZXXhk3meFgboSL5fw.jpeg" /><figcaption>Rail bridge in Durham, NC across the street from the OG “Bull Durham” ball park.</figcaption></figure><blockquote><em>Engineers were running commands on their laptops, or clicking around a web UI without a lot of transparency or context about who was doing what. Coordinating with the rest of the team was an extra step or afterthought. — Aaron Suggs Operations Engineering Manager at Kickstarter</em></blockquote><p>If uncoordinated action happens within a small team, it <em>can</em> be manageable. Throw in a larger team, remote working, time zones, security needs, and differing experience levels into the mix, and coordination becomes essential, yet extremely difficult to realize. This is where Cog can help — it allows you to start securely coordinating your workflows in chat, providing much-needed transparency to your entire team.</p><p><a href="https://medium.com/u/4d1eec0518e7">Aaron Suggs</a> (Operations Engineering Manager at Kickstarter) and Kyle Burckhard (Senior Operations Engineer) are ahead of the DevOps + ChatOps curve. They have lots of custom automation already in place, and were evaluating several different ChatOps platforms when Operable approached them with a proposition: let’s take a look at which of your current workflows are causing you the most pain and see if we can come up with a set of commands for Cog that can help make a better experience for your team.</p><p>They were game, and so Aaron and his team worked with <a href="https://medium.com/u/ae2630ddde1a">Mark Imbriaco</a> and <a href="https://medium.com/u/72faed955369">Matthew Peck</a> of Operable to tackle their thorny CloudFormation management workflow with Cog.</p><h4><strong>How did you interact with CloudFormation / ec2 / AWS prior to Cog?</strong></h4><p>We have a few homegrown tools like <a href="https://github.com/kickstarter/cfn-flow">cfn-flow</a> and <a href="http://ktheory.com/archives/feature-environments/">Hivequeen</a> that were our opinionated way of doing things. I never felt like we got it quite right; and they were kind of stop-gaps until better abstractions and more robust OSS tools came out.</p><p>Engineers were running commands on their laptops, or clicking around a web UI without a lot of transparency or context about who was doing what. Coordinating with the rest of the team was an extra step or afterthought.</p><h4><strong>How has the Cog integration improved that interaction?</strong></h4><p>Cog is a significant improvement in a couple ways. It gives us transparency and auditability to see who did what when and why. Our chat history became a natural teaching tool to document how we manage our infrastructure day-to-day.</p><p>Cog’s composable pipeline architecture is a big improvement over the more imperative, special-purpose scripts I’ve made in the past.</p><p>Take the Cog <a href="https://github.com/cogcmd/aws-cfn">aws-cfn bundle</a> for instance. My colleague Kyle Burckhard was able to implement our custom business logic and workflow as a few lines of Ruby code and Cog aliases. The heavy lifting is done by Cog and the general-purpose aws-cfn bundle. Cog’s composable pipelines let us elegantly encapsulate &amp; easily test our CloudFormation workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugY2FKXoOV995F7YZhccdw.png" /><figcaption>Aaron using Cog to launch a new development server via CloudFormation.</figcaption></figure><h4><strong>What do you want to do with Cog in the future?</strong></h4><p>Oh, there are big plans, Shelton. :-) Short term, we’re building out new services as Docker containers in ECS; we’ll use Cog to deploy those services. We’re thinking about how we could use Cog to run arbitrary commands across groups of services with something like Rundeck or AWS SSM Service.</p><p>And we think of a new easy-win each week, like using Cog to manage our status page, or let engineers more easily interact with our CI service.</p><p>The big picture plan is for Cog to elevate the Kickstarter engineering team’s happiness &amp; productivity by making complex tasks simple, safe, and easy.</p><h3>That’s it for now.</h3><p>We’re continuing to work with Aaron and the team at Kickstarter to improve the experience of managing AWS infrastructure, but you can start using our new commands now! Be sure to check out the <a href="http://bit.ly/COG_CloudFoundation">aws-cfn bundle</a> in the Bundle Warehouse.</p><p>An in-depth whitepaper describing our work with Kickstarter is in the works; join us in our <a href="http://slack.operable.io/">Slack channel</a> to find out when it lands.</p><p>Lastly, be on the lookout for an upcoming post on Kickstarter’s use of our new <a href="http://bit.ly/Bundle_ecs">aws-ecs bundle</a>!</p><h3>Past Interviews:</h3><ol><li><a href="http://bit.ly/Blog_Greenbar"><strong>Quick Interview #1 </strong>: Templates + Project Greenbar</a><br>NOTE: <a href="http://bit.ly/2cxkVae">Greenbar + Templates</a> features went out in release 0.14! Check out our release <a href="https://github.com/operable/cog/releases/tag/0.14.0">notes</a>.</li><li><a href="http://bit.ly/BlogHumanScale"><strong>Quick Interview #2 </strong>: Human Scale Systems with Mark Imbriaco</a></li><li><a href="http://bit.ly/TheCogBook"><strong>Quick Interview #3</strong> : The Cog Book, and How to Write A Command Bundle</a></li></ol><h3>Next Interviews:</h3><ul><li>Quick Interview #5 : A Talk with <a href="https://medium.com/u/fd005a814ab0">Patrick Van Stee</a> about our new <a href="http://bit.ly/CogBundleWarehouse">Bundle Warehouse</a>.</li><li>Quick Interview #6 : TBD</li></ul><h3>Stay in Touch:</h3><ol><li>Join our Cog public Slack: <a href="http://slack.operable.io/">slack.operable.io</a></li><li>Follow us on Twitter <a href="https://twitter.com/operableinc">@operableinc</a></li><li>Sign up for our emailed updates via Mailchimp (seldom used and only for BIG announcements) <a href="http://eepurl.com/ce6Sr1">Sign up</a></li><li>Follow this Operable Blog (button somewhere near the top of the page)</li></ol><h4>Interview Topics</h4><p>Have a topic in mind? Contact me, (<a href="https://medium.com/u/32ac24ff136f">Shelton</a>) and we’ll chat about it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b2450f7a054" width="1" height="1" alt=""><hr><p><a href="https://medium.com/operable-news/quick-interview-4-cog-chatops-at-kickstarter-3b2450f7a054">Quick Interview #4: Cog + ChatOps at Kickstarter</a> was originally published in <a href="https://medium.com/operable-news">Operable News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Interview #3 : The Cog Book, and How to Write A Command Bundle]]></title>
            <link>https://medium.com/operable-news/quick-interview-3-the-cog-book-and-how-to-write-a-command-bundle-3a2c2d1e3720?source=rss-32ac24ff136f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a2c2d1e3720</guid>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[asciidoctor]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[chatops]]></category>
            <dc:creator><![CDATA[Shelton Davis]]></dc:creator>
            <pubDate>Fri, 14 Oct 2016 16:06:00 GMT</pubDate>
            <atom:updated>2016-10-18T02:16:09.651Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GatJdV_UqZBiqQRcQQrgfg.jpeg" /></figure><p>We are writing a book about Cog! Though the book will eventually encompass all aspects of running, managing, using, and writing for Cog, <a href="https://medium.com/u/3c1c6d503233">Christopher Maier</a> (Operable Software Engineer) started the book off with some much-requested material all about writing a command bundle. For those that aren’t familiar, a bundle is a set of commands that make Cog do something. For example, from chat (Slack, HipChat, more to come) a user with the right permissions can do something simple like tweet the status of an API:</p><pre>@cog twitter:tweet Currently experiencing API slowdowns; investigating.</pre><p>Someone had to write that twitter:tweet command and Chris takes you through the process step-by-step in the chapter <em>Writing A Command Bundle</em>. I asked Chris a few question about the chapter and the book itself; here are his responses.</p><h4>What are you trying to accomplish with this new chapter on Bundle Creation that wasn’t included in the previous tutorial?</h4><p>Although we have some of the lower-level details covered in our online <a href="https://docs.operable.io/">documentation</a>, there wasn’t any comprehensive overview of how to tie it all together. If you already knew how to write a Cog command, the documentation we had would serve you pretty well (“what was the name of that particular environment variable… oh yeah, COG_ARGV!”), but if you were brand new to Cog, it could be difficult to piece it all together.</p><p>What we’ve tried to do with this chapter is take the reader from an initial idea — sending tweets from Cog — and then gradually introduce Cog concepts to build a complete bundle. Sending tweets is a pretty accessible and small objective to tackle, so it’s a nice framework to use for exploring the details of the Cog / command interface. And while we have libraries that make it easier to write commands in <a href="https://github.com/operable/cog-rb">Ruby</a> and <a href="https://github.com/operable/pycog3">Python</a>, we don’t use either of those in this chapter. In order to make the Cog / command interface very clear, and to drive home the fact that you can write a command in whatever language you like, we actually write a lot of the bundle using bash scripts!</p><p>Another thing we kept in mind was the fact that although, in the end, the Cog / command interface is pretty simple, dealing with that in addition to other details like the bundle metadata format and packaging and deployment concerns could be a lot to assimilate at once for new users. We wanted to show something working as soon as possible. To that end, we break things up and introduce just a small piece of the overall picture at a time. In the beginning, we’re actually running the new Cog command completely outside of Cog! At every stage, though, we’ve always got something that runs; it just gains more features as we go on.</p><h4>What format are you writing Cog Book and why did you choose this format?</h4><p>We’re using <a href="http://www.methods.co.nz/asciidoc/">Asciidoc</a>. Like Markdown, it’s a human-readable markup language, but unlike Markdown, it has a lot of nice features for writing technical documentation (I particularly like the ability to add callouts in code samples).</p><p>The fact that it’s a plaintext format that we can version control is very nice, too.</p><p>For the curious, our build tooling is based on <a href="http://asciidoctor.org/">Asciidoctor</a>, which we’ve packaged up into a convenient Docker image. The code for both the book and the tooling is available at <a href="http://bit.ly/GitHub_TheCogBook">http://bit.ly/GitHub_TheCogBook</a>.</p><h4>What chapter is next in the Cog Book?</h4><p>Next up will probably be something about installing and running Cog and Relay, targeted toward developers, with a particular eye out for bundle developers. Now that we’ve got bundle authoring covered, we want to make sure that people that want to write bundles can easily set up their machines to do so.</p><h3>That’s it for now.</h3><p>If you haven’t already installed Cog, head over to our <a href="http://docs.operable.io/docs/installation">installation docs</a> and get yourself a shiny new Cog. Once you have Cog up and running, check out the chapter Chris just walked with us about, <a href="http://cog-book.operable.io/">Writing Command Bundles</a> in The Cog Book. Enjoy!</p><h3>Past Interviews:</h3><ol><li><strong>Quick Interview #1 : Templates + Project Greenbar</strong><br>NOTE: <a href="http://bit.ly/2cxkVae">Greenbar + Templates</a> features went out in release 0.14! Check out our release <a href="https://github.com/operable/cog/releases/tag/0.14.0">notes</a>.</li><li><a href="http://bit.ly/BlogHumanScale"><strong>Quick Interview #2 : Human Scale Systems with Mark Imbriaco</strong></a></li></ol><h3>Next Interviews:</h3><ul><li>Quick Interview #4 : A Talk with<a href="https://medium.com/u/fd005a814ab0">Patrick Van Stee</a> about our new Bundle Warehouse.</li><li>Quick Interview #5 : TBD</li></ul><h3>Stay in Touch:</h3><ol><li>Join our Cog public Slack: <a href="http://slack.operable.io/">slack.operable.io</a></li><li>Follow us on Twitter <a href="https://twitter.com/operableinc">@operableinc</a></li><li>Sign up for our emailed updates via Mailchimp (seldom used and only for BIG announcements) <a href="http://eepurl.com/ce6Sr1">Sign up</a></li><li>Follow this Operable Blog (button somewhere near the top of the page)</li></ol><h4>Interview Topics</h4><p>Have a topic in mind? Contact me, (<a href="https://medium.com/u/32ac24ff136f">Shelton</a>) and we’ll chat about it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a2c2d1e3720" width="1" height="1" alt=""><hr><p><a href="https://medium.com/operable-news/quick-interview-3-the-cog-book-and-how-to-write-a-command-bundle-3a2c2d1e3720">Quick Interview #3 : The Cog Book, and How to Write A Command Bundle</a> was originally published in <a href="https://medium.com/operable-news">Operable News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>