<?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 Dormain Drewitz on Medium]]></title>
        <description><![CDATA[Stories by Dormain Drewitz on Medium]]></description>
        <link>https://medium.com/@dormaindrewitz?source=rss-2594bc46074e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*Wz8vQzGAdYC7mfddgc9nlA.jpeg</url>
            <title>Stories by Dormain Drewitz on Medium</title>
            <link>https://medium.com/@dormaindrewitz?source=rss-2594bc46074e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:37:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dormaindrewitz/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[On derivatives of technical debt: defining terms and players]]></title>
            <link>https://medium.com/@dormaindrewitz/on-derivatives-of-technical-debt-defining-terms-and-players-fb5d58406de0?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb5d58406de0</guid>
            <category><![CDATA[technical-debt]]></category>
            <category><![CDATA[gluecon]]></category>
            <category><![CDATA[tech-debt]]></category>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Thu, 22 Aug 2019 12:01:03 GMT</pubDate>
            <atom:updated>2019-08-22T12:01:03.188Z</atom:updated>
            <content:encoded><![CDATA[<p>In May 2019, I gave a talk at GlueCon, “<a href="https://www.slideshare.net/dormain/gluecon-2019-can-we-trade-derivatives-of-technical-debt">Can We Trade Derivatives of Technical Debt?</a>” The purpose of the talk wasn’t to answer the question literally. It was a way to rethink the tech debt analogy, where it’s gotten stuck, and where we can re-frame the analogy to have a useful conversation between technical teams and business stakeholders. I’ve published about <a href="https://content.pivotal.io/intersect/risk-profile-of-technical-debt">understanding the risk profile of your technical debt</a> separately. Here, I’ll define the terms of players needed to explore the derivatives side of the analogy.</p><p>Before we can extend the “tech debt” analogy to derivatives trading, we need to establish a few things. First, we need to define derivatives.</p><h4>Derivatives: A layperson’s definition</h4><p>I won’t provide an academic definition here. There are plenty of places on the Internet to get more detailed definitions. In layperson terms, however, most derivatives are an agreement. Derivatives are usually an agreement between two parties, usually for:</p><ul><li>Something to happen (e.g. option to buy or sell something)</li><li>In some quantity (e.g. 500 shares in a company)</li><li>In the event of something (e.g. the stock is “in the money,” a.k.a. it’s above/blow the strike price)</li><li>Within a certain period of time (e.g. before the options contract expires)</li></ul><figure><img alt="Image of a historical insurance agreement with text overlaid to describe a derivative" src="https://cdn-images-1.medium.com/max/1024/0*Iwo1b6yuVnUQjgkT" /><figcaption>Derivatives have a lot in common with insurance agreements</figcaption></figure><p>If this sounds like a home owners insurance policy, you’re not far off. The house itself is the underlying asset. It’s insured for a certain amount and for a certain period of time. Certain types of events are covered by the policy. As we go on, we’ll see how other derivatives are kind of like insurance for other types of assets. That will be useful as we carry this analogy over to technical debt.</p><figure><img alt="Painting of an old fashioned bazaar with examples of derivatives agreements overlaid" src="https://cdn-images-1.medium.com/max/1024/0*FzdKv0AGHhxWzInn" /><figcaption>There are many types of derivatives, but they often have things in common</figcaption></figure><p>If you are familiar with stock options, you’ll recognize these four qualities to a derivatives agreement. These same aspects of the agreement apply to things like <a href="https://www.investopedia.com/terms/f/futures.asp">futures</a> and <a href="https://www.investopedia.com/terms/i/interestrateswap.asp">interest rate swaps</a>. Derivatives that trade on an exchange are standardized and regulated. But most derivatives are not exchange-traded. They are basically contracts between two parties.</p><p>Why do people (or organizations) buy and sell derivatives? At their core, derivatives are used to hedge, or offset, risk. One entity stands to gain with prices, interest rates, exchange rates, whatever going up. So, they use a derivative to gain something (and offset losses) if that thing goes down, for example.</p><p>If you own a stock, you already stand to gain if the price increases. You can buy an option to sell at a certain price, even if the price drops below that point. Effectively, you pay a little extra to lock in potential losses. Or a farmer that stands to gain if the price for their crop goes up and they use a futures contract to lock in a price for their crop. Or a business that stands to gain if the dollar gets weaker, so they write a contract to gain if the dollar gets stronger. These are all means of offsetting risk of potential losses. Of course, someone has to take the other side of that trade… the counterparty.</p><p>There’s another kind of derivative, which is also used to offset risk, which involve pooling assets. This is where mortgage-backed securities come in. Here, loans are pooled and then resold in tranches. Each tranche is like a slice of the full pizza pie that is the pool of mortgages. It’s still a way for the bank who lent the money to home buyers to offset the risk of defaults. In fact, the tranches can have different risk profiles, depending on the underlying buyer creditworthiness or home appraisal. This is where the notion of “prime” and “subprime” comes in.</p><figure><img alt="Pizza with words overlaid that say “Pooling and repackaging”" src="https://cdn-images-1.medium.com/max/930/0*6MyHzmhMkqnoggLi" /><figcaption>A “slice” of a pool of tech debt?</figcaption></figure><p>The notion of classifying debt by different risk profiles is very useful when thinking about technical debt. Read my other post to understand the risk profile and interest rate on technical debt.</p><h3>Who is the borrower? And who is the lender?</h3><p>Thinking through the lens of derivatives brings certain parts of the tech debt analogy into sharp relief. It heightens the awareness of assessing risk profiles and interest rates since, after all, derivatives are about hedging risk. But derivatives are also a contract between two parties, and, at first glance, it’s unclear who those parties would be? Who is the borrower in this scenario, and who is the lender? We need this answered to know who is the party who would trade derivatives to offset their risk as a lender.</p><figure><img alt="Emoji showing money going from the bank to a house and more money going from a family to a businesswoman" src="https://cdn-images-1.medium.com/max/1023/0*uw_SbEu2LdFuQVW-" /><figcaption>As consumers, we naturally empathize with the “borrower”</figcaption></figure><p>Most of the discussion around tech debt seems to revolve around the borrower’s experience. Borrowers have to make the interest payments, and get squeezed with a higher bill when rates spike. Technical teams express the pain of this burden with tech debt. After all, they are shouldering the work of changing the code. They also are the ones to “pay down” the debt in the form of retiring code. Does that make developers the “borrower” in this relationship? Maybe. But they also are more directly in control of the factors that set the interest rate.</p><p>Meanwhile, product owners, representing the business goals, also pay a price when interest rates spike and releases are delayed. The decision to rush a product out, even if it means taking on hard-to-change code, is usually a business-oriented decision. They want what the debt — the code — can buy: an application that drives business. Does that make product owners the borrower in this relationship? And would that make developers the lender?</p><figure><img alt="A businesswoman emoji who’s face is covered by the question: “Who are we borrowing from when we take on tech debt?”" src="https://cdn-images-1.medium.com/max/1022/1*EhV6fVWRml4svqyrnyx7nQ.png" /><figcaption>The Tech Debt Lender Question</figcaption></figure><p>I raised this question of “who is the lender in the tech debt analogy?” in my GlueCon talk, but my opinion has taken shape since. Technical teams are more directly in control of adjusting the interest rate. Despite how it may sometimes appear, technical teams are akin to the lender in these relationships, with the business as the borrower. Technical teams are underwriting loans to the business, which the business hopes are covered by growth or efficiency (i.e., cost savings). Healthy debt powers a growing economy, but lenders get nervous if they see unhealthy debt. Similarly, businesses face a number of risks when they take on too much code that is too hard to change.</p><p>***</p><p>We’ve established the basics of what derivatives are and who the lender and borrower are in the tech debt analogy. However, several questions remain to extend the tech debt analogy to derivatives trading. First, we’d need to understand who the counterparty would be to technical teams (the lenders). Who is taking the other side of that deal? Next, what is the event technical teams would want to insure against. What kind of agreement would protect against that event?</p><p>The questions don’t stop there and at a certain point we have to ask ourselves if these analogies are still helpful. Alas, we probably won’t be trading derivatives of tech debt anytime soon, but hopefully we <a href="https://content.pivotal.io/intersect/risk-profile-of-technical-debt">understand our tech debt risk profile</a> a little better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb5d58406de0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to write an abstract for your conference talk or webinar]]></title>
            <link>https://medium.com/@dormaindrewitz/how-to-write-an-abstract-for-your-conference-talk-or-webinar-66ae959be2e6?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/66ae959be2e6</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[writing-tips]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[webinar-tips]]></category>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Thu, 02 May 2019 02:12:41 GMT</pubDate>
            <atom:updated>2025-04-25T16:23:12.379Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-bbyuBY4F4eamVasC1QQpw.jpeg" /><figcaption>Writers Block. Image credit <a href="https://www.flickr.com/photos/42931449@N07/5263541791/in/photolist-9282Ax-8xDP5L-Au3cM7-AUh7cY-6TgXys-2b8W6jP-BtcWbK-cmZYC1-bVRXUM-7PrwbL-8kvbUC-2RGwKs-bAJoTW-bVtmk8-asgMUi-75GAc-Qzsc3e-cWmXJm-51m6sp-5koRnU-b6fJci-b6fHWZ-rZQzf-dbctfy-6v7oBz-QiPZZA-2bqErKN-bAVXQo-5E28PF-bAW24w-3W8FN-7M2gwP-4rT3eS-5koSRw-6APkUX-oY1s6K-2SRA4B-8nUMKJ-98YRsC-6T5ZZk-UfBbd6-hwAgto-Jw3kgU-26Cqn58-8DT8fX-6ABKU5-QidPof-6vc7b3-adqHz6-6v7oBp">photosteve101</a> (<a href="https://creativecommons.org/licenses/by/2.0/">CC By 2.0</a>)</figcaption></figure><p>For better or for worse, I’ve become an abstract-writing machine over the years. Whether it’s from writing my own abstracts for conference CFPs, or ghost-writing webinar abstracts for others, I’ve drafted a lot of abstracts. I’ve settled into a bit of a formula.</p><p>No one likes to admit they like formulaic writing, but it means that I can quickly churn out an abstract. When I follow that formula, I know that I’ve covered the key parts. Things can still go wrong, but I haven’t missed an important element. It’s also a check against belaboring a single point in an abstract.</p><p>In this article, I’m going to share some examples from abstract’s I’ve worked on with teammates. I’m not saying they are perfect. But striving for perfection in an abstract means you aren’t focused on the right thing.</p><p>Before I walk you through this formula, I want to share a bit about my philosophy on the topic. That philosophy is to not get too wrapped around the axle over an abstract. Remember that you’re not going to win a Pulitzer Prize for your abstract, no matter how great it is. It’s an abstract.</p><h3>Why your talk wasn’t selected (spoiler alert: it probably wasn’t your abstract)</h3><p>When you are submitting for a competitive conference call for proposals, it can feel like a lot is riding on that abstract. But the reality is you shouldn’t agonize over the abstract. If you’re spending hours on it, you’ve probably spent too much time. In the end, if your talk wasn’t selected, there are many other factors that were in play. Here are some to remember:</p><ul><li>How many other submissions were there for how many spots? The raw odds of being selected may have been very low.</li><li>How many other submissions came from your company? Many conference organizers are mindful to not have a single vendor or company dominate a track. If lots of your colleagues were submitting to the same event, you may have been competing with each other.</li><li>Did your title stand out? <strong>Your title is the most valuable real estate when selling your talk to a track organizer and prospective audience.</strong></li><li>Was your submission aligned with the conference or track? As a track co-chair, I’ve seen submissions that are way out-of-whack with the track’s purpose. Sometimes they look like a thoughtless copy-paste job from a generic talk or pitch. Sometimes it seems like the person picked the track that was “close enough” to what they wanted to talk about — but didn’t adjust their talk to be in line with what the track was about. Depending on how many submissions, that kind of “loose interpretation” can cost you.</li></ul><p>It’s also unlikely that low webinar attendance is due to the abstract. Again, there are many factors, including title (again), promotion, and channel.</p><p>Now let’s get on with that formula.</p><h3>Open with the pain. And maybe a question.</h3><p>People are too quick to offer solutions. They don’t take a moment to bask in the pain. But if I’m searching for a solution to my problem, I’m first looking for someone who understands my problem. As a reader or audience member, I need to recognize myself (and my pain) first.</p><p>Here’s one where we establish a couple facts, including the pain points:</p><p><em>RabbitMQ is the most popular open-source message broker. It’s a de facto standard for message-based architectures. And yet, </em><strong><em>despite the abundant documentation and usage, developers and operators can still get tripped up on configuration and usage patterns</em></strong><em>.</em></p><p>Here’s another opening line that focuses on a specific pain:</p><p><strong><em>Measuring the value of a platform on your organization can be difficult, and communicating it can be even more so</em></strong><em>.</em></p><p>Sometimes the pain is the uncertainty itself around a topic. When there are questions swirling around, it’s useful to state those questions. There also might be questions that people <em>aren’t</em> asking, but should. Again, stating the question is a useful way to prompt curiosity within your prospective audience.</p><p>Here’s using a question to highlight an inconsistency that demands further exploration:</p><p><em>Serverless computing has become a hot topic in developer communities. The use of ephemeral containers eliminates the need for always-on infrastructure. But the real payoff for serverless is greater code simplicity and developer efficiency. Sounds great! Except the open-source serverless framework space is crowded and complex. </em><strong><em>Each unique offering approaches functions differently, with varying methods for triggering, scaling, and event formatting.</em></strong><em> </em><strong><em>How is that efficient?</em></strong></p><p>Articulate the pain up front. Make it clear that you understand the audience’s problems and questions.</p><h3>Build interest and credibility with some nuanced facts and a point of view</h3><p>You’ve made that connection with your prospective audience in the opening paragraph. Now you need to build trust and interest. You don’t want to go into the full detail of your talk. But you also don’t want to distill out so much that you’re left with generic platitudes.</p><p>The whole point of your talk or webinar is to leave the audience smarter. The second paragraph of your abstract is a moment to teach something to your audience even before they attend. Give the audience a taste for what kind of expert you are. Share some facts, some observations, or some opinions.</p><p>Here’s an example that starts with a simple definition and adds observations:</p><p><em>Continuous integration is the automation of building and testing new code. Development teams that use CI can catch bugs early and often; resulting in code that is always production ready. Compared to manual testing, CI eliminates a lot of toil and improves code quality. At the end of the day, it’s those code defects that slip into production that slow down teams and cause apps to fall over.</em></p><p>Here’s another example that hints at what will be covered, but with specific examples:</p><p><em>There are a lot of misconceptions about cloud portability. The term itself implies moving workloads with no work (not true), suggests completeness in what’s moved (mileage may vary), and ignores the laws of data gravity (at your peril!). Platforms, like Pivotal Cloud Foundry (PCF), can make it much simpler to move workloads between clouds. But PCF fits within a broader set of concerns and decisions that need to be made.</em></p><p>Provide some background in a sentence. Be specific about the challenges or benefits you plan to cover in your talk. Make your point of view clear. Use plain language to describe complex ideas.</p><h3>Finally, list what the audience will learn</h3><p>You’ve given readers a small taste of what the knowledge they will tap into. Now, step back and list what they will learn. What are the questions they can expect to have answered in the talk? Three to five bullet short bullet-points keeps it easy to scan.</p><p>Using question words helps align your language with what the audience is seeking. It also reminds you of other questions you may want to answer. For example, if you are preparing a talk about <em>how</em> to use a tool, consider also answering <em>when</em> or <em>where</em> the tool should be used. Or <em>why</em> use something. With anything that involves change, don’t forget to think about <em>what</em> to measure and <em>how</em> to measure progress. Thinking through your question words helps you cover your topic comprehensively.</p><p>Here is an example with a clear point of view and short list, using question words:</p><p><em>The journey to continuous integration maturity has some requirements. Join Pivotal’s James Ma, product manager for Concourse, and Dormain Drewitz, product marketing to learn about:</em></p><ul><li><em>How Test-Driven Development feeds the CI process</em></li><li><em>What is different about CI in a cloud-native context</em></li><li><em>How to measure progress and success in adopting CI</em></li></ul><p>Here’s one that’s heavy on “how” questions, sometimes combined with “when” questions:</p><p><em>You’ll learn:</em></p><ul><li><em>How and when — and when *not* — to cluster RabbitMQ</em></li><li><em>How to optimize resource consumption for better performance</em></li><li><em>When and how to persist messages</em></li><li><em>How to do performance testing</em></li></ul><p>Here’s an example that does not use question words, but has concise outcomes:</p><p><em>Using a stringent methodology, Forrester highlights some of the benefits that Pivotal customers realized in areas such as:</em></p><ul><li><em>Operational efficiency</em></li><li><em>Increased developer productivity</em></li><li><em>Decreased downtime / higher quality software</em></li><li><em>Shortened release cycles</em></li></ul><p>You opened with the audience’s pain. Then you shared some details and your point of view. Now you come back to the audience and their goals. The last section should make it clear what they will learn.</p><h3>Keep your promise</h3><p>As much as I told you not to overthink and belabor the abstract, it is a commitment. Freedom from trying to perfect what your write is not freedom from responsibility for what you write. The abstract is a promise to the audience about what they will learn. Refer back to it as you develop your presentation to make sure you are keeping with your promises.</p><p>If something has changed from the time you published or submitted the abstract, address that directly. You are learning and keeping your content fresh, which is great! Acknowledging that shows respect for your audience and builds your credibility.</p><p>Was this helpful? Do you think I left something out? Let me know here or on <a href="https://twitter.com/DormainDrewitz">Twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66ae959be2e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stealing Keyboards and Other Leadership Techniques]]></title>
            <link>https://medium.com/@dormaindrewitz/stealing-keyboards-and-other-leadership-techniques-e18022123370?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e18022123370</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Sat, 29 Sep 2018 00:42:27 GMT</pubDate>
            <atom:updated>2018-09-29T00:42:27.000Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xpPLBrr3V-ri801H_EVFwg.jpeg" /><figcaption>Image Credit: <a href="https://www.flickr.com/photos/elisfanclub/347525552/in/photolist-wHaeS-bxTrbN-6y7dRb-oiFHFy-7LiRU8-tfTcFJ-7LjeS4-2vGuA-47dnYK-4WrmRD-hMNUd-aNXewX-HdeRa-9eyLd5-bc1djK-7Dv6JR-9JfDGw-729dPG-51Cy3N-4qyozZ-egQzZH-QiJm-J3iguH-b1qEA-e9Kru-knMJ6Z-89Dkyq-9JoCic-5f8zvT-5w3By8-aCdapn-fyWHR-r7s7ro-bswqbL-9gdeCP-4kKxhD-qCQYZp-6EhCZT-YGcxWm-9KjnM7-AdNAF-4nNQZr-7HZS4d-6vEyXS-95Pq4F-wuu2Qn-7HPi2L-56wnaQ-5uEbNj-8KR6B">Eli Duke</a> (<a href="https://creativecommons.org/licenses/by-sa/2.0/">CC BY-SA 2.0</a>)</figcaption></figure><h3>More evidence for the Secrets of Successful Cloud Foundry Adopters</h3><p>Call it confirmation bias (it is), but at <a href="http://springoneplatform.io/">SpringOne Platform</a> I couldn’t help but notice new examples of “<a href="http://content.pivotal.io/secrets">The Secrets</a>.” This growing list of “secrets” are patterns across companies digitally transforming using PCF. They surface as I listen to Pivotal’s customers describing their journeys, but they transcend vendor. Anyone leading a digital transformation journey can take note.</p><p>Here’s my observations from user talks at SpringOne Platform 2018, mapping back to these patterns.</p><p><strong>1. Give teams space to change</strong></p><p>This initially came to my attention as Pivotal customers highlighting the importance of doing the Pivotal Dojo. But it applies regardless of vendor. It’s really about making any change to a team. To start working in a new way, you have to stop working in an old way.</p><p>I often highlight this to executives and leaders. It’s often managers that fail to explicitly give their team permission to change. Unless you’re employing Bartleby the Scrivener, they need help saying “no” to their old work as you ask for the new. But the reality is that resistance to this change can come from all levels.</p><p>In Ryan Johnson’s talk, he described how the teams were reluctant to work in a new way. The Accenture Pivotal Business Group (APBG) in Columbus, Ohio was adopting agile and extreme programming practices, including pair programming. So, overnight, he took away half the monitors and keyboards to force the teams to pair. Now that team can complete tasks in hours which take other teams days to complete.</p><h3>Dormain Drewitz 🧟‍♀️ on Twitter</h3><p>I stole half the laptops and keyboards over night so the next day they had to pair program/ Ryan Johnson on extreme but effective tactics to change how teams were developing at @Accenture @pivotal business Group at #SpringOne</p><p>It’s an extreme example, but it speaks to the role of leadership in facilitating a new way of working.</p><p><strong>2. Pick an application</strong></p><p>In parenting, I *try* to practice a technique called “name it to tame it”. If you can help kids use words to describe their emotions, you move closer to a calm state. I’m starting to think it’s the same with applications — you need to be able to name the applications that you want to tame!</p><p>For example, I recently heard about a CIO that was excited about the capabilities of the platform. They mandated that their team get ten applications on PCF within a quarter, but they didn’t care which ones. Not surprisingly, the team didn’t achieve that goal. (Don’t worry, they have come around and made a lot of progress since)</p><p>In contrast, I liked the focus of George Loyer (<a href="http://twitter.com/gloyer">@gloyer</a>), Director of Technical Operations at Stubhub. He was specific about the progress made about their storefront application. And he highlighted three more applications — Search Events, Checkout, and Mobile Ticket Transfer — that are on the roadmap for modernization.</p><h3>Ronak Kumar Mallik on Twitter</h3><p>Wow. Value Delivered. Love seeing these outcomes (cool to see @pivotalcf as a part of this larger story) @StubHub @gloyer #SpringOne @s1p</p><p>Another interesting from this list of applications on deck is the common need for experimentation. Experimentation requires an ability to iterate at high velocity. Otherwise, it’s risky and so it’s avoided.</p><p>Which brings me to a related topic. I’m getting more questions from folks about how to decide what runs in PAS versus PKS. After an <a href="https://content.pivotal.io/webinars/may-31-debunking-myths-about-cloud-portability-webinar">enlightening talk with Josh McKenty earlier this year</a>, I recommend folks think about their velocity needs when making this decision. Does the business want to be able to experiment around this application? If yes, then you want to choose an abstraction that supports higher velocity through higher developer productivity. If not, then a lower and slower abstraction may do just fine.</p><p>So, as we move to a multi-abstraction world, that focus — that ability to name the apps we want to tame — continues to be a key to success.</p><p><strong>3. Make the new way to go viral among developers</strong></p><p>Ongoing developer enablement seems to go overlooked and unfunded. Perhaps it’s the prevailing project-oriented mentality. Perhaps it’s the derth of leaders that adopt the <a href="https://blog.careerlark.com/giving-great-feedback-g-is-for-growth-oriented-cc87cfffc924">growth-oriented mindset</a>. Either way, many companies don’t fully realize the full return on their technology or consulting investments because they don’t include enablement.</p><p>I confess that I didn’t make the session that probably would have offered great ideas for enablement. I’m looking forward to the replay video of <a href="https://springoneplatform.io/2018/sessions/teaching-tdd-to-different-learning-styles">Tiffany Larsen of HCSC on teaching TDD to different learning styles</a>. Not just because <a href="https://builttoadapt.io/why-tdd-489fdcdda05e">TDD supports the necessary assurance to release code more frequently</a>. But because HCSC has been doing a lot of great work in their digital transformation, including developer enablement.</p><h3>Michael McNichol on Twitter</h3><p>Tiffany Larsen schooling the class on TDD and styles of learning @s1p Are you an auditory, visual, kinesthetic learner....is your pair? Great job showing how to be empathetic through countless hours of your own personal experience! #SpringOne #womenintech #crushsoftware</p><p>It’s also worth noting that <a href="https://content.pivotal.io/analyst-reports/hack-your-culture-to-drive-quality-and-devops-success">Gartner recently published a recommendation to budget for tool and practice adoption</a> when adopting DevOps. Leaders, take note.</p><p><strong>4. Metrics and measuring</strong></p><p>Evidence of value stream mapping abounds! In the spirit of “<a href="https://twitter.com/DormainDrewitz/status/927830042461331456">figure out how many tickets it takes to get something done and make the number go down</a>”, George Loyer shared the reduction in tickets to get Stubhub’s applications into production.</p><h3>Dormain Drewitz 🧟‍♀️ on Twitter</h3><p>Before: Typical for a small software project to require 20-25 tickets to get into production Now: Storefront team can push into production with 1-2 tickets Great early progress at @StubHub shared by @gloyer at #SpringOne!</p><p>Then, Greg Meyer (<a href="http://twitter.com/greg_meyer93">@greg_meyer93</a>) at Cerner shared four value stream mapping use cases. Use cases ranged from restoring a development database to building a blue-green deployment environment. I enjoyed how his examples illustrated how granular these value maps can be. I also, of course, enjoyed seeing how recovering from a production node loss shrunk from 3 hours and 4 people to 15 minutes with no people.</p><h3>Dormain Drewitz 🧟‍♀️ on Twitter</h3><p>From: 7 days and 2-3 resources To: 4hours and 1 resources Oh, and data fully restored, too #valuestream map of restoring a dev database at @Cerner from @Greg_Meyer93 at #SpringOne</p><p>Finally, there were plenty of great metrics shared. Highlights include zero hours planning security patches at Dick’s Sporting Goods via Jason Williams (<a href="http://twitter.com/jwilliamspgh">@jwilliamspgh</a>). Speaking of zero, Siew Choo Soh (<a href="http://twitter.com/siewchoosoh">@siewchoosoh</a>) shared that DBS has had zero minutes of downtime on PCF for the last 2 years.</p><h3>Brian McClain on Twitter</h3><p>These are always my favorite slides to see. Real, measured results from @DICKS Sporting Goods that represents a total change in development AND culture. Especially love that ops to dev ratio and zero time spent on security patches thanks to BOSH and PCF #SpringOne</p><h3>Dormain Drewitz 🧟‍♀️ on Twitter</h3><p>Major releases: from 6m to under 4w Infra provisioning: from 1w to intraday Downtime: 0 minutes in 2 years @siewchoosoh shares @dbsbank results with @pivotalcf at #SpringOne</p><p><strong>5. Don’t Launch with the Avengers</strong></p><p>The flip side to not stacking the deck with heroes and super stars, is who you <em>do</em> put on your team. Diversity of skills and experience on these early teams is useful. It brings fresh ideas and perspectives to problem solving. So, how do you get a diversity of skills and experience onto your team?</p><p>Siew Choo Soh shared a recruiting practice that DBS has used for the last two years. She noted that this has brought in diverse candidates from outside of banking. These candidates would have been difficult for the bank to recruit through traditional methods. Check out the replay of her talk to hear about how they are iterating on their hackathon approach.</p><h3>Dormain Drewitz 🧟‍♀️ on Twitter</h3><p>Now THIS is how you recruit! @siewchoosoh shares how @dbsbank has transformed how they recruit and attract large groups from diverse backgrounds #SpringOne</p><p><strong>6. Invest in test automation</strong></p><p>The corollary to investing in testing automation is that you have the tests. Who, when, and how are you going to write those tests? When you combine the need for tests to confidently make changes with a value-stream mapping exercise to identify and eliminate waste, you have a strong case for test-driven development (TDD).</p><p>Boeing’s Sophia Bright noted how TDD and other practices fit into the company’s stringent safety controls. They provide a framework for building checks into the software development process. And that helps the broader organization accept going faster.</p><h3>Dormain Drewitz 🧟‍♀️ on Twitter</h3><p>Using paired programming, using #TDD, building checks in along the way, it answers the question of how are we going to build quickly and safely/@Boeing&#39;s Sophia Bright at #SpringOne</p><p>DBS has done engagements with Pivotal Labs, learning various Agile and XP practices. But when asked about whether they were still practicing pair programming, Siew Choo said they leave that up to individual teams. TDD, however, is non-negotiable.</p><h3>Dormain Drewitz 🧟‍♀️ on Twitter</h3><p>TDD is something we strictly enforce because it allows us to bake quality into the process/@siewchoosoh talks about what @dbsbank has retained from their @pivotallabs experience #SpringOne</p><p>Another interesting observation about automation pipelines in general, was the cost of retrofitting. Not surprisingly, if you can, invest in pipelines from the beginning, you’re better off. But what Cory Jett (<a href="http://twitter.com/coryjett">@coryjett</a>)also noted in his talk, alongside William Marchlewski (<a href="http://twitter.com/stlguitarist">@stlguitarist</a>) at Mastercard, was the ongoing pipeline maintenance. Just like savings habits or eating your veggies, tending to your pipelines is an undeniably good habit.</p><h3>Dormain Drewitz 🧟‍♀️ on Twitter</h3><p>Retroactively building pipelines is way harder... and all pipelines require discipline and dedication/@CoryJett shares some lessons learned from working with Mastercard at #SpringOne</p><p><strong>7. Be bold</strong></p><p>Sometimes bold feels crazy. For Darryl Smith and Alfred Brown, Site Reliability Engineers with the US Air Force, an order to deliver PCF in a remote location within 150 days seemed crazy at the time. But, along with Lt. Davis Gunter, they managed to contract, procure, hire, build, and ship in 148 days. At one point, they had to set up an IaaS environment in an air-gapped environment in 4 days. They were long days, but they did it.</p><h3>Yatin Khadilkar on Twitter</h3><p>Amazing story of Lt. Davis Gunter and his platform team at @usairforce delivering fully functional app on production grade @pivotalcf platform on other side of the world in 148 days at #SpringOne #KesselRun</p><p>These types of stretch goals can make people uncomfortable. Some leaders are uncomfortable with making others… uncomfortable. But, when done right, some temporary discomfort are part of the growth process.</p><p>The effort required to meet bold goals can be unsustainable, which needs to be kept in perspective. But when a team meets or beats a bold goal it can unite the team in new ways. It can also galvanize their commitment to the broader mission. And, of course, it can accelerate the teams progress by reaching a milestone quickly.</p><p>The flip side of setting bold, stretch goals for a team is practicing gratitude for the effort of the team. Alfred Brown put it best on stage when he said, “You have to celebrate the wins.”</p><p>***</p><p>Is that it? Seven secrets and we’re done? Not quite. I’ll be revealing <a href="http://sched.co/GATw">the next couple of “secrets”</a> at CF Summit in Basel, October 10–11. You’ll have to register <a href="https://www.regonline.com/registration/Checkin.aspx?EventID=2247021&amp;utm_source=red&amp;utm_medium=mem&amp;utm_campaign=eu18&amp;utm_content=reg">here</a> (and show up) to hear them first!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e18022123370" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Death and DevOps]]></title>
            <link>https://medium.com/built-to-adapt/death-and-devops-dd0517605802?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd0517605802</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[pixar]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Tue, 19 Dec 2017 19:01:02 GMT</pubDate>
            <atom:updated>2019-06-10T16:52:55.203Z</atom:updated>
            <content:encoded><![CDATA[<h4>Dealing with unfortunate things shape a culture.</h4><p><em>UPDATE: You can now watch a talk version of this article from Monktoberfest 2018. See link at the end.</em></p><p>There are certain universal human experiences that transcend cultures. The birth of a child. The coupling of two people in marriage. And death. From baptisms to burials, how we handle these moments is a reflection of our culture.</p><p>For better or worse, how death is dealt with leaves a lasting legacy that we can study. You can learn a lot about a culture — a mindset — by how people treat their dead. In medieval Europe, bodies were buried intact, facing east, so that they could rise facing Jerusalem upon the Resurrection. In Judaism, the dead are typically buried within a day and are never left unattended until burial. And, if you saw <em>Coco</em>, you saw a version of how families remember and honor the dead in Mexico.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vz1co6IVo0ivgkei." /><figcaption>Image from Pixar’s Coco.</figcaption></figure><p>So, what does that all have to do with DevOps?</p><p>Well, even in the DevOps world, things die. Servers die. VMs die. Applications die. With the right kind of automation and abstraction, these events matter less. But complex events and human error still cause outages, even at the most sophisticated of cloud-native companies. So, what happens when there’s an outage?</p><p>In his breakout at SpringOne Platform, Matt Curry rattled off four steps for dealing with an outage:</p><h3>Dormain Drewitz on Twitter</h3><p>When you have an outage: 1) apologize and mean it 2) know what went wrong 3) articulate what you&#39;re going to do to prevent it in the future 4) apologize again and still mean it @mattjcurry #SpringOne</p><p>I noticed that of all my live-tweeting of SpringOne Platform, that tweet was getting more reactions. This got me wondering: Why does this four step process resonate with people? Then it hit me: this is a concrete example of DevOps “culture.” And we need those concrete examples.</p><h3>What are your rituals?</h3><p>At SpringOne Platform, many speakers said cultural change was the hardest part of their transformation. As Niki Allen from Boeing <a href="https://www.amazon.com/Culture-Eats-Strategy-Lunch-Coffman/dp/0615577962">quoted</a>, “Culture will eat strategy for lunch.” But for all the talk of how important culture is for transformation, examples were scarce — there were a few ping-pong references and photos of open office spaces.</p><p>But, as Ben Horowitz and Jason Rosenthal discussed on <a href="https://a16z.com/2017/02/19/startups-pivots-culture-decisions-timing/">this great podcast episode</a>, culture really matters when things go wrong. Culture has a lot to do with how we deal with the hard stuff, from the day-to-day to the life changing. The way most societies deal with hard stuff is a set of rituals. Rituals help us know what to do in really stressful situations (like a death) when it can be hard to think clearly.</p><h3>Dormain Drewitz on Twitter</h3><p>Culture doesn&#39;t matter as much when things are going well. It matters when shit hits the fan https://t.co/SgHN8suCLO</p><p>Google has a lot of ritual around failure. Listening to Andrew Clay Shafer’s digest of the Google SRE book, I got the sense that the culture around learning from failure was borderline obsessive. It’s like a mourning process, one that ultimately lets people move on.</p><h3>Dormain Drewitz on Twitter</h3><p>You had me at &quot;failure porn&quot; &amp;amp; &quot;wheel of misfortune&quot; /@littleidea reviews the GoogleSRE book https://t.co/iV2cZOF5sb</p><p>You need to have a set of rituals for when things go wrong. They may not look like Matt’s list and you may not even be aware of them. These rituals may vary from department to department, but they exist. They also may not be healthy and may be creating friction to change.</p><p>For example, your rituals for an outage may involve an urgent conference call. That turns into a blamestorming session, where a couple people or teams get thrown under the bus. Once the issue is resolved, a manager writes an email to only execs with a high-level overview. After that, the issue is considered buried and put to rest, only spoken of again on the next blamestorming call.</p><h3>Defining a new way to mourn the outage</h3><p>Unfortunately, you can’t just declare a new set of rituals and claim a cultural change. I mean, you could, but it probably wouldn’t work very well. If you want to have any hope of changing a culture, you have to first understand it. Then you can introduce new rituals to change the culture by teaching and practicing.</p><p><strong>1) Learn and observe.</strong></p><p>Abigail Stason has an insightful <a href="https://static1.squarespace.com/static/5902179c1e5b6c0e24ff9329/t/59c99b5780bd5e1a6ea9ab3a/1506384728142/Commitment+Framework.pdf">framework for what she calls Conscious Commitment</a>. It’s intended (to my knowledge) for individuals, but can apply to teams and organizations as well. She starts with noticing patterns of what’s already happening, then allowing time to really study the behavior.</p><p>Observe what happens when something goes wrong. Include the good, bad, and ugly. Document the steps. Figure out what triggers different stages in the process. From there, you will be in a better position to recognize this pattern — and if need be head it off — once you’ve committed to a new set of rituals.</p><p><strong>2) Define some new rituals and iterate.</strong></p><p>Matt’s four steps are great: short and simple, making them easy to absorb as a multi-step process. They also emphasize humility and empathy, with can be easier said than done. That takes practice.</p><h3>Ash Hathaway 💁 on Twitter</h3><p>@mcrowther talking about culture and security along with values, behaviors, and practices. #SpringOne #pivotal</p><p>You can also take inspiration from <a href="https://sweetcode.io/gitlab-outage-respond-downtime/">analysis of public outages, like one at GitLab</a>. <a href="https://landing.google.com/sre/book.html">Google’s SRE book</a> sounds like a good source of ideas (full disclosure: I haven’t read it). But, <a href="https://www.theregister.co.uk/2017/11/17/do_the_devops_not_here_no_thank_you/">be careful not to adopt concepts, like “blameless post-mortem,” without internalizing what they mean</a>.</p><p>I’m going to go out on a limb here and say there’s a lean approach to defining new cultural rituals as well. Don’t try to craft the perfect outage response guide. Identify a couple things that you think would be an improvement and start to try them out. See how they go. Learn from them and change or add to them over time. When part of your culture is continuous improvement — iterating on solutions — you move faster because you don’t get stuck in analysis paralysis trying to nail it the first time.</p><p><strong>3) Teach and practice.</strong></p><p>So, now you have a couple new things you want to see happen in the event of an outage. How do you make that happen? You need to educate people. You can’t expect them to know any other way than what they are already doing.</p><p>We aren’t born knowing what to do at a funeral. For example, I had my first experience with a Jewish funeral this summer. There were little, printed handouts at all the seats of the temple. Each one explained the practices, along with the translated Hebrew prayers. The rabbi explained a lot of what was happening and why as the funeral progressed. Elder members of the community leaned over to fill me in on this or that. Having never participated in that part of the culture, there were several ways for me to learn.</p><p>Write down the “this is what we do when there’s an outage” list or manifesto. You’re (probably) not writing it in stone, so it can change. Don’t wait for an outage to spring the list on people. To lift an idea from Adrian Cockcroft, you may even want to run a few fire drills where you can reinforce new rituals.</p><h3>Daniel Bryant on Twitter</h3><p>People are the most important part of chaos testing. However people need training. Ask yourself who runs the &#39;fire drill&#39; for IT?&quot; @adrianco #qconsf</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJubjEkJA0_g%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJubjEkJA0_g&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJubjEkJA0_g%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1bf8165da4b6f563e96fbe9c8094eb74/href">https://medium.com/media/1bf8165da4b6f563e96fbe9c8094eb74/href</a></iframe><h4>Enough death. What are some happy rituals?</h4><p>Okay, okay. I get that death and mourning are heavy topics. I’m asking you to put your cultural anthropologist hat on (<a href="https://en.wikipedia.org/wiki/Indiana_Jones#/media/File:Indiana_Jones_in_Raiders_of_the_Lost_Ark.jpg">looks like this</a>). There’s something to be learned from cultural response to death and your culture around outages. Both are stressful events that are a question of when, not if, they will happen.</p><p>But we can also apply the same thinking to other moments. What about the “birth” of a new product? How do you celebrate it’s launch? How does the community support the new “parents”? These are questions for another post, but I’ll leave you with this thought: If you go to observe your rituals for new products and can’t find any, is your birth rate too low?</p><p><em>What are some of your team’s rituals around outages, new products, or something else? Let me know by responding to this post.</em></p><figure><a href="http://builttoadapt.io/"><img alt="" src="https://cdn-images-1.medium.com/max/71/1*HmnjOtABFnaIfxz9jIBVSg.png" /></a></figure><p><em>Change is the only constant, so individuals, institutions, and businesses must be </em><a href="http://builttoadapt.io/"><em>Built to Adapt</em></a><em>. At</em> <a href="http://pivotal.io/"><em>Pivotal</em></a><em>, we believe change should be expected, embraced, and incorporated continuously through development and innovation, because good software is never finished.</em></p><figure><a href="http://pivotal.io/"><img alt="" src="https://cdn-images-1.medium.com/max/435/1*YSGFr6g3OYR8MQbcXEeXWQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd0517605802" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/death-and-devops-dd0517605802">Death and DevOps</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Transformation Anti-Patterns]]></title>
            <link>https://medium.com/@dormaindrewitz/digital-transformation-anti-patterns-81f6190e2c4c?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/81f6190e2c4c</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cloud-foundry]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[pivotal]]></category>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Thu, 07 Dec 2017 08:53:30 GMT</pubDate>
            <atom:updated>2017-12-07T08:53:30.427Z</atom:updated>
            <content:encoded><![CDATA[<h4>Takeaways from SpringOne Platform 2017</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*vfBLo2AgEVaB0V_jTkc3RA.png" /></figure><p>Day 2 at SpringOne platform was a whirlwind of keynotes and more user-led breakouts than one can physically attend. <a href="https://medium.com/@dormaindrewitz/secrets-of-successful-cloud-foundry-adopters-232193111b18">I’m always on the look out for patterns</a> in how users are adopting technologies. This time, I looked for the behaviors to avoid: the anti-patterns.</p><h3>Anti-pattern #1: Assemble “<em>The Avengers”</em> of a Team</h3><p>When the rubber meets the road for kicking off a change to your software practices, you need people. This could be for standing up your PCF platform ops team, or just building a DevOps team in general. Assembling that team might feel like you’ve got to assemble <em>The Avengers</em>.</p><p>But modeling your DevOps team on <em>The Avengers</em> is an anti-pattern. Why? Three reasons came up during day 2.</p><p>First, you’re not looking for heroes. When asked about changing job roles, Dean Parke of Discover noted a shift in emphasis. The “maturity model” titles still existed, but the focus is on equality as a team over seniority. This harbors the teamwork over heroism.</p><p>Second, you want to normalize the new. <a href="https://twitter.com/jonnio20">Jon Osborn</a> of Great American Insurance Group, had a session packed with great tips. One that stood out was to not pack your team with “rock stars” because it lets others dismiss their work. If your team starts, say, releasing software twice as often, you want everyone to feel like they could do that too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/1*7ytJ1eoTgjUQGeJFWxMmAQ.png" /><figcaption><a href="https://twitter.com/DormainDrewitz/status/938191034563010560">https://twitter.com/DormainDrewitz/status/938191034563010560</a></figcaption></figure><p>Third, you want diversity. Okay, okay, so <em>The Avengers</em> are sort-of diverse… Thor’s from another world, Captain America is from another era, and Black Widow is… female… But more importantly, they bring different skills to the table. That’s the kind of diversity that both <a href="https://twitter.com/mattjcurry">Matt Curry</a> of Allstate and Jon Osborn highlighted. Different career stages bring important diversity of perspectives.</p><h3>Anti-pattern #2: Skip the Testing and Release Automation</h3><p>Back at Cloud Foundry Summit in June, I spoke with a customer running PCF at scale who told me he didn’t care if his developers paired. He only cared that they had automated their tests. That was my first clue at how important this was. Here at SpringOne Platform, Ford, <a href="https://www.youtube.com/watch?v=5wokS2VySoQ&amp;t=3s">Scotiabank</a>, and others all highlighted the importance of automating CI/CD.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*htxKyq7TkygyEZpGJ8ZvLA.png" /><figcaption><a href="https://twitter.com/bglithero/status/938232014683095043">https://twitter.com/bglithero/status/938232014683095043</a></figcaption></figure><p>From the platform ops perspective, automating platform updates has life-changing implications. <a href="https://twitter.com/osukirkland">Brian Kirkland</a> at Verizon can watch Monday Night Football again, despite “Maintenance Mondays.” And this is taking patching frequency from every 6 months to weekly for twelve foundations.</p><p>Meanwhile, Bryan Kelly of Cerner was visibly excited as he described a recent automated platform update. In twelve hours to move 220 virtual machines across sandbox, non-production, and finally production. But zero humans were involved. Cerner is using PCF Pipelines, a collection of Concourse pipelines for installing and updating PCF.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/1*I4laaTEzDdEpxmoNPKg4Pw.png" /><figcaption><a href="https://twitter.com/DormainDrewitz/status/938181445176115200">https://twitter.com/DormainDrewitz/status/938181445176115200</a></figcaption></figure><p>While the endgame of pipeline automation becomes obvious, getting there isn’t. It’s daunting to imaging writing all the tests needed to automate all your application deployments. But, like anything, it starts with small steps. Or, as Matt Curry from Allstate put it, as incremental deposits into an interest-earning account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*-NU-beKuoQMpMKDLyP26Og.png" /><figcaption><a href="https://twitter.com/DormainDrewitz/status/938171272768262144">https://twitter.com/DormainDrewitz/status/938171272768262144</a></figcaption></figure><p>You may not need all the tests and release automation on Day 1, but begin investing early.</p><h3>Anti-pattern #3: Go Slow, Stay Small</h3><p>There’s a natural tendency to take small, cautious first steps when doing something new. But PCF users who were reaping major benefits from the platform didn’t stay small. Liberty Mutual and Comcast were all explicit about making bold moves.</p><p>In his keynote, <a href="https://www.youtube.com/watch?v=vabrFqYKNeI">John Heveran reiterated the big goals that Liberty Mutual set for itself</a>. Then he described how the company converted ten applications into microservices running on PCF in ten weeks. They next tackled an application that supports $4bn of their $10bn in commercial insurance revenue. That progressively bolder approach has yielded 10% of workloads on PCF, deploying at least weekly if not daily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*MBhIzSbJuy-YhlgJyvBoCQ.png" /><figcaption><a href="https://twitter.com/rseroter/status/938119761208139777">https://twitter.com/rseroter/status/938119761208139777</a></figcaption></figure><p><a href="https://twitter.com/findneville">Neville George</a> of Comcast distilled a number of lessons from scaling PCF to 9k apps and 2100 developers. Second on the list was to “Be Ambitious” and bring big apps onto the platform. Bigger apps bring more developers with them, force more standardization in the process, and create strong endorsers. Landing a big app is the antidote to getting stuck in “science project-land.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*4jK22amQscXSZVu_KMBRyg.png" /><figcaption><a href="https://twitter.com/AlexEvade/status/938129659232948225">https://twitter.com/AlexEvade/status/938129659232948225</a></figcaption></figure><p>Everything usually starts as a pilot project, but when it goes well, you want to scale. To scale you need to think bigger.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81f6190e2c4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secrets of Successful Cloud Foundry Adopters]]></title>
            <link>https://medium.com/@dormaindrewitz/secrets-of-successful-cloud-foundry-adopters-232193111b18?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/232193111b18</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[cloud-foundry]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Mon, 19 Jun 2017 18:13:21 GMT</pubDate>
            <atom:updated>2017-06-19T18:13:21.614Z</atom:updated>
            <content:encoded><![CDATA[<h4>Takeaways from Cloud Foundry Summit Silicon Valley 2017</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VMVaw_4W07nuDb00yqkkzQ.jpeg" /></figure><p>1100 deploys a month. 50% improvement in time to market. Same day bug fixes with no downtime. 1500 production services. MVP prototypes in four weeks. The measured effects of using Cloud Foundry (and associated people and process changes) are compelling.</p><p>But how did they get there? After all, change is hard. Picking the platform is the easy part. How did they get started? How did they gain momentum?</p><p>At the Cloud Foundry Summit in Santa Clara last week, each company had it’s own story. But after two and a half days of keynotes and presentations, some patterns emerged.</p><h4>Do you Dojo?</h4><p>Where to start? For writers, it’s the torture of the blank page. For platform operators? It’s the torture of having selected Cloud Foundry, but not yet having it running. <br> <br>One word came up again and again from users that had achieved escape velocity: dojo. A “dojo” is literally a martial arts studio, where students train and practice. It’s not the actual place of battle, and the training is as much mental as it is physical. At Pivotal, it’s a 6–8 week engagement that’s more about teaching teams *how* to use the platform than just installing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BGFnn3gztxH2Mhp7pil0jA.png" /><figcaption>Garmin’s second dojo: <a href="https://schd.ws/hosted_files/cfsummit2017/9e/CF-Summit-2017-formatted.pdf">https://schd.ws/hosted_files/cfsummit2017/9e/CF-Summit-2017-formatted.pdf</a></figcaption></figure><p>At Garmin, it took a couple of tries for the practice to pay off. According to Jonathan Regehr (<a href="http://twitter.com/jonathanregehr">@jonathanregehr</a>) and James Stueve (<a href="http://twitter.com/james_stueve">@james_stueve</a>), the company showed up at at it’s second dojo ready to change. And the foundation they set up in that dojo is still running in production after over a year.</p><p>Melissa Chapman (<a href="http://twitter.com/Bluesky142">@Bluesky142</a>) and Brendan Aye of T-Mobile credited their first dojo as setting the stage for DevOps. The team used to take seven months and 72 steps to release new code. Now they’re fixing bugs same-day with zero downtime. The dojo provided a place to practice shared responsibility, which made it real.</p><p>Another customer I spoke to credited the dojo with taking six months off the time to get their first foundation deployed. Having experts on the ground ready to work proved to be a forcing function for their company. Now they’re enjoying the benefits of applications in production on the platform.</p><blockquote>Having experts on the ground ready to work proved to be a forcing function for their company.</blockquote><p>Large companies need help achieving lift-off in operating the Cloud Foundry platform. It’s not a technology problem. The organizational inertia grounding a company in the status quo needs to be offset by a powerful force. The immersive nature of the dojo forces changed behaviors for would-be platform operators.</p><h4>Pick an app</h4><p><a href="https://builttoadapt.io/stop-trying-to-monetize-your-data-a61791fa5d98">I’ve written before about orienting work around a specific outcome and application</a>. But I couldn’t have illustrated that point any better than Mojgan Lefebvre (<a href="http://twitter.com/mojganlefebvre">@mojganlefebvre</a>), SVP and CIO at <a href="https://pivotal.io/liberty-mutual">Liberty Mutual</a>. In her keynote, she walked through how the 100 year old insurance company released an app for brokers in the $240mn Australian market in six months. And that app performed better than industry averages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*UC6Z5Rc02ImGmzJujfHk1w.png" /><figcaption><a href="https://twitter.com/DormainDrewitz/status/875038341946904576">https://twitter.com/DormainDrewitz/status/875038341946904576</a></figcaption></figure><p>But picking an app to jump start use of Cloud Foundry doesn’t have to be greenfield. T-Mobile chose their GetUsage application — a Java monolith with over 1,000 functions running on WebLogic. Within three months, they had it rebuilt as a Spring app running on Cloud Foundry taking 100 percent of production traffic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*fkM90jFuHudKOqiqOtcixw.png" /><figcaption><a href="https://twitter.com/DormainDrewitz/status/875425578094022656">https://twitter.com/DormainDrewitz/status/875425578094022656</a></figcaption></figure><p>Arguably, picking an existing application can provide a forcing function for faster change. That’s what Comcast did, picking three core applications to migrate first to Pivotal Cloud Foundry. That allowed them to bring forty percent of traffic on to the platform in their first year and paving the way for the remaining sixty percent. Today, Comcast has over 1500 developers deploying to the platform and over twelve thousand app instances supporting hundreds of millions of transactions per day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*aggfIJ6zO84SoJpT71KvDA.png" /><figcaption>Comcast keynote panel: <a href="https://twitter.com/DormainDrewitz/status/874782459568599040">https://twitter.com/DormainDrewitz/status/874782459568599040</a></figcaption></figure><h4>Feed the groundswell for the developer “tipping point”</h4><p>Another recurring theme was the rapid acceleration in adoption by developers within companies. Several companies described a “hockey stick” in the volume of applications being deployed to the platform. Home Depot noted a couple of months that saw month over month doubling of activity. Greg Otto (<a href="http://twitter.com/iamgregotto">@iamgregotto</a>) of Comcast echoed that with a graph of applications on an accelerating slope.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rhkD-A1j0sfrsKBkx2Pkww.png" /><figcaption>Comcast application growth on Cloud Foundry: <a href="https://schd.ws/hosted_files/cfsummit2017/21/2017-06-13%20-%20CF%20Summit%20-%20Greg%20Otto%20Comcast%20CF%20Journey%20-%20Part%202%20%28final%29.pdf">https://schd.ws/hosted_files/cfsummit2017/21/2017-06-13%20-%20CF%20Summit%20-%20Greg%20Otto%20Comcast%20CF%20Journey%20-%20Part%202%20%28final%29.pdf</a></figcaption></figure><blockquote>Several companies described a “hockey stick” in the volume of applications being deployed to the platform.</blockquote><p>But these “tipping points” were not purely accidental, nor were they complete chaos. Education on cloud-native principles was often cited by practitioners with large-scale deployments. Garmin has launched Garmin Labs to immerse teams for 4–6 weeks at a time and “see what sticks”. Verizon noted an approach to “hammer [developers] with 12 Factor”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*SepZIgxQjKcNHuI8_-ekLg.png" /><figcaption><a href="https://twitter.com/littleidea/status/875125224752111617">https://twitter.com/littleidea/status/875125224752111617</a></figcaption></figure><p>T-mobile stressed the importance of outreach and consistency. T-Mobile offers monthly “PCF 101” classes. Lectures on “cloud-native” principles in the morning are followed by hands-on labs in the afternoon. Afterwards, developers are given an org or space for 90s to develop a PoC. And developers are gravitating to the platform in growing numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hDK08u0ZYul-rfPHwl16eg.png" /><figcaption>Platform adoption at T-Mobile: <a href="https://schd.ws/hosted_files/cfsummit2017/e5/T-Mobile-ZeroTo12Million.pdf">https://schd.ws/hosted_files/cfsummit2017/e5/T-Mobile-ZeroTo12Million.pdf</a></figcaption></figure><p>By offering internal training, education, and immersion, these companies seeded a groundswell of internal demand for the platform. Even outside of formal programs, developers will talk. Word gets around about faster deployments and no tickets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/1*y3waYVGFgVPswnfxqDKLJg.png" /><figcaption>Comcast keynote panel: <a href="https://twitter.com/DormainDrewitz/status/874782049399218176">https://twitter.com/DormainDrewitz/status/874782049399218176</a></figcaption></figure><h4>Demystifying success</h4><p>Every company is different, so there is no guarantee that these steps are the recipe for success for you. But if you are starting down the path of using Cloud Foundry, or contemplating digital transformation, take note. The patterns of success are emerging.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=232193111b18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Trying to Monetize Your Data]]></title>
            <link>https://medium.com/built-to-adapt/stop-trying-to-monetize-your-data-a61791fa5d98?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a61791fa5d98</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[big-data]]></category>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Mon, 31 Oct 2016 22:05:17 GMT</pubDate>
            <atom:updated>2017-04-06T22:40:39.181Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>How data can help your customers take actions based on insights</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8HKEpPNHAnrYvkUs2lCCg.jpeg" /></figure><p>Every week in our briefing center, we talk to companies about unlocking the potential of their data, and the same question crops up. I often find some version of it in the pre-brief document I get as a regular speaker for these data overview sessions. But it’s usually the same: “<strong>How can we monetize our data</strong>?”</p><p>While I’m excited to talk to companies about the possibilities for their data, I find that trying to answer that question directly misses the real question: What problems can you solve — or solve better — with data?</p><p>Looking at data in isolation from the problems it could help solve is a widespread misstep made by organizations. Nick Heudecker, research director at Gartner, <a href="http://www.gartner.com/newsroom/id/3466117">recently noted</a> that “the big issue is not so much big data itself, but rather how it is used. While organizations have understood that big data is not just about a specific technology, they need to avoid thinking about big data as a separate effort.”</p><p>This is not to say that monetization doesn’t or can’t happen. Rather, consider how your data can help solve specific business problems. This indirect but potent path can eventually lead to data monetization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mZ1TL7iB4iPN4Z8kDetnOg.jpeg" /></figure><h4><strong>Start with the problem, not the data</strong></h4><p>Approaching your data with the sole purpose of spinning it into gold is — surprise! — the stuff of fairy tales. Starting with your data and trying to find the money is actually more like panning for gold: labor-intensive, stressful, and inefficient. You can spend a lot of time sifting through data for something promising, but you still have to validate that it’s something someone will pay for.</p><p>Instead, start by identifying business problems that exist and treat them as opportunities. Here are some broad categories of ‘problems’ and opportunities that data can help address:</p><ol><li><strong>Customer problems you’re already solving:</strong> Your data will have the greatest impact on the core customer problem you already solve. Whether it’s delivering packages or providing retirement plan services, this should be the reason you exist as a business. Your data can help improve how you solve these core problems, and, in some cases, instantly provide a path to scale.</li><li><strong>Customer problems you haven’t solved yet:</strong> No matter your industry, your customers have many times when they could make better decisions about using your product or service, and, as a result, have a better experience. For example: a student at a university might enjoy knowing which courses to take to earn a higher GPA. A car owner would appreciate understanding how fast to drive to optimize fuel efficiency. Or in general, you could use data could tell your users how long it will take to have a problem with your product or service addressed.</li><li><strong>Operational problems that cost organizations money:</strong> Many enterprises have lists of inefficiencies — like a telco or bank with high customer churn, a utility company that’s losing revenue due to service theft, or unexplained application outages that reduce productivity. Issues like these can become high priority areas based on the estimated impact to the business.</li></ol><p>As you think about current and potential problems to solve, consider what type of person needs to do something differently as part of that solution: Is it a field technician? A support center rep? A specific customer persona? A user?</p><p><a href="https://blog.pivotal.io/big-data-pivotal/features/a-recipe-for-smart-applications">A Recipe For Smart Applications</a></p><h4><strong>“Monetize” through the application</strong></h4><p>Once you know whose problem you are trying to solve, understand how they currently solve this problem. Some questions to guide you in this process include:</p><ol><li>Where do they go for their information as they make their decisions or take actions?</li><li>What steps do they take?</li><li>What applications are they already using in that process?</li></ol><p>You either already have an application in front of this target user or you don’t. A lot of enterprises have existing applications that could be augmented. Other times, it makes more sense to build an app from scratch.</p><p>Regardless, the application needs to let the user take an appropriate action as part of solving that problem. It can’t simply be an information portal. Why? Users generally come back to apps that allow them to take meaningful action. For example, if the target user is a bank customer, they should be able to transfer funds, not just look at their bank balance. If it’s a customer service rep, they should be able to dispatch a technician or issue a credit to their account.</p><blockquote>Users generally come back to apps that allow them to take meaningful action.</blockquote><p>Now, consider that action as the one you want to optimize. Sometimes it’s relatively simple: If the target user is a consumer and they are able to purchase a product or book a service, you are probably trying to drive more of those actions. Sometimes, it’s a little more complex: If the action is to dispatch a service technician, perhaps you want to dispatch the closest technician that isn’t likely to require overtime pay. Influencing these actions as they are happening is what can drive additional revenue or lower costs.</p><p>And that’s precisely where data comes in.</p><h4><strong>Use data to improve the experience</strong></h4><p>At this point you should know the <strong>user</strong>, the <strong>application</strong>, the <strong>action</strong>, and which way you want to <strong>influence</strong> that action. You can influence that action with data by offering decision support directly in the app at or preceding the action in question. This is not just data surfaced in an analytical report — most users don’t have time to interpret a bar chart or scatter plot. Instead, it’s a feature that directly offers a tip, recommendation, or estimate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B5EDhS8R3jZRQwHuCJdlGw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*2wo05X6TEQkGB6jxKMKLDw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/881/1*SdOi8r1GlqN2BBUx76faUg.png" /><figcaption>Data was used to improve Netflix recommendations (left), Uber trip estimates (middle) and give Airbnb hosts a tip on what to price their rooms (right).</figcaption></figure><p>Unpacking what goes into one of these data-driven features reveals a number of requirements. Predictive analytics and optimization math is nothing new, but the scale of data that is available to help build those models strains legacy systems. Being able to run analytical queries and libraries of analytical functions, like R or Python, in parallel across a horizontally scaled database, markedly changes the sophistication and speed of your data models.</p><p><a href="https://medium.com/built-to-adapt/for-cloud-native-data-is-the-new-black-544f26a45059">For Cloud Native, Data is the New Black</a></p><p>Analytical models — however sophisticated — are still in essence just math that produces a table. Tables by themselves are not enough to prompt a user to take an action. Getting there through analytical models means asking and answering two common questions:</p><ul><li>Approximately when is something going to happen?</li><li>What is the best option range of potential actions?</li></ul><p>Notice that neither question seeks an exact answer. Predictions and optimizations can have a range of confidence levels that leaves some margin for error. Given what users on Netflix or Amazon are trying to do, a recommendation reel functions best as a range of curated option. <a href="http://www.forbes.com/sites/ellenhuet/2015/06/05/how-airbnb-uses-big-data-and-machine-learning-to-guide-hosts-to-the-perfect-price/">AirBnB’s “price tip” feature</a> offers a slider bar to show a range of suggested listing price points and relative degrees of booking likelihood.</p><p>Finding the right way to surface the output from an analytical model to drive behavior and better meet user needs can take several iterations. This is where an agile approach — test-driven, iterative releases; a platform for <a href="https://blog.pivotal.io/pivotal-cloud-foundry/features/cloud-native-continuous-delivery-with-netflix-spinnaker">continuous delivery</a>; and <a href="https://docs.cloudfoundry.org/devguide/deploy-apps/blue-green.html">blue-green deployments</a> — all support data-driven applications. Further, user feedback and analyzing clickstream data are essential to fine-tuning the experience for users.</p><h4><strong>It’s about value</strong></h4><p>Anticipating a user need at the right moment and changing a user’s behavior is no trivial task. But if you can present an easier, faster, smarter alternative, you have an opportunity to promote a new or different action that is relevant to the user.</p><p>In the end, your data capabilities and models are only as good as how well you get those insights into the hands of users at the moment they need them. And it is this very place where the user finds value — in smart alternatives and features — where you can finally fulfill that promise of monetizing your data, by making it useful.</p><figure><a href="http://builttoadapt.io/"><img alt="" src="https://cdn-images-1.medium.com/max/71/1*9fg8oHTkroGjylRUKyKQAw.png" /></a></figure><p><em>Change is the only constant, so individuals, institutions, and businesses must be </em><a href="http://builttoadapt.io/"><em>Built to Adapt</em></a><em>. At</em> <a href="http://pivotal.io/"><em>Pivotal</em></a><em>, we believe change should be expected, embraced and incorporated continuously through development and innovation, because good software is never finished.</em></p><figure><a href="http://pivotal.io/"><img alt="" src="https://cdn-images-1.medium.com/max/300/1*z9lcnjksUjJ7wuEH-H0R8A.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a61791fa5d98" width="1" height="1" alt=""><hr><p><a href="https://medium.com/built-to-adapt/stop-trying-to-monetize-your-data-a61791fa5d98">Stop Trying to Monetize Your Data</a> was originally published in <a href="https://medium.com/built-to-adapt">Built to Adapt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Rules to Follow When Adopting Big Data in the Cloud]]></title>
            <link>https://medium.com/@dormaindrewitz/3-rules-to-follow-when-adopting-big-data-in-the-cloud-30ee05368428?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/30ee05368428</guid>
            <category><![CDATA[gartner]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[data-lake]]></category>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Fri, 19 Aug 2016 19:34:59 GMT</pubDate>
            <atom:updated>2016-08-19T19:47:10.782Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-JnmRYrGatbiVxrFomUFoQ.jpeg" /><figcaption>By Justin Norton from Bristol, United Kingdom (uganda2009–49) [CC BY 2.0 (<a href="http://creativecommons.org/licenses/by/2.0">http://creativecommons.org/licenses/by/2.0</a>)], via Wikimedia Commons</figcaption></figure><p>The gloves came off this week. At Gartner’s Catalyst conference in San Diego the message in the big data track was loud and clear: go to the cloud *now*. From Carlie Idoine’s session, “<a href="http://events.gartner.com/#/en/navigator/catus7/myagenda/690440/sessiondetail/speakers-tab">From Data to Insight to Action: Building a Modern End-to-End Data Architecture</a>”, to Svetlana Sicular’s “<a href="http://events.gartner.com/#/en/navigator/catus7/myagenda/690436/sessiondetail/speakers-tab">Implementing Data Lakes and the Ocean of Big Data in the Cloud</a>”, to John Hagerty’s “<a href="http://events.gartner.com/#/en/navigator/catus7/myagenda/690376/sessiondetail/speakers-tab">Architecting Business Analytics in the Cloud: SaaS, PaaS and IaaS</a>”, the opinion of many esteemed analysts was distinctly clear and consistent: Cloud is no longer an option in your data architecture; it is a requirement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/0*FahWu_rW4OzYCyyp." /><figcaption>John Hagerty tweets about going to the cloud NOW during Gartner Catalyst 2016</figcaption></figure><p>But for many enterprises, the question is how? The classic (and justified) answer from most analysts is: “It depends”. Let’s set aside the start-ups of the world, who are starting from scratch and likely already heavily using the cloud. For most enterprises, that’s not the reality and there is no easy switch to flip and suddenly operate a data lake in the cloud.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/0*jOBdJ-NO3etHwQrd." /><figcaption>Data lakes in the cloud were all the buzz at Gartner Catalyst 2016</figcaption></figure><p>Most of the enterprises I speak to and caught up with at the Pivotal booth at the conference have some kind of legacy architecture on premises. One of the most pressing pains is that they are using an appliance-based data warehouse. It’s a capital-intensive and inelastic environment — the complete antithesis to the cloud. But changing is a risky proposition and without a clear plan, it’s hard to see how the clouds on the horizon aren’t mirages in the desert.</p><p>For those enterprises, I recommended a “bridge” solution that would give them a path forward, without completely unwinding critical business practices:</p><ol><li><strong>Obey the laws of data gravity:</strong> As Gartner analyst Angelina Troy articulated in her session, “One of the hardest things you can do in your hybrid cloud architecture is move data around”. Having worked at the leading WAN optimization vendor, I know that network bandwidth should not be taken lightly. Troy has even calculated the “ship it” threshold for moving data in bulk to the cloud — as in, when you put disks on a truck and physically drive it to the cloud provider. Net takeaway: Leave the data where it is. If it’s born in the cloud, great. If not, leave it on prem. The mix will change over time, so architect for both.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*WHVCjoDUCSihGROn." /><figcaption>The point at which it makes more sense to FedEx your data to the cloud</figcaption></figure><p><strong>2) Adopt software data warehousing: </strong>The nice thing about software is that it can generally run anywhere, so long as it’s hardware requirements are met. You can adopt software on premises and move it to the cloud. You may be able to completely replace an on-premise data warehouse appliance with data warehouse software that runs on commodity hardware, or you can at least start to move new and less sensitive workloads to the new software-based system.</p><p>Wait, wouldn’t I just move those new workloads to a data lake? Well, “it depends”, but as the slide below from Sicular’s presentation illustrates (deliciously, I might add), the data warehouse remains relevant and complementary to data lakes. But since data warehouses appliances are so acutely un-cloud, it’s worth building a strategy for those workloads, which do have different requirements and will remain valuable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/0*kC2eOPZ4wtkqdByJ." /><figcaption>Gartner, “Implementing Data Lakes and the Ocean of Big Data in the Cloud”, Svetlana Sicular, presented at Gartner Catalyst, August 2016</figcaption></figure><p><strong>3) Mind the compute-storage debate for cloud-based data lakes:</strong> Sicular made an unapologetic prediction that the future of data lakes would entail the separation of compute and storage. Cloud offerings like Amazon S3 epitomize this type of architecture, so this prediction goes hand in hand with the call to go to the cloud *now*, but it also implies that Hadoop does not necessarily have to be the basis of that data lake. In fact, my colleague <a href="https://twitter.com/jeffreyfkelly">Jeff Kelly</a> just wrote about how we are observing (and supporting) the <a href="https://medium.com/data-state-of-mind/data-lakes-the-lure-of-the-cloud-66bf69b2f1fe#.sqnomq2ma">rise of the S3-based data lake</a>.</p><p>So, does that mean the future of data lakes is NOT Hadoop? Again, that depends. Another colleague, <a href="https://twitter.com/JagMirani">Jagdish Mirani</a>, recently covered the <a href="https://blog.pivotal.io/big-data-pivotal/products/the-das-vs-nas-debate-for-apache-hadoop">debate between local versus network attached disk in Hadoop</a>. There is a case to be made on both sides within Hadoop, which means the separation of compute and storage — in the public cloud or not — does not require abandoning Hadoop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/0*Gjk39tC61ns6bfSu." /><figcaption>Gartner, “Implementing Data Lakes and the Ocean of Big Data in the Cloud”, Svetlana Sicular, presented at Gartner Catalyst, August 2016</figcaption></figure><p>With changes afoot, it’s time to evaluate your options and find a bridge from your current architecture to a future state architecture. Expect changes and seek out solutions that offer flexibility in what and how you deploy data management software. Find partners with experience across domains to de-risk your transitions. <a href="https://pivotal.io/big-data/pivotal-big-data-suite">Pivotal</a> is here to help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30ee05368428" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why a history major is excellent preparation for a career in investment analysis]]></title>
            <link>https://medium.com/@dormaindrewitz/why-a-history-major-is-excellent-preparation-for-a-career-in-investment-analysis-75c604c4bfa7?source=rss-2594bc46074e------2</link>
            <guid isPermaLink="false">https://medium.com/p/75c604c4bfa7</guid>
            <dc:creator><![CDATA[Dormain Drewitz]]></dc:creator>
            <pubDate>Wed, 18 Jun 2014 05:22:38 GMT</pubDate>
            <atom:updated>2014-06-18T05:22:38.438Z</atom:updated>
            <content:encoded><![CDATA[<p>As a history major at UCLA, I often faced the question, “so, what are you going to do after college? Teach?” Just as <a href="https://medium.com/@danielfschmidt">Daniel Schmidt</a> wasn’t thinking about his career when he chose <a href="https://medium.com/@danielfschmidt/why-a-philosophy-major-is-excellent-preparation-for-a-career-in-product-management-3e728a9d12e0">a philosophy major</a>, I wasn’t picking my major as a future job description. I was passionate about history, and I was good at it. That’s a powerful combination for producing good work.</p><p>When looking for my first job after graduation, I used “research” as my search term — it was a skill I had developed and enjoyed using. That’s what led me to “equity research”: first, as an assistant, and then, later, as an associate analyst. In total, I spent 6.5 years in equity research, using skills I had developed as a history major every day. Here’s why I continue to think it was the secret to my success:</p><p>1. History trains you to consider your sources. Every testimony to history is given from some perspective: an individual, part of some social group, with biases and possibly motives. The information provided can be useful, but it must be evaluated in the context of its source. The same goes for investment analysts as they digest information from company executives, industry analysts, news pundits, and channel checks.</p><p>2. You must be able to quickly get an idea down on paper in a history course. As a history major, you’re often evaluated by written “in class” essays. You don’t have to be the best writer, but you do have to be able to articulate your thesis and support it in a short amount of time. This pertains specifically to sell-side equity research, when you will need to summarize and publish your analysis of a company’s earnings or other event in a matter of hours or less.</p><p>3. Not strictly economic, history requires both a macro and micro view. How you evaluate the social-economy of a town in medieval Europe will vary whether you are looking before, during, or after the Black Death. Same goes for stock valuations before, during, or after a tech bubble, financial crisis, currency fluctuations, or other macro factor.</p><p>4. You learn to think without complete information in history. Studying history is like looking at circus through a pinhole — if you don’t know that you’re only seeing a tiny fraction, it’s easy to jump to conclusions about that bear on a bicycle you saw. As an analyst, I had a healthy appreciation for that which I didn’t know, and always made the assumptions that drove my models clear to investors and myself.</p><p>5. Historians love a contrarian view. The mainstream might think of the Vikings as plundering barbarians, but studying history exposes you to the case for their contribution to society through cities and trade. History scholars can make or break their careers on these types of bold, contrarian assertions, just like stock analysts can with a “sell” or “buy” rating that goes against the majority.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75c604c4bfa7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>