<?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 Cory Kennedy-Darby on Medium]]></title>
        <description><![CDATA[Stories by Cory Kennedy-Darby on Medium]]></description>
        <link>https://medium.com/@ckdarby?source=rss-be84bff14144------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*VatyVwUQ2BF65uTd.png</url>
            <title>Stories by Cory Kennedy-Darby on Medium</title>
            <link>https://medium.com/@ckdarby?source=rss-be84bff14144------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:20:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ckdarby/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[Most developers feature creep on themselves]]></title>
            <link>https://medium.com/@ckdarby/most-developers-feature-creep-on-themselves-f36ddaf7350d?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/f36ddaf7350d</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Mon, 29 Jul 2019 01:39:40 GMT</pubDate>
            <atom:updated>2019-07-29T01:39:40.731Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*HBrFoF1P2QBsVgucRsjwwA.jpeg" /><figcaption>Photo Credits: Kristian Niemi</figcaption></figure><p>Them: “That Jira ticket will take me at least a week or maybe two.”<br>You: “Really? That feature didn’t seem like a lot of effort.”<br>Them: “This new feature will be accessing the database. I’ll need to write a caching layer.”</p><p>You: “Our platform doesn’t take that many requests. It’ll be a negligible amount of additional reads to the database.”<br>Them: “Ugh! Another hack, why can’t we do anything the right way?”</p><p><em>You’re probably not writing code for, Google, Facebook or Apple. Stop thinking you are.</em></p><p>A common trend I see more these days is that when other developers aren’t getting their way(aka “the right/correct way”), they are more likely to write off the solution as a “hack”. Every solution comes with compromises.</p><p>At what point do you draw the line? Is it when they start suggesting rewriting the whole JDBC driver because they believe their solution is more performant?</p><p>If we lived in a magical world where Steve Jobs sings to us every morning, the streets are paved with gold and everyone dreams to be us then, yes, time is infinite, and then they can implement as much as they want.</p><p>Instead of adding that caching layer, implementing an outrageous multitier abstraction, or using a new design pattern you just read about last week, can we focus on solving problems that make our lives better?</p><p>Wouldn’t it be a better use of this developer’s time to solve problems that will have a significant impact? It would be a better use of their time fixing the tooling that is going to make the team more productive seems like a better use of time then over engineering the shit out of this feature.</p><p>Yes, there are times when you’ll need to add caching on your reads but measure it, prove it and then develop it. Too many of us in the industry think we’re some mythical unicorn, Google, Apple, or Facebook, but in reality, a lot of our day to day problems aren’t near that kind of requirement.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f36ddaf7350d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Canada’s Newest Cell Provider, Fizz Mobile]]></title>
            <link>https://medium.com/@ckdarby/canadas-newest-cell-provider-fizz-mobile-27c69c3b9dfa?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/27c69c3b9dfa</guid>
            <category><![CDATA[canada]]></category>
            <category><![CDATA[cell-phones]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Sun, 02 Dec 2018 16:14:31 GMT</pubDate>
            <atom:updated>2018-12-02T16:14:31.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CUN0ulk0rx0-WD3J-hGM6g.png" /></figure><p>Monopolies run the telecommunication industry In Canada for the most part. Almost all of our choices can be grouped into three major carriers, Bell, Rogers, and Telus.</p><p>It shouldn’t be a surprise that Canada pays some of the highest monthly plans in the world, a while ago Canada was <a href="https://www.mtlblog.com/news/canadians-are-paying-the-highest-cell-phone-bills-in-the-world">ranked #1 </a>for the highest cellphone bills in the World.</p><blockquote>Why Are Canadian Wireless Carriers Increasing Prices? Because They Can. — Michael Geist</blockquote><p>To achieve lower pricing the industry needs a competitive landscape with more providers, and that is why I’m happy to see <a href="https://fizz.ca/?ref=XBK2X">Fizz Mobile</a> launch.</p><h4>Pros</h4><ul><li>Pricing, for example, Canada &amp; USA with 8 GB Data, unlimited voice, only $45/Month!</li><li>Data rolls over from the prior month</li><li>Gifting my extra data to any other Fizz member, including friends and family.</li><li>Customization of plans, no longer need to pay for minutes or SMS if you don’t want to</li><li>Once I got the SIM card, it took me less 10 minutes to set up, including transferring my number</li></ul><h4>Cons</h4><ul><li>Early stage company, there will be hiccups</li><li>Had an outage of ~5 hours</li><li>Customer support is only business hours</li><li>No physical retail location that to my knowledge</li></ul><p>If you’re looking to save or you’re just tired of overpaying for mobile data, then I recommend taking <a href="https://fizz.ca/?ref=XBK2X">Fizz Mobile</a> for a spin.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27c69c3b9dfa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Having a team that matters in a company starts with this…]]></title>
            <link>https://medium.com/hackernoon/having-a-team-that-matters-in-a-company-starts-with-this-1e66505b7bc8?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e66505b7bc8</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Wed, 13 Dec 2017 16:47:30 GMT</pubDate>
            <atom:updated>2019-04-29T09:35:00.283Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n-Qe2OcgiQ53xA-xq_2aWw.jpeg" /><figcaption>The dream to stand above the others &amp; have a meaningful impact. Photo Credits: <a href="https://www.flickr.com/photos/denalinps/5302422150/">Denali National Park and Preserve</a></figcaption></figure><p>Every <a href="https://hackernoon.com/tagged/team">team</a> has clients, customers or someone they serve to better. Some clients are easier to spot than others because they’re vocal, they drive the roadmap, or they come shouting when something breaks. No matter the case, every team has a client.</p><p>If every team has a <a href="https://hackernoon.com/tagged/client">client</a>, what are the most fundamental metric to measure?</p><p><strong>Adoption</strong> of your implemented solutions. At this moment you might be tilting your head sideways and saying, ‘Adoption, really?’.</p><p>Yes, adoption. Let me give you an example of where a team might think otherwise and the underlying problem.</p><p>Assume for a moment that you are the head of the <a href="https://hackernoon.com/tagged/security">security</a> team at your company. You are responsible for policies, data protection, preventing leaks, etc. You might have gone as far as saying your team’s mission is protecting the company, and mitigating risk. There is just one catch with your mission statement, and that is the lack of your client(s) in the statement.</p><p>You might be frustrated at this point thinking, ‘But I have, I run the <a href="https://hackernoon.com/tagged/security">security</a> team! My client is the company.’ The company isn’t your client, the company is who employs your team, and protecting them is the by-product of working with your clients.</p><p>The reality is that your clients are the employees of the company. Your mission is listening to them, finding their pain points and implementing a solution. There’s just one small catch, the solution you implemented, what was the adoption rate across those that had the pain point?</p><p>Adoption is everything. As a manager of a security team, you can set the best practices, policies, knowledge, etc. but if nobody is adopting it, using it or everyone is just trying to bypass it, then it is pointless.</p><p>Having a team that matters in a company starts with being able to get adoption within the company. To get adoption you need to listen. Listen to your clients.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e66505b7bc8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/having-a-team-that-matters-in-a-company-starts-with-this-1e66505b7bc8">Having a team that matters in a company starts with this…</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The most important thing every manager should list as their number one]]></title>
            <link>https://medium.com/hackernoon/the-most-important-thing-every-manager-should-list-as-their-number-one-a400d2f2d2da?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/a400d2f2d2da</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[personal-growth]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Sat, 11 Mar 2017 17:49:45 GMT</pubDate>
            <atom:updated>2019-04-29T09:35:01.708Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mRZBloKFdAaMvSSNWdI5Bg.jpeg" /><figcaption>Photo credits: <a href="https://www.flickr.com/photos/freestocks/28123133694">FreeStocks.org</a></figcaption></figure><p><a href="https://hackernoon.com/tagged/imagine">Imagine</a> that you are in an <a href="https://hackernoon.com/tagged/interview">interview</a>, and you’ll be a manager of a <a href="https://hackernoon.com/tagged/team">team</a>, and the interviewee asks you, ‘What is your number one priority if you are working here?’</p><p>Take a moment, and think about what you would say.</p><p>The most common responses I hear from people when I ask them this question is, the highest priority objective, meeting deadlines, achieving company objectives.</p><p>These responses are the safe nonsense that we have come accustom to saying because it is non-threatening to our boss and our boss just hears that they’re going to look amazing.<br> <br>To most it will make us sound like a star candidate, that we are result driven, we’ll get a lot done and in return make whoever is <a href="https://hackernoon.com/tagged/hiring">hiring</a> us look stellar.</p><p>Using these responses and looking like a star candidate might be acceptable for a position that doesn’t have anyone reporting to them, but for managers, this should be a massive red flag.</p><p>Don’t hire these managers and fire them if you have them.</p><p>In the short term managers who operate with objectives as their number one priority will deliver and have results to back the original decision to hire them. In the long term, these managers will begin just to have teams that deliver half of what they should be delivering.</p><h4>People should always be the number one priority</h4><p>Caring about them, retaining them and showing them how their work matters in the company.</p><p>Nothing else will matter in the long term game of the business. If the company ends up with a revolving door of its high impacting talent leaving it will struggle. Without these high impacting individuals the business will struggle to innovate, and the market punishes those that stay stagnant.</p><p>Stagnant businesses are dead businesses.</p><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a400d2f2d2da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/the-most-important-thing-every-manager-should-list-as-their-number-one-a400d2f2d2da">The most important thing every manager should list as their number one</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a single indexing mistake nearly cost us a boat-load of money!]]></title>
            <link>https://medium.com/@ckdarby/how-a-single-indexing-mistake-nearly-cost-us-a-boat-load-of-money-642263d193f6?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/642263d193f6</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Sun, 04 Dec 2016 08:47:54 GMT</pubDate>
            <atom:updated>2022-02-19T13:33:23.257Z</atom:updated>
            <content:encoded><![CDATA[<h3>How a single indexing mistake nearly costed a boat-load of money</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a1WmgD8E-jn1tIdbzisvrA.jpeg" /><figcaption>One step away from a catastrophic outcome. Photo Credits: <a href="https://www.flickr.com/photos/oddsock/9125510233">Ian Burt</a></figcaption></figure><p>A long time ago on a Monday morning you’re sitting at your desk drinking coffee trying to wake up. All sudden someone from another department taps you on the shoulder.</p><p>“Today’s the big day. One of our largest publishers is ready to switch over to our platform. Are you all set for today’s move?”</p><p>You’re sitting there thinking, I have no idea about this migration. To add to your stress, you’ve only been a team lead for a short period of time, and are not the most experienced person on your team handling the <a href="https://en.wikipedia.org/wiki/Extract,_transform,_load">ETL</a> (Extract, Transform, Load) cluster.</p><p>You tell them there must have been some miss communication and that this is the first you’ve heard of this migration.</p><p>There’s clearly some worry.</p><p>So you say: “Don’t worry. Things should go smoothly. We have already done half a dozen other migrations.”</p><p>They give you the green light to start the migration, and then leaves. And so begins your challenging week.</p><h3>Opening the flood gates</h3><p>The publisher flips the switch.</p><p>You wait. Then you wait some more. Other people are standing around waiting, too. Nothing is showing up.</p><p>There are people showing up who were ready to high five you but instead are getting anxious because nothing’s showing up. The reports are blank.</p><p>You realize you have forgotten to configure the settings for the publisher’s website. This means all that traffic is getting marked as failed and going straight into the failed bucket.</p><p>Phew! Nothing is lost. You just need to spend time configuring a couple of things and replaying from the failed bucket.</p><p>After some configuration, you begin replaying the data from the failed bucket. In the charts, the <strong>red</strong> boxes show where your replay begins.</p><p>Woah.</p><p>Total traffic events have tripled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0tu1TZ-8-w9z4SMUrWMEsw.png" /><figcaption>*The 8th — 10th, includes all sites. It wasn’t until mid day through the 10th we split the metrics up.</figcaption></figure><p>And traffic aggregations have tripled, too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mgOkvCTcEzac3zcHJmKYNA.png" /></figure><p>Ouch! The database is now using 7x the amount of CPU.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GIYPja_CVB-S7AQIpXzpxw.png" /></figure><h3>Hardware solves everything, right? Right?</h3><p>Under the hood of your infrastructure is a cluster performing the ETL. Your cloud portion is handling cache and a Postgres cluster. There’s publisher events that get pushed into your system.</p><h4>High level view of Infrastructure</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nJ_IQVrVzPAKkvVi5JsXHg.png" /><figcaption>Green lines represent pushing data &amp; red lines represent pulling data.</figcaption></figure><h4>Throwing more hardware at the problem</h4><p>The priority during this situation is to get the system under control, then bring it back to a stable state. Until the problem is identified, the low hanging fruit is throwing hardware (and money) at the problem.</p><p>Your team decides to upgrade the master database instance to the largest possible size instance size. After the upgrade, there are small improvements, but not significant enough. With the upgrade, the database is now running the largest possible box, and it is not possible to upgrade it any further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NRvw6q4-1LYZyTWrZ5rUyQ.png" /><figcaption>Stopping everything while the being upgraded to the largest instance</figcaption></figure><p>Hardware will not solve this problem because PostgreSQL is single-threaded. However, in PostgreSQL 9.6 they introduce parallel queries, but upgrading PostgreSQL would only delay the inevitable, and would hide the underlying problem.</p><h3>Improper indexes = N² vs N Log (N)</h3><p>At this point, you might be thinking that there isn’t any index on the table at all, but there is an existing index on the table on the time column.</p><p>The problem is that indexes can be pointless when you don’t understand how the data is entering a given column in the first place.</p><p>During the aggregation layer, PostgreSQL must check whether there’s already an existing aggregation within that hour, or whether this is indeed a new aggregation.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/80c804dee1f58d56ddfffc23acabd5aa/href">https://medium.com/media/80c804dee1f58d56ddfffc23acabd5aa/href</a></iframe><p>The above query looks innocent, but the problem becomes more apparent when you run <em>explain,</em> or run a count on the stamp clause.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/06c8637656e475943ed6acff799f47e2/href">https://medium.com/media/06c8637656e475943ed6acff799f47e2/href</a></iframe><p>You realize that everything gets aggregated on the hour, making this index somewhat pointless on its own. Once the query applies the index, it must perform the WHERE clause on ~50,000 rows, using filtering. And it has to perform all this for <strong>every single aggregation</strong>.</p><p>Using <a href="https://en.wikipedia.org/wiki/Big_O_notation">Big-O notation</a>, this query is actually N² instead of the standard N log(N) that indexes provide.</p><p>Here’s a chart to show you why this becomes such a problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HwLR-DKk0lYNEMpkH475kg.png" /></figure><h3>How could anyone miss something so simple? Because context is everything.</h3><p>This next anecdote may seem like a wild tangent. But bear with me — it is very relevant to this problem.</p><blockquote>Legend has it that Pablo Picasso was sketching in the park when a woman approached him and asked him to sketch her.</blockquote><blockquote>He finishes the drawing, she is overwhelmed with what he is able to do and asks to purchase it.</blockquote><blockquote>“Five thousand dollars,” Picasso replies.</blockquote><blockquote>The woman asks, “How could you want so much money for this picture? It only took you a couple minutes to draw it!”</blockquote><blockquote>To which Picasso responded, “Madame, it took me my entire life to be able to get to this point.”</blockquote><p>Experienced developers understand that indexes are necessary to reduce the amount of data that needs to be scanned and filtered. Knowing where the bottlenecks are, their causes, and how to fix them — these are all pretty straight forward.</p><p>But all this becomes much harder with more complicated infrastructure and more moving pieces.</p><p>If you knew the true inner workings of a sophisticated platform like this, your opinion may changed regarding how easy it would be to identify an issue like this one.</p><h3>Everyone makes mistakes</h3><p>During writing this article up a friend of mine who runs a startup had a similar issue happen. They forgot to add an index on a column they began using and the CPU on their database instance skyrocketed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q1gUDTpCZ-rFt8jmRxU1mQ.png" /><figcaption>A startup forgetting to add an index, then adding it.</figcaption></figure><h3>Postmortem</h3><h4>Index alterations for a happy ending</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5cmg12p58UE8qoCM5BLWXA.png" /><figcaption>Stopping our workers, applying the index and restarting.</figcaption></figure><h4>Lessons learned</h4><ul><li>Communication is king</li><li>Get client metrics beforehand, so you can understand the demand increase</li><li>Start with a small portion — not the entire fire hose.</li><li>Understand the data that you are indexing</li></ul><p>Thanks for reading! Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=642263d193f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Not Found A Startup / Work At One?Wait, You Work At A Giant Corporation.]]></title>
            <link>https://medium.com/@ckdarby/why-not-found-a-startup-work-at-one-wait-you-work-at-a-giant-corporation-d740e91d9651?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/d740e91d9651</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Mon, 05 Sep 2016 21:36:10 GMT</pubDate>
            <atom:updated>2016-09-05T21:42:43.373Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8qNxEpTMuvAr2I1Rj1ugNQ.jpeg" /><figcaption>Executive Boardroom — MindGeek</figcaption></figure><p>It seems every conversation I have with entrepreneurs these questions arise during our conversation:</p><blockquote>Why are you not a founder of a startup? Why are you not working for one?</blockquote><p>I work for a company called, <a href="https://en.wikipedia.org/wiki/MindGeek">MindGeek</a>. It currently has 1000+ employees, ranks in the top ten bandwidth consumption companies in the world, and is far from being a startup.</p><p>Before this last year, I’ve spent six years in the startup world. I’ve worked for multiple startups, different industries, different sizes, funded and bootstrapped. I’ve gone through the cycles of stable, hyper growth and downsizing. I’ve also founded a startup with two amazing co-founders, but it wasn’t successful. Why work for a large company, though?</p><h4><strong>Risk vs. Reward</strong></h4><p>A significant factor is the risk vs. reward between a startup and a large corporation. There is a common myth that you must work in a startup to cash out enough to live an extraordinary life. Thankfully this has already been <a href="https://80000hours.org/2015/10/startup-salaries-and-equity-compensation/">disproved</a>. Once you factor everything in, on average, you’re going to make about the same as an employee at a top notch company.</p><h4>More Opportunities Than You’ll Know What To Do With</h4><p>At a large corporation, there is a sickening amount of waste and inefficiencies. This waste &amp; inefficiencies create an excellent opportunity to be able to return 10x or more return vs. your salary. It is easier to generate additional revenue from existing products, services. It is even easier to cut costs when you’re dealing with multi-millions and millions in operating costs.</p><h4>Huge Impact = Generous Compensation</h4><p>In less than a month in my new position, I’ve saved the company more than they’re paying me in a year. I’ll generate approximately $1 million in savings over the next 12 months through reducing operating costs.</p><p>You don’t need to be a superhero when you’re playing with millions, hundred of millions or billions of dollars. If you’re dealing with subscription revenues of $100 million and you’re able to increase approval throughput of your users by 1%, you’ll have an impact of $1 million in additional revenue.</p><p>Asking for enormous compensations isn’t challenging when you’re <strong>documenting</strong> your impact and back it with <strong>results</strong>. The amount of compensation has never been an issue if it was fair when compared to what was being saved or generated.</p><h3>Silicon Valley’s / Startup’s Dirty Secret</h3><p>You <strong>don’t</strong> have to be a founder to be successful; you <strong>don’t</strong> need to be in a startup to reap the rewards. You <strong>can</strong> love what you’re doing even in a large company and with the right company have just <strong>as</strong> <strong>much</strong> autonomy.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FmzbC18i_1rg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmzbC18i_1rg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FmzbC18i_1rg%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/741356af410fa3c27a4c9dd2e5f7c636/href">https://medium.com/media/741356af410fa3c27a4c9dd2e5f7c636/href</a></iframe><blockquote>Self-awareness is maybe you should be number 2, 5, 7, 12. Maybe you should be an accountant, not an entrepreneur, become a CFO of an entrepreneur’s company and make a billion dollars. — <a href="https://medium.com/@garyvee">Gary Vaynerchuk</a></blockquote><p>I don’t even think you have to be the best of the best. However, I believe you have to be better than average, in the top 20% of your specialty. Just find what brings you happiness while working, become great in that, and everything else will fall into place.</p><p><em>Disclaimer: These are my opinions and they do not reflect my employer’s opinions or stances.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d740e91d9651" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retrospective: lessons we learned from 2 major API outages]]></title>
            <link>https://medium.com/free-code-camp/insights-into-two-recent-service-outage-incidents-6e9a9c93c225?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e9a9c93c225</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Fri, 08 Apr 2016 04:13:07 GMT</pubDate>
            <atom:updated>2016-07-16T03:45:19.754Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gkNc8TL_ZIb6w6LzZTQIUQ.jpeg" /></figure><p>I belong to a team that provides internal services exposed through an API to various other teams within the company. These teams have become increasingly reliant on the services we provide.</p><p>Without sounding egotistical, these services are likely the most critical in the company. When these services are not entirely operational and stable, it impacts nearly all other teams, and has an enormous direct impact on revenue.</p><p>Internally, other teams in the company using our service are referenced as “clients.” For clarity sake, this article will treat the terms “clients” and “teams” as interchangeable.</p><h4>Wednesday — we start receiving an enormous volume of requests</h4><p>I get into the office, get some coffee and begin my day by checking our metrics and logs. Most people in the company already knew from the night before that there were a couple small hiccups with the load balancers that host our service. My manager wants to me to focus on an important initiative, and send all other unrelated tasks to him.</p><p>A couple of hours into my day I notice that one of our error log emails has a massive spike in a validation error. These validation errors are nothing special. We log to notify any client that sends us incorrect payload parameters that don’t match the validation rules.</p><p>The team I belong to hadn’t deployed any changes, infrastructure was in a healthy state, and nothing was out of place on our side to warrant such a massive increase.</p><p>My manager made it clear earlier that I should pass off to him anything that isn’t related to my current project I’m working on. I quickly realize I’ve made a mistake when I ask him where can I find the team lead of the team that is sending us all these validation errors.</p><p>The mistake is the moment I ask him this question he wants to know why I’m asking. The short version is he sees this as me not being focused on the initiative, and explains he’ll handle the validation errors. Shortly after our conversation, I get an email CC’ing me with the other team pointing out their issue to them.</p><h4>All sudden there’s panic in the office</h4><p>There is a flurry of emails about issues with our service, and everyone points the finger at the prior issue the night before with the load balancers.</p><p>I’m pulled off the initiative to handle the task of dealing with operations and the data center crew to deal with the load balancers. After some discussion, they decide to start rerouting portions of our traffic to other load balancers.</p><p>Magically the load balancers begin to stabilize.</p><h4>The calm before the storm</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3Ii6gyGmAZm-bVHLFHcT9Q.jpeg" /></figure><p>The panic in the office disappears and everything goes back to running smoothly. After a couple of hours, the issue seems to begin to reappear and once again our service becomes compromised by an enormous amount of requests.</p><p><strong>Ding!</strong></p><p>The error log email comes in, and I notice those validation errors are reappearing again. I had been so focused on dealing with the data center that I hadn’t noticed they had stopped when the load balancers became stable.</p><p>Hold on! I pull up our Kibana dashboard to see our requests over time and compare the timestamps of the validation errors and the total requests over time. They are nearly an exact match.</p><p>I am fairly confident this is the issue, and I decide that I’m not repeating the same mistake from the morning. I ask a colleague where the other team is located and head there armed with the knowledge of the correlation between when the spikes happen and when everything becomes unstable.</p><p>Within 10 minutes of explaining the situation to the other team, they realize that this lines up exactly with when they deployed a feature, when they disabled the feature, and when it was accidentally redeployed.</p><p>They disable the feature on their side, and our service returns to stability. The feature they had deployed had a bug that would call our service in all situations, even when it wasn’t required.</p><h4>Monday — ~600% amount of requests to an endpoint</h4><p>The weekend passes, and there hadn’t been any issues with our service since the incident on Wednesday. Monday starts off normal without any issues, but by the end of the work day, our service begins to become unstable.</p><p>Quickly glancing through the Kibana events and our access logs, I notice what appears to be an insane amount of requests coming from a single team. The same team from Wednesday.</p><p>I rush off to that team’s area in the company and explain the details, asking if they by mistake relaunched the buggy feature from Wednesday.</p><p>To be sure that the feature hadn’t been deployed again by mistake, they reviewed their deployment logs and verified on git that the feature hadn’t mistakenly been merged into another branch.</p><p>The feature from Wednesday had not been redeployed.</p><p>I returned to my desk and began chatting with the data center operations team. The situation at this point has become severe because of the time the service has been impacted. The operations team is investigating, and I’m sitting waiting for an answer when the VP of operations shows up.</p><p>He’s clearly not happy because our API impacts a lot of products and services that are from the operations side of the business. He has some questions about bypassing our service, utilizing some fallback methods, and an ETA on the service returning to normal conditions.</p><p>A couple more minutes pass and then everything stabilizes.</p><h4>Fixed? Not unless I believe in unicorns and mythical creatures</h4><p>The data center operations team explains that a feature on our stage server was causing the load balancer processes to keep crashing. I call BS on their answer because this feature had been successfully running without any issues for nearly two months straight. The other reason I wasn’t willing to accept their answer was I had noticed on our Kibana dashboard that our total requests had roughly quadrupled.</p><p>It seemed too crazy that such a stable feature on our staging servers would randomly start causing such large issues.</p><h4>Tuesday — Stakeholders Want Answers</h4><p>Tuesday morning my manager asks me to deal with providing a clear outline of the events that happened on Monday for him to write up an incident report for the stakeholders.</p><p>The night before I spent a lot of time reflecting on the recent situations and I realized that a significant pain point was using our Kibana dashboard. Our Kibana dashboard is amazing when you want to see all requests, but with our current mapping, it’s hard to drill down and isolate requests from a specific client.</p><p>The problem? It’s going to take a bit of work, nobody has assigned me to do this, and this isn’t the original task given to me. On the spot I decide that I’m going to build this out. High performing individuals don’t ask permission to do their job. They go and deliver results.</p><blockquote>High performing individuals don’t ask permission to do their job. They go and deliver results.</blockquote><blockquote>- Cory Darby</blockquote><p>I begin to hack together a script that uses regular expressions with our Elasticsearch that passes the results into Highcharts. During this, our CTO stops by to ask about the situation that unfolded on Monday. I explain that there’s no evidence at the moment, but that my gut feeling from what I saw in the logs, graphs, and metrics is that the other team’s cache died. The other team’s cache dying would force them to make an enormous amount of requests to our service.</p><p>He leaves to get answers from the other team, and I finish hacking the script together. It isn’t elegant code but it gets the job done, and it means we’re not in the dark anymore.</p><p>Just 10 minutes after finishing, our CTO returns. He explains that the other team can’t find any issues on their side. At this point I show him the graph, which shows every request grouped by every team using our service:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k46yDptWTSQIKSTFEs_GSw.jpeg" /><figcaption>This chart shows all the requests to our service originating from +100 client services.</figcaption></figure><p>The giant spike in the graph above is the other team that had just explained that everything looked healthy on their side.</p><p>Further investigation by the other team showed that a new feature they launched required a significant amount of caching. The rules they have in place with their cache were to evict the oldest cached objects to make room for new ones. The evicted data happened to be all the cached data for our service.</p><p>Their cache was working, but it didn’t have any of our service cached anymore. The other team was hitting us for nearly every request.</p><h3>Areas of Improvement</h3><p>After any major engineering incident, it’s important to cover the cause, solution, prevention, and any pain points the incident exposed.</p><h4>Insightful metrics &amp; monitoring</h4><p>Clients using our services need better insights into their usage. On our side, we will be providing easier ways to drill down for specific metrics.</p><p>After these events, it’s clear that we will need to create an actual dashboard for both the clients and for ourselves. The dashboard will replace the script I built to push data into the Highchart graph. The dashboard graphs will have monitoring on the data being received so they can provide the earliest alerting.</p><h4>Reduce team Silos</h4><p>Ideally, we would allow other teams in the company to be able to push pinpoints to the dashboard when they deploy to their production environments. If the requests from a single team increase substantially after a deployment, the deployment is most likely responsible for this spike.</p><h4>Communication</h4><p>During these outages, stakeholders created a lot of distraction throughout the company. These distractions take the form of emails, chat messages, and individuals showing up at the team’s space to ask about the service.</p><p>To reduce the number of distractions, we will have an internal dashboard that includes the current status and the events as they unfold. The events will include time of creation, a description of the situation, and an estimated time of recovery (if known).</p><h3>Wrapping up</h3><p>It’s never a question of “if” there will be an outage. It’s a question of “when.”</p><p>Every incident — no matter how small — is a learning opportunity to prevent things like this from happening again, reduce its negative impact, and become better-prepared.</p><p><em>Disclaimer: These are my opinions, nobody else’s, and they do not reflect my employer’s.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e9a9c93c225" width="1" height="1" alt=""><hr><p><a href="https://medium.com/free-code-camp/insights-into-two-recent-service-outage-incidents-6e9a9c93c225">Retrospective: lessons we learned from 2 major API outages</a> was originally published in <a href="https://medium.com/free-code-camp">We’ve moved to freeCodeCamp.org/news</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Keeping Customers As Repeat Customers]]></title>
            <link>https://medium.com/@ckdarby/keeping-customers-as-repeat-customers-18a3a8113922?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/18a3a8113922</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Sun, 27 Mar 2016 20:42:12 GMT</pubDate>
            <atom:updated>2016-03-27T20:42:12.445Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g-2ktpZnKWv95Er3T0Ffrw.jpeg" /><figcaption>Puerto Rico’s coffee 10/10. Photo Credits: Myself</figcaption></figure><p>In January, I was in Puerto Rico speaking at a conference called, <a href="https://www.facebook.com/CenasPR/">Cenas Empresariales</a>. The first day I was introduced to the majority of the other speakers. Not all of the speakers had arrived yet, a lot of the others were arriving the next day.</p><p>As dinner approached, we decided to stop at a restaurant to eat. We sat down, I flipped through the menu and my eyes were fixed on the dreaded statement I hate to see on a menu:</p><p><strong>6 or more we don’t split the bill</strong></p><h4>Our First Trip</h4><p>Our group was 6, nearly all of us were not carrying cash with us because we were visitors. We notified the waiter, and he did his best to accommodated us. The food was surprisingly better than I had expected, our waiter gave us one single bill and explained just to label the items that belonged to each. We marked the order with different numbers representing who ordered what and he came back with separate bills for the corresponding numbers.</p><h4>Returning — The Second Time</h4><p>The rest of the speakers arrived the following day. The prior day we had such a pleasant experience at the restaurant that we suggested the same place the next day. The group was 12 this time. We proceeded with the same system that had worked the day before.</p><p>This time, our group had a different waiter and it was a nightmare. Paying the bill took longer than the time we spent eating, some people got charged the wrong amount and out of sheer frustration of the time being wasted, I told the waiter to charge the outstanding amount to my card.</p><h3>Convenience Nearly Trumps Everything</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*8e9nwz8QkiXFrcfNKxDiag.png" /><figcaption>Nearly everything on my statement is related to convenience. Photo Credits: Myself</figcaption></figure><p>Even though the food was quite good, the rest of the experience was a disaster. The hassle of paying our bill made the collective group agree not to return to that restaurant during our stay in Puerto Rico.</p><p>The greatest day to day example in my life is Uber. The original reason I began using the service is the fact I hated wasting time at the end of the trip sorting out the bill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4X-OFGie2KiwgMkeizAwfg.jpeg" /><figcaption>Photo Credits: Myself</figcaption></figure><p>Customer expectations are shifting but all that is required is to reduce the friction, reduce the unnecessary interactions, and provide convenience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18a3a8113922" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Demystifying A Team Lead’s Day]]></title>
            <link>https://medium.com/@ckdarby/demystifying-a-team-lead-s-day-8b380a529201?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b380a529201</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Sun, 20 Mar 2016 02:31:47 GMT</pubDate>
            <atom:updated>2016-03-20T02:40:02.360Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Recently a colleague attempted to question my hours being logged based on the hours in <a href="https://en.wikipedia.org/wiki/Jira_(software)">Jira</a>. The majority of our tickets in Jira focus specifically on development and code maintenance tasks and miss a large portion of what makes up the role I’m filling.</p><p>To give my colleague a better understanding of my time, I decided to track every minute and send it to them.</p><h3>Every Minute Breakdown</h3><p><a href="https://medium.com/p/83d5b86afbfa"></a></p><h3>Summary of the Day</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xLNEY4pighXlElb6fuUZ7g.png" /><figcaption>This is what 2016–03–18 looked like for me.</figcaption></figure><h3>Details</h3><ul><li>Communication, 2 hours and 32 minutes</li><li>Dev &amp; Operations, 2 hours and 32 minutes</li><li>Break, 1 hour and 5 minutes</li><li>Manager, 37 minutes</li><li>Director, 33 minutes</li><li>Planning, 23 minutes</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b380a529201" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Organization + Silo Mentality = RIP Money]]></title>
            <link>https://medium.com/@ckdarby/organization-silo-mentality-rip-money-29c22e943917?source=rss-be84bff14144------2</link>
            <guid isPermaLink="false">https://medium.com/p/29c22e943917</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Cory Kennedy-Darby]]></dc:creator>
            <pubDate>Sat, 12 Mar 2016 21:02:18 GMT</pubDate>
            <atom:updated>2016-03-12T21:02:18.420Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNfFR0G9A0tDynZtWAWhuA.jpeg" /><figcaption>The picture above is probably the most efficient way to waste money. In my opinion, Silo mentality in an organization places second. Photo Credits: <a href="https://www.flickr.com/photos/ishinelike/3500417450">Lauren</a></figcaption></figure><p>Let’s imagine that you work at a large company with hundreds of employees. You belong to a team that for legacy reasons is stuck using an internal framework. Management has finally agreed to allocate the time to move to a modern framework, excellent!</p><p>Like most things in a large company, you will need to do some analysis of the various other frameworks. Your analysis includes disadvantages, advantages, benchmark performances, etc. You outline all of this. You ask for feedback from your team. There is a couple of small handful of meetings with various other individuals that need to be kept in the loop.</p><p>Fast forward a bit, there’s a decision made and everyone celebrates because an upcoming quarter the move to a modern framework will happen.</p><p>All is splendid, right? Let’s say a couple of weeks later you’re searching on the company’s wiki and come across search results about, ‘Framework proposals’. You realize two different teams are discussing identical situations and have repeated the same task.</p><p>You might be thinking that this never happens. That what I have outlined is just an extreme example. Sorry, it is the reality. I work in a large company of hundred employees, and I can tell you that these situations happen more than most people realize or are willing to admit. In fact, it happens all the time.</p><h3>Silos Hinder Communication</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EGWmj4cSBXBP65IObVpVSg.jpeg" /><figcaption>Photo Credits: <a href="https://www.flickr.com/photos/metrojp/92038203/">https://www.flickr.com/photos/metrojp/92038203/</a></figcaption></figure><p>The book <a href="http://amzn.to/1RdTdAa">Leader’s Eat Last</a> discusses the devasting consequences of failing to have basic trust between individuals. If you never communicate with other teams how do you know if they’re struggling?</p><p>The book outlines trust can not be established without communication between each other. Without this basic trust, it becomes hard to have empathy for others, and this can result in undesired company culture.</p><p>The culture will become one where individuals will be frustrated and put their needs always ahead of others, and that is a culture that will be a disaster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29c22e943917" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>