<?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 Ezequiel Actis Grosso on Medium]]></title>
        <description><![CDATA[Stories by Ezequiel Actis Grosso on Medium]]></description>
        <link>https://medium.com/@eactisgrosso?source=rss-883ae6009da5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TYl0Njr1OFf9SKhlhkGtZw.jpeg</url>
            <title>Stories by Ezequiel Actis Grosso on Medium</title>
            <link>https://medium.com/@eactisgrosso?source=rss-883ae6009da5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:14:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eactisgrosso/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[Build Optionality]]></title>
            <link>https://medium.com/@eactisgrosso/build-optionality-6201fffd7618?source=rss-883ae6009da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/6201fffd7618</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[antifragility]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Ezequiel Actis Grosso]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 02:32:38 GMT</pubDate>
            <atom:updated>2024-10-19T14:33:19.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f2ykyJFm0l1k5f8-" /></figure><p>Years ago, during one of Argentina’s many recessions, a experienced founder shared something that stuck with me.</p><p>While everyone else was panicking, he calmly said, “When this is over, there will be fewer competitors.”</p><p>It was a lesson in 𝘀𝘂𝗿𝘃𝗶𝘃𝗮𝗹 over 𝘴𝘩𝘰𝘳𝘵-𝘵𝘦𝘳𝘮 𝘴𝘶𝘤𝘤𝘦𝘴𝘴.</p><p>Warren Buffet calls it “avoiding the zeros.” Nassim Taleb talks about it when he mentions “absorbing barriers.” The idea is simple: to succeed, you must be able to 𝗸𝗲𝗲𝗽 𝗽𝗹𝗮𝘆𝗶𝗻𝗴 𝘁𝗵𝗲 𝗴𝗮𝗺𝗲.</p><p>If there’s one lesson to take away from this period — post zero-interest rates, massive layoffs, and the AI hype — it’s this: we need to hedge against risks by building 𝗼𝗽𝘁𝗶𝗼𝗻𝗮𝗹𝗶𝘁𝘆.</p><p>That doesn’t mean quitting your corporate job, but relying on it as your only option is becoming more fragile by the day.</p><p>So, how does one go about building optionality?</p><p>There’s a concept drawn from the investment world called a 𝘣𝘢𝘳𝘣𝘦𝘭𝘭 𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺.</p><p>Imagine you’re lifting a barbell with weights on both ends. On one side, you have something very safe, like cash or bonds. On the other side, you have high-risk, high-reward investments, like stocks or startups.</p><p>The idea is to split your approach between these two extremes — play it safe with most of your time or income, but take some small, calculated risks on the side to open up big opportunities for growth — and avoid middle-of-the-road choices.</p><p>As an individual, you keep a stable source of income, but take small, calculated risks — diversifying skills, building a personal brand, maybe starting a side project. This way, you’re ready to adapt and seize new opportunities when the landscape shifts.</p><p>As a founder, you keep a reliable revenue stream — enterprise contracts, consulting services, or smaller but steady customers that ensure cash flow. These keep your business afloat.</p><p>And, on the other side, experiment with new products, moonshots, or market expansions. These could lead to exponential growth but won’t ruin the business if they fail.</p><p>The goal isn’t just success — it’s survival first. Because when the dust settles, those who survive will have fewer competitors and more room to grow.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/posts/fractionaltech_years-ago-during-one-of-argentinas-many-activity-7251969132689035264-hjVp?utm_source=share&amp;utm_medium=member_desktop"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6201fffd7618" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why do some people get promoted faster than others?]]></title>
            <link>https://medium.com/@eactisgrosso/why-do-some-people-get-promoted-faster-than-others-2a703314981?source=rss-883ae6009da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a703314981</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[luck]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Ezequiel Actis Grosso]]></dc:creator>
            <pubDate>Tue, 12 Sep 2023 17:05:21 GMT</pubDate>
            <atom:updated>2023-09-12T17:05:21.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*AmdAbvGrS0tKHGRL" /></figure><p>The velocity of promotions is a topic that keeps sparkling heated debates.</p><p>What we sometimes don’t realize is that the world we live in doesn’t resemble the world we learned in.</p><p>🧪 In school, we are taught about a world where outcomes are normally distributed. We experience a steady progression through different development levels. The growth is often directly proportional to the knowledge, skills, qualifications, and experience we acquire.</p><p>And the world has operated like that for much of its history, in a predictable way.</p><p>That’s 𝗠𝗲𝗱𝗶𝗼𝗰𝗿𝗶𝘀𝘁𝗮𝗻, in Nassim Taleb’s words.</p><p>🚀 Yet, we increasingly live in 𝗘𝘅𝘁𝗿𝗲𝗺𝗶𝘀𝘁𝗮𝗻.</p><p>The distribution of events in today’s world is governed by power laws, where some events have a massive impact.</p><p>Covid, memes, Elon Musk, and the latest Hollywood blockbuster are all examples of Extremistan. Outcomes are not fairly distributed.</p><p>Career growth can be highly unpredictable in startups, where a single project, role, or joining the right company can catapult an individual to great heights.</p><p>Networking, luck, and being in the right place at the right time can disproportionately influence one’s career.</p><p>🎲 But the good news is 𝘭𝘶𝘤𝘬 𝘤𝘢𝘯 𝘣𝘦 𝘩𝘢𝘳𝘯𝘦𝘴𝘴𝘦𝘥.</p><p>I like how Naval describes it, based on James Austin’s book:</p><p>🔶 𝗟𝘂𝗰𝗸 𝗳𝗿𝗼𝗺 𝗠𝗼𝘁𝗶𝗼𝗻: “It comes through persistence, hard work, hustle. When you’re running around creating lots of opportunities, you’re generating a lot of energy; you’re doing a lot of things, and lots of things will get stirred up in the dust.”</p><p>🔶 𝗟𝘂𝗰𝗸 𝗶𝗻 𝗣𝗿𝗲𝗽𝗮𝗿𝗮𝘁𝗶𝗼𝗻: “You become very good at spotting luck. If you are very skilled in a field, you will notice when a lucky break happens in that field.”</p><p>🔶 𝗟𝘂𝗰𝗸 𝗨𝗻𝗶𝗾𝘂𝗲 𝘁𝗼 𝗬𝗼𝘂: “Which is where you build a unique character, a unique brand, a unique mindset, then luck finds you.”</p><p>Although technical skills and qualifications are still essential, soft skills and adaptability might come in handy in Extremistan.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/posts/eactisgrosso_why-do-some-people-get-promoted-faster-than-activity-7107331151094067200-FX9e"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a703314981" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ The Evolution (Cycles?) of Engineering Roles]]></title>
            <link>https://medium.com/@eactisgrosso/the-evolution-cycles-of-engineering-roles-3512837ce896?source=rss-883ae6009da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3512837ce896</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology-trends]]></category>
            <category><![CDATA[product-engineering]]></category>
            <dc:creator><![CDATA[Ezequiel Actis Grosso]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 12:57:30 GMT</pubDate>
            <atom:updated>2024-10-16T02:37:33.752Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IwmGAbsxmBjRIBbG" /><figcaption>T-Shaped Skills</figcaption></figure><p>I’ve noticed an interesting pattern in tech: history tends to repeat itself, or rather, work in cycles. When I started, wearing multiple hats was the norm. We coded, tested, handled support, and immersed ourselves in the business problems — all in a day’s work.</p><p>As the tech landscape became more complex, roles became more compartmentalized. Specialists emerged, with QA engineers, backend and frontend developers, sys admins, and others focusing on their specific domains. It was the era of deep expertise, of growing vertically, i.e., silos.</p><p>If you’ve worked with me, you have probably heard me mention three mental models to fight that cycle:</p><p>🔶 <strong>T-Shaped People</strong>: capable in many things (the horizontal bar of the T) and with deep knowledge in, at least, one (the vertical bar of the T). If you value the agile principle of “Responding to change over following a plan”, there’s nothing like T-shaped people for adapting to varying demand. With specialists and silos, you risk getting bottlenecks.</p><p>🔶 <strong>Drive</strong> — Autonomy, Mastery, and Purpose: I’ve cited Daniel Pink’s book insights more times than I can remember. I want my team to have the autonomy to make overarching decisions, master diverse skills, and be deeply intertwined with the purpose of the product they shape.</p><p>🔶 <strong>Theory X to Theory Y</strong>: Over the decades, I’ve seen management attitudes shift. From treating employees as cogs in a machine (Theory X) to understanding their innate drive and potential (Theory Y). This cyclical shift favors roles that encourage autonomy and innovative thinking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z05dcg5vsQweJkrS" /><figcaption>Theory X vs Theory Y</figcaption></figure><p>Now, observing the recent trends, it seems to be a re-emergence of the “T-shaped” mindset:</p><p>🔹 The sys admin’s decline, and the DevOps movement’s rise: “you build it, you run it”.</p><p>🔹 The decline of the dev/tester ratio: when you own operations, you’ll definitely care about testing. No one wants to get paged out of hours.</p><p>🔹 The push for Product Engineers: devs interested in the business, opinionated about the product, and actively engaging with the “why”.<br> <br>I really like seeing things come full circle. The essence of a developer is back but with a richer, more evolved persona.</p><p>What’s your take on these cyclical trends? Have you noticed them too?</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/decoding-conways-law-your-company-structured-success-actis-grosso"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3512837ce896" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decoding Conway’s Law: How Microservices Mirror Your Communication Flow]]></title>
            <link>https://medium.com/@eactisgrosso/decoding-conways-law-how-microservices-mirror-your-communication-flow-21bb12061965?source=rss-883ae6009da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/21bb12061965</guid>
            <category><![CDATA[team-topologies]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[technology-strategy]]></category>
            <category><![CDATA[organizational-design]]></category>
            <dc:creator><![CDATA[Ezequiel Actis Grosso]]></dc:creator>
            <pubDate>Tue, 15 Aug 2023 16:58:04 GMT</pubDate>
            <atom:updated>2025-07-28T20:09:09.513Z</atom:updated>
            <content:encoded><![CDATA[<h4>Is your company structured for success?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*lnmWlvXpQkxz7YWwo0uyNQ.png" /><figcaption>Manu Cornet / <a href="http://www.bonkersworld.net/">www.bonkersworld.net</a></figcaption></figure><p>There’s a phrase attributed to a well-known Argentinian politician that states:</p><blockquote><em>If you want something not to get done, create a committee.</em></blockquote><h3>Conway’s Law in Action</h3><p>Coincidentally enough, between that politician’s periods in office, a programmer named Melvin E. Conway published a paper titled “How Do Committees Invent?” whose most remarkable feature is now called Conway’s law:</p><blockquote><em>Any organization that designs a system will produce a design whose structure is a copy of the organization’s communication structure.</em></blockquote><p>Let’s unpack that.</p><p>Have you ever seen a busy home page that looked like the result of a power struggle between business units?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JxLrlrREX0zzWUq5FaUVEA.png" /><figcaption>Daniel Rabinovich (Mercado Libre COO) presentation at Endeavor Argentina</figcaption></figure><p>That’s Conway’s law at play.</p><p>Have you experienced software development teams bottlenecked by waiting on each other? Or building services whose names resemble their inner workings rather than the domain boundaries of the business model? That’s probably because they are playing against Conway’s law.</p><p>Subconsciously -or not- businesses will create systems that closely mirror how they communicate internally -or get blocked trying to develop systems that go against that communication structure-. And that problem has been exacerbated ten-fold by companies going remote without adequately and explicitly designing that structure to account for async work, time differences, or even leadership styles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L3PEKZZuHGq65-0Z4gDeJw.jpeg" /></figure><p>It amazes me how many companies undergoing a digital transformation are still trying to transplant “squads” or “agile” concepts over organizational silos and hierarchical structures. And I sympathize with the engineers and managers involved in those processes because <strong>no amount of software architecture or design will enable fast flow in teams organized in a way that introduces friction and bottlenecks</strong>.</p><p>Architecture modernization and transformation projects usually imply migrating from a monolith to a microservices architecture or from on-premises to the cloud, and that’s never a purely technical endeavor.</p><p>For instance, the overhead of a microservices architecture won’t be worth it if your team is a single large unit. And even if you have multiple autonomous teams, the design of those teams’ communications will likely dictate your software architecture, not vice versa.</p><p>Take the following example from the book <a href="https://www.amazon.com/Team-Topologies-Organizing-Business-Technology/dp/1942788819">Team Topologies</a>. Say that you have four teams comprised of FE and BE developers that hand over changes to a central DBA for database changes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Q96eX_QJeMpCeuWV" /><figcaption>Team Topologies — Four Teams Working on a Software System</figcaption></figure><p>The software architecture most likely to emerge from such a team design, would have separate frontend and backend components for each team, and a single, shared core database:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*1qoIjorwjnGCiimj" /><figcaption>Team Topologies — Software Architecture from Four-Team Organization</figcaption></figure><p>A shared DBA team will promote using a single shared database, and separate frontend and backend developers will likely create separation between UI and app tiers.</p><p>If you don’t want a single shared database, that’s a problem.</p><h3>The Inverse Maneuver</h3><p>So, how can one increase the chances of building highly cohesive, loosely coupled architectures optimized for fast flow?</p><p>In the <a href="https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339">Accelerate book</a> Jez Humble and Gene Kim research lent support to the “Inverse Conway Maneuver”, which states:</p><blockquote><em>Organizations should evolve their team and organizational structure to achieve the desired architecture. The goal is for your architecture to support the ability of teams to get their work done-from design through to deployment-without requiring high-bandwidth communication between teams.</em></blockquote><p>Taking the example from the previous section, if we want to achieve a microservice architecture with independent data stores, we can design the teams to match the desired architecture by having separate developers for the client apps and the API, and a database developer within each team:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*cdUoPCuZmrDYpRya" /><figcaption>Team Design for Microservices Architecture with independent data stores</figcaption></figure><p>The <a href="https://www.amazon.com/Team-Topologies-Organizing-Business-Technology/dp/1942788819">Team Topologies</a> book also introduces <a href="https://teamtopologies.com/key-concepts">four fundamental topologies and three interaction modes</a> to help approach team design.</p><p>The challenge is understanding what software architecture is needed <strong>before</strong> organizing the teams.</p><h3>How to Start the Journey</h3><p>Ideally, starting a digital transformation or an architecture modernization approach informed by Conway’s law will require investing time to collaborate across silos and connecting architectural decisions with strategy and business outcomes. <a href="https://www.wardleymaps.com/">Wardley maps</a>, <a href="https://www.eventstorming.com/">business modeling</a>, <a href="https://www.youtube.com/watch?v=Stc0beAxavY">JTBD</a>, <a href="https://www.whatmatters.com/faqs/okr-meaning-definition-example">OKRs</a>, and many other tools and frameworks can help to design and align teams and their work. But more often than not, I’ve witnessed technical teams wanting to jump immediately into a monolith to microservices migration, and, in my experience, the “divide and conquer” algorithm rarely works in those situations. On the contrary, it risks becoming an integration hell down the road, because it is challenging to determine the boundaries of the domain/services upfront.</p><p>So, if you really can’t dedicate time or prefer to do product discovery along the way, it’s usually better to do “ <a href="https://jchyip.medium.com/conquer-and-divide-ba6cdcfcf122">conquer and divide</a>”, and keep the monolith until there’s enough visibility of those boundaries:</p><blockquote><em>In XP, we don’t divide and conquer. We conquer and divide. First we make something that works, then we bust that up and and solve the little parts.</em></blockquote><blockquote>Kent Beck</blockquote><p>The other suggestion would be applying a <a href="https://martinfowler.com/bliki/StranglerFigApplication.html">strangler pattern</a> to progressively sunset the monolith, rather than migrating to a microservices architecture in one go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G59b4txSzjMEyfKZ" /><figcaption>Stranger Fig — Confluent</figcaption></figure><p>That way, the teams’ cognitive load can increase progressively instead of becoming overwhelming too fast. And, if you want to assess the team’s cognitive load, there’s a <a href="https://github.com/TeamTopologies/Team-Cognitive-Load-Assessment">template</a> that the Team Topologies team has made available.</p><h3>Key Takeaways</h3><ul><li>The structure of systems designed by an organization will mirror that organization’s internal communication.</li><li>Many companies attempt to adopt modern practices such as “squads” or “agile” without addressing the foundational organizational and communication structures, leading to inefficiencies and bottlenecks. Companies transitioning to remote work face amplified challenges related to Conway’s Law,</li><li>Designing teams properly is crucial for a successful software architecture. Understanding the desired architecture before organizing the teams is essential.</li><li>Rushing from a monolithic system to a microservices one without proper preparation can lead to integration issues and increase cognitive load.</li></ul><h3>Have you experienced some of these problems?</h3><p>If you need help with a digital transformation or an architecture modernization project, drop me a line and let’s have a chat!</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/decoding-conways-law-your-company-structured-success-actis-grosso"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21bb12061965" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Ride the Argentinian Rollercoaster with Shorter Development Cycles]]></title>
            <link>https://medium.com/@eactisgrosso/how-to-ride-the-argentinian-rollercoaster-with-shorter-development-cycles-c07f89e7cc76?source=rss-883ae6009da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c07f89e7cc76</guid>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ezequiel Actis Grosso]]></dc:creator>
            <pubDate>Wed, 24 Oct 2018 20:05:39 GMT</pubDate>
            <atom:updated>2018-10-24T20:05:39.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GcRyEmD6zLEvVkRk3thagg.png" /></figure><h4>A Real-World Use Case</h4><h3>A really dynamic business environment</h3><p>A few months ago, the Argentinian peso lost almost 20% of its value in a day, and the interest rate climbed to 60% — the world’s highest. If you didn’t grow in Argentina as I did, it might strike you as a black swan event, but, it has happen before:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-bVcE9cw5I9kaYrVoyclhA.png" /></figure><p>…and even worse:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-xvo8FOW7BlLZadabf_KtA.png" /></figure><p>For a <a href="https://www.linkedin.com/company/mg-group-s-a/">company that offers loans to individuals</a>, that’s usually bad news. Almost every other company in the same line of business was shutting down their loan request websites and apps until further notice, which didn’t seem like a bad idea considering how difficult it is to keep the business of lending money running without a reference rate.</p><p>Fortunately, our team shines when it comes to thinking out of the box, and the sales and tech teams came up with an idea to keep taking loan requests from customers, even when we weren’t able to offer an exact amount of money until the country were back on track:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3bqiWVG-0QPlM1zmfnAsg.png" /></figure><p>The “Undefined Rates” flag allowed our app and website to continue running as usual, capturing customer requests and evaluating credit risks, but instead of giving automatic approvals we offered pre-approved loans.</p><p>We could even target specific users and test it directly in production before turned it on (the same mechanism that can be used for <a href="https://vwo.com/ab-testing/">A/B testing</a>):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*B7AKKGrmKTR05HSR3DJ6ow.png" /></figure><blockquote><em>And it was ready to be turned on in production in less than an hour after the idea emerged.</em></blockquote><h3>The Foundations of Agility</h3><p>The implementation of the feature, and the commit to the codebase that triggered the deploy to production, were done by Aylen, a developer that joined our team just<strong> a few months ago</strong>. And it was done <strong>from her home</strong>. And even when it was a Friday afternoon close to 6pm, <strong>she volunteered</strong>.</p><p>As many other companies we could have centralized critical parts of our codebase in the hands of the most experienced developers. We could also have several approval steps before releasing software to production. We could have forbidden working from home. <strong>But we did none of that</strong>. We created a work environment with <strong>high levels of autonomy</strong>.</p><blockquote><em>Even more important than any agile methodology or devops environment, is the removal of barriers preventing the delivery of added value.</em></blockquote><h4>Data Driven Culture</h4><p>The first step for achieving high levels of autonomy is to get rid of the need for micromanagement by agreeing on the metrics relevant to the business (like the <a href="http://startitup.co/guides/374/aarrr-startup-metrics">Pirate metrics</a>, for instance), and building a data driven culture. As Eric Schmidt wrote in “How Google Works”, <strong>don’t listen to the HiPPos </strong>(Highest-Paid Person’s Opinion), or, as stated in the now famous quote from Jim Barksdale “If we have data, let’s look at data. If all we have are opinions, let’s go with mine”.</p><p>Once it is clear how to measure success, it is easier to align the work of each contributor to the organization’s objectives (by means of <a href="https://en.wikipedia.org/wiki/OKR">OKRs </a>or similar frameworks), without having to resort to micromanagement, and the notions of place and time where the work is done, become less relevant.</p><h4>Lean Experimentation</h4><p>The next step towards agility is to <strong>embrace uncertainty</strong>, and to <strong>take risks</strong>.</p><p>It would be very difficult for us to provide solutions like the one I mentioned in the beginning of this article, if we had to ask for permission at every step of the way. Even with a good amount of automated tests and coverage, we make mistakes. But we learn from each of them. We improve our decisions based on them, and we get insights that we wouldn’t get otherwise.</p><p>The <a href="http://theleanstartup.com/">Lean Startup</a> method focuses on testing new ideas as iterative experiments, and validate them against our existing or potential customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWtQlcokiTFY7JaiBL863g.jpeg" /></figure><blockquote>Decks of cards that we bought from <a href="http://cards.ui-patterns.com/">UI Patterns</a> for, among other things, validate lean product experiments through common patterns, regularly used by product proffesionals at companies like Spotify, Booking.com, Facebook, Amazon, and Google and recommended by top universities like Havard, MIT, and Stanford</blockquote><p>There is a great deal of ideas that can be learned from the <a href="https://www.ideou.com/pages/design-thinking">Design Thinking</a> world and applied to software development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mwRAoOXLfzCmlnH5fjIM3A.png" /></figure><p><em>via </em><a href="https://medium.com/@geertwlclaes/when-which-design-thinking-lean-design-sprint-agile-a4614fa778b9"><em>When, which … Design Thinking, Lean, Design Sprint, Agile? by Geert Claes</em></a></p><h4>Continuous Delivery and DevOps</h4><p>Lean experiments can happen in any development environment, but work best when built on a solid foundation of <a href="https://aws.amazon.com/devops/continuous-delivery/">Continuous Delivery</a> and <a href="https://aws.amazon.com/devops/">DevOps</a>. I very much like the definition of DevOps provided by aws as:</p><blockquote><em>“the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity”</em></blockquote><p>We recently gave a talk with <a href="https://www.linkedin.com/in/gustavo-ruscitto/">Gustavo Ruscitto</a> at AWS Startup Days in Argentina, in which I said that no one in our team has to ask for permission to deploy to production. No one has to wait for a particular hour or day. We deploy all the time, at any time. That would be impossible to achieve if there were a person in charge of moving software to production.</p><p>If you feel like watching the “techie” part of the talk, in Spanish, and recorded with a phone 🤷, here goes the link:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FM3uBX3GydPY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DM3uBX3GydPY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FM3uBX3GydPY%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/81b2778dbc7ea20c112f055860e792c2/href">https://medium.com/media/81b2778dbc7ea20c112f055860e792c2/href</a></iframe><h3>How to Measure Flow</h3><p>In addition to measuring business metrics (the ones that tell us how efficiently we are meeting the market need), we are constantly trying to improve the agility of our delivery process, our “Flow”, with the help of some diagrams:</p><p><strong>Control Chart</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M_3jJ3UCIXVcnFzV1X-yMA.jpeg" /></figure><p>The control chart shows the amount of time an issue or a story spent in a given set of states, in our case, from “In Progress” to “Done”. That is, the time it takes for a given workitem, once works begins, to be ready to be used for our customers in Production (also known as Cycle Time).</p><p>Even when our average cycle time of the last eight weeks is 4 days, we aim to reduce the standard deviation cycle days when the cost of delay is high.</p><p><strong>Cumulative Flow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UuKbdPQikmRLe6x7orlQnQ.jpeg" /></figure><p>One of the best books I have read on the subject of improving Flow, is <a href="https://www.amazon.com/Principles-Product-Development-Flow-Generation/dp/1935401009">The Principles of Product Development Flow</a>, where Donald Reinertsen explains why invisible and unmanaged queues are the underlying root cause of poor product development performance. One of the most useful tools for managing queues is the Cumulative Flow Diagram.</p><p>In the example above (from one of our software components), the area of “In Progress” and “Ready for Test” items, before applying <a href="https://kanbantool.com/kanban-wip-limits">WIP limits</a>, was to wide. For example, in July 30 there were 7 items “In Progress” and 17 “Ready for Test” items, with a the team of only 6 developers. If we were a manufactoring company, the factory floor would become crowded with cases of work-in-process inventory. That is, increased cycle time, delayed feedback, and poor economic performance. After applying limits to the amount of items that can exists in a given state, the focus of the team shifted, from taking new work to making sure than the finished work was already adding value to the customer in Production.</p><p><strong>Throughput</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CdqVgChpgjd2OjOPw2Ay7w.jpeg" /></figure><p>The Throughput Diagram shows the amount of workitems delivered to the customer in a given period of time. The objective, of course, is to continuously improve it.</p><p>In the example above, the average of 12 workitems per week for a team of 6 developers can be used for planning purposes and rough estimates, but, what is more important, the variability can shed some light on the impact of factors like story size, complexity, urgency, and person’s skills.</p><blockquote><em>While “ </em>manufacturing deals with predictable and repetitive tasks, homogeneous delay costs, and homogeneous task durations<em>” and “</em>manufacturing sequences work in a simple first-in-first-out (FIFO) order”<em>.</em>”FIFO prioritization is almost never economically optimal in product development, because product development deals with high variability, nonrepetitive, nonhomogeneous flows. Different projects almost always have different delay costs, and they present different loads on our resources.<em>”</em></blockquote><blockquote><em>Reinertsen, Donald G. The Principles of Product Development Flow</em></blockquote><h3>Conclusion</h3><p>I recognize that Argentina is an extreme example of a rapidly changing business environment, but in an exponential world where the knowledge will double every 12 hours, is it too far fetched to think that fast-paced business environments will be the norm?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*opkE4ngPNVETWQcLyyArdQ.jpeg" /></figure><p>Maybe the critical competitive advantage will be defined by how teams develop new abilities, learn by trying and failing, adapt, and make the process part of their DNA.</p><p><em>Thanks for sticking around! If you made it through this rather lengthy article, I hope you learned something valuable.</em></p><p><em>If you have any questions or comments, please let me know, I will be more than happy to chat about these topics or any other related. If you are in Rosario, you can also join our meetup at </em><a href="https://www.meetup.com/Rosario-Lean-Startup-Meetup/"><em>Rosario Lean Startup</em></a><em>.</em></p><p><em>If you are a developer, designer, data scientist, and would like to join our team working remotely, please drop me a message.</em></p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/how-ride-argentinian-rollercoaster-shorter-cycles-actis-grosso/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c07f89e7cc76" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adapting to business changes with React apps and containerized .NET Core microservices]]></title>
            <link>https://medium.com/@eactisgrosso/adapting-to-business-changes-with-react-apps-and-containerized-net-core-microservices-9c2fa8b220f1?source=rss-883ae6009da5------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c2fa8b220f1</guid>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[net-core]]></category>
            <dc:creator><![CDATA[Ezequiel Actis Grosso]]></dc:creator>
            <pubDate>Sun, 08 Apr 2018 14:53:56 GMT</pubDate>
            <atom:updated>2018-05-03T12:14:01.256Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nqbF_7xl44i2rOZ_wxPb2A.jpeg" /></figure><h4>10+ Deploys Per Day to Production</h4><h4>The Great Convergence</h4><p>A big part of my work as VP of Software Engineering has to do with two related concerns:</p><ul><li><em>Reducing the product development lead time</em></li><li><em>Recruiting smart and highly motivated individuals, training them, and staying out of their way</em></li></ul><p>Time has become the key competitive advantage for businesses all around the world, and from Facebook motto of “Move fast and break things” to Netflix <a href="https://jobs.netflix.com/culture">culture deck</a>, encouraging team members to make independent decisions has proved to be a prerequisite, not only for moving fast and being innovative, but also to attract great talent.</p><p>Fortunately, over the last few years the software development landscape has experienced a convergence between <a href="http://agilemanifesto.org/">agile</a> methodologies and <a href="https://martinfowler.com/bliki/DevOpsCulture.html">DevOps</a> practices, architectural styles such as <a href="http://microservices.io/">microservices</a> and <a href="http://alistair.cockburn.us/Hexagonal+architecture">hexagonal architectures</a>, and platforms such as <a href="https://www.docker.com/">Docker</a> and <a href="https://aws.amazon.com/ecs/">Amazon ECS</a>, which have paved the way and enabled businesses to move faster than ever, empowering individuals to take calculated risks, which, as a result, has led to shortening the release cycles and improving scalability and availability.</p><blockquote>Docker provides a way to run applications securely isolated in a container, packaged with all its dependencies and libraries. (source:docker.com)</blockquote><h4>Eliminating Waste</h4><p>Our current development workflow at <a href="https://www.linkedin.com/company/18366690/">MG Group</a> (based in Rosario, Argentina, the land of Messi, in case you wonder) can be summarized as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vLUhK_jjqFZNpJf2x3C8Ug.jpeg" /><figcaption>Development workflow</figcaption></figure><p>As many other manufacturing principles and tools applied to software, the Kanban Board has given us great results in keeping the time between the initiation and delivery of a work item to a bare minimum (following the principle of lean manufacturing of eliminating waste). Each story’s status is mapped to a branch in the code repository, which in turn is mapped to an environment: we only consider a story done when it is deployed to a test environment, and shipped when it is ready for our customers to use.</p><p>We don’t have a dedicated team (or even a person) that takes care of the infrastructure, but rather a team of developers that knows exactly how the code they write is run in production. They commit their code to the repository alongside with the instructions for running it in every environment:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/09a61794d5c6db580f8f2e4619a727c4/href">https://medium.com/media/09a61794d5c6db580f8f2e4619a727c4/href</a></iframe><p>Once the code is pushed, the CI server (Jenkins) builds and uploads:</p><ul><li>.NET Core docker images of our microservices to <a href="https://aws.amazon.com/ecr/">Amazon ECR</a></li><li>Workers to <a href="https://aws.amazon.com/lambda/">lambda</a></li><li>React files to <a href="https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html">Amazon S3</a></li></ul><p>And updates the services and tasks definitions in order to enable Amazon ECS to run what is called a <a href="https://martinfowler.com/bliki/BlueGreenDeployment.html">blue/green deployment</a>, draining connections from the current version of the container and registering the new one with the application load balancer as it come online.</p><blockquote>All within five minutes after the code has been pushed to the master branch, with zero downtime.</blockquote><blockquote><a href="https://jenkins.io/">Jenkins</a> is an automation server that run jobs triggered by various means, for example by a commit in a version control system. Its functionality can be extended with <a href="https://en.wikipedia.org/wiki/Plug-in_(computing)">plugins</a>, and supports implementing continuous delivery pipelines. (source: Wikipedia)</blockquote><p>If you want to give it a try, we have a <a href="https://hub.docker.com/r/eactisgrosso/jenkins-netcore/">prebuilt Jenkins image</a> available in Docker Hub, bundled with .NET Core, AWS CLI and pre-installed plugins.</p><h4>Achieving Freedom</h4><p>The containerized deployment of microservices on ECS not only eliminates the need of managing virtual machines, but also produces valuable byproducts such as:</p><ol><li>Zero Downtime</li><li>Auto-scaling</li><li>Self-healing</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jHNqorhyHokz9Q4ekBGcEg.png" /></figure><p>And, more importantly, by means of the blue/green mechanism, deployment becomes routine and low risk, allowing us to push our code to production as many times per day as we need, experimenting and testing new business ideas as they arise, and discovering what creates the most value for our customers.</p><p><em>In subsequent posts the team and I will be digging deeper into Docker, Amazon ECS, Lambda, .NET Core microservices (DDD/CRQS/Event Sourcing), React.js and a lot more. You can find the spanish version of this post in </em><a href="http://blog.mg-group.net.ar/es"><em>our blog</em></a><em>.</em></p><p><em>If you have any comments, suggestions or questions, please chime in below!</em></p><p><em>If you are in Argentina, and especially in Rosario, </em><strong><em>we are always </em></strong><a href="http://bit.ly/2Aby6YV"><strong><em>hiring</em></strong></a><strong><em> </em></strong><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c2fa8b220f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>