<?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 Vibhu Pratap on Medium]]></title>
        <description><![CDATA[Stories by Vibhu Pratap on Medium]]></description>
        <link>https://medium.com/@vibhu.pratap?source=rss-74ad10731069------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Vibhu Pratap on Medium</title>
            <link>https://medium.com/@vibhu.pratap?source=rss-74ad10731069------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:06:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vibhu.pratap/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[Micro-Iterators will inherit the earth]]></title>
            <link>https://medium.com/@vibhu.pratap/micro-iterators-will-inherit-the-earth-c92edf9645e7?source=rss-74ad10731069------2</link>
            <guid isPermaLink="false">https://medium.com/p/c92edf9645e7</guid>
            <dc:creator><![CDATA[Vibhu Pratap]]></dc:creator>
            <pubDate>Tue, 08 Jul 2025 05:11:36 GMT</pubDate>
            <atom:updated>2025-07-08T05:11:36.634Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/993/0*eNN61DQuCNSnD-Bv" /></figure><p><em>How small bursts of human creativity paired with AI execution will reshape our world</em></p><blockquote>Part 1 of a 4-part series on survival in the AI age</blockquote><p>The biblical promise that “the meek shall inherit the earth” may have found its modern translation: the microiterators will inherit the earth. This observation started as a single line I posted on LinkedIn after a robust discussion over Indian tea about how creators are adapting to AI. That conversation, and the responses it generated, convinced me there was something worth exploring more deeply.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/0*hrru0l-YmtIhsPXh" /></figure><p>Peter Sims demonstrated in his excellent book “Little Bets” how breakthrough innovations often emerge from small discoveries rather than grand plans. Now, in our AI-amplified world, this insight has evolved into something more powerful: the future belongs not to those who can execute at massive scale, but to those who can generate tiny sparks of creativity and let artificial intelligence transform them into reality at unprecedented speed.</p><p>This is the first in a four-part series exploring my observations on how to survive in the AI age. While others debate whether AI will replace human creativity, I’ve noticed a different pattern emerging — one where the most successful creators are learning to work <em>with</em> AI in precise ways that amplify their capabilities without surrendering their agency.</p><blockquote><em>A caveat before we dive in: the pace of change we’re experiencing is unprecedented. No one truly knows what the future holds in this AI-accelerated world. What I’m sharing here are, at best, educated guesses.</em></blockquote><h3>The Death of the Marathon Creator</h3><p>The traditional model of creation is becoming extinct. I’m seeing this across teams and individuals I work with. We’re entering the age of the creative sprinter, where value lies not in sustained effort but in the ability to generate brilliant micro-insights.</p><p>AI has fundamentally changed the economics of creation. When implementation can happen in hours rather than weeks, the bottleneck shifts from execution capacity to creative direction. The question becomes: what do you want to build, rather than how long it will take to create it?</p><h3>What Are Microiterators?</h3><p>From my observations, microiterators are individuals who have adapted to this new reality by fundamentally changing how they approach creative work. They operate differently:</p><p>They generate small, focused bursts of creative insight rather than attempting to plan everything. Think of it as creative sprinting instead of creative marathons.</p><p>They rapidly test and refine ideas through quick cycles. I’ve watched developers break down complex features into tiny, testable pieces that can be validated in minutes rather than months.</p><p>They leverage AI to handle execution while maintaining control. This is the crucial part — they don’t hand over creative control to AI; they use AI as an execution engine for their ideas.</p><p>They focus on the “what” and “why” while AI handles the “how.” Strategic thinking remains human; implementation receives AI amplification.</p><h3>The New Creative Mathematics</h3><p>What I’ve observed is a fundamental shift in how creative output gets generated:</p><pre>Human Creativity (Micro) + AI Execution (Macro) = Exponential Output</pre><blockquote><em>Traditional creativity required both the spark and the sustained effort to bring ideas to life. Now, the spark alone — if properly directed — can ignite entire systems of AI-powered execution.</em></blockquote><h3>Why Microiterators Are Winning</h3><h3>The Small Bets Advantage</h3><p>Building on Sims’ Little Bets methodology, microiterators transform innovation economics by placing many small bets instead of few large ones. What I find fascinating is how this dramatically increases the scope for success:</p><ul><li><strong>Statistical probability works in your favor</strong> — more attempts mean a higher likelihood of breakthrough discoveries.</li><li><strong>Risk gets distributed </strong>— no single failed iteration can derail your entire project.</li><li><strong>Learning compounds</strong> — each small bet teaches you something that improves the next bet.</li><li><strong>Unexpected wins emerge</strong> — solutions often come from directions you didn’t initially consider.</li></ul><h3>Speed Over Stamina</h3><p>In conversations with successful creators, a pattern emerges: those thriving in the AI age aren’t the ones who can grind the longest. They’re the ones who can generate quality creative direction most frequently. The bottleneck isn’t execution speed — it’s the quality and frequency of creative insights.</p><h3>Cognitive Arbitrage</h3><p>While others exhaust themselves on implementation details, microiterators conserve mental energy for what matters most: original thinking, pattern recognition, and creative problem-solving. They’ve learned to delegate the heavy lifting while retaining the high-value decision-making.</p><h3>Sustainable AI Partnership</h3><p>Here’s what sets them apart from those who become AI-dependent: microiterators keep AI contributions small and contained. They get AI’s speed benefits without sacrificing long-term maintainability or becoming dependent on systems they can’t understand or debug.</p><h3>A Pattern I Keep Seeing</h3><p>The developers who exemplify this approach have mastered breaking down complex problems into manageable pieces. Instead of submitting massive pull requests, they stick with the following workflow:</p><ul><li>Decompose features into atomic changes.</li><li>Submit small, focused PRs that get reviewed quickly.</li><li>Build useful functionality incrementally.</li><li>Create faster feedback loops while reducing integration risk.</li><li>Ship value continuously rather than in significant, risky releases</li></ul><p>While their colleagues struggle with merge conflicts and lengthy code reviews, these developers compound their progress through dozens of small, solid iterations. Each commit represents tested, useful functionality that builds toward larger goals.</p><h3>The Inheritance</h3><p>Just as the meek were promised the earth through patience and humility, microiterators will inherit the digital world through creativity and adaptability. They understand that in an age of artificial intelligence, the most powerful position isn’t to compete with machines but to direct them intelligently.</p><p>The future belongs to those who can think in bursts, create in cycles, and let AI amplify their imagination into reality. They are the new meek, not because they lack ambition, but because they understand that true power lies in generating endless small beginnings rather than executing single grand finales.</p><h3>What’s Coming</h3><p>This approach raises important questions about creativity, learning, and human development that I want to explore further:</p><ul><li>Part 2: How does this build on proven innovation methodologies and the practical workflow that makes it work?</li><li>Part 3: The technical philosophy of maintaining control while leveraging AI execution</li><li>Part 4: The challenge of developing creative foundations in a world of AI amplification</li></ul><p>The microiterators are already inheriting the earth — one small iteration at a time. The question is: Will you join them, or will you get sidelined in due time?</p><p><em>This is Part 1 of my observations on survival in the AI age. I would love to hear your thoughts on the patterns you’re seeing in your work.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c92edf9645e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Self Driving Software Stack]]></title>
            <link>https://medium.com/@vibhu.pratap/self-driving-software-stack-5776f2965ac6?source=rss-74ad10731069------2</link>
            <guid isPermaLink="false">https://medium.com/p/5776f2965ac6</guid>
            <category><![CDATA[self-driving]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Vibhu Pratap]]></dc:creator>
            <pubDate>Tue, 20 Aug 2019 03:16:15 GMT</pubDate>
            <atom:updated>2019-08-20T03:16:15.393Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*WovYsR9qE5bTvJEQ" /><figcaption><a href="https://europe.autonews.com/automakers/daimler-bmw-deepen-cooperation-self-driving-venture">https://europe.autonews.com/automakers/daimler-bmw-deepen-cooperation-self-driving-venture</a></figcaption></figure><p>About a year back, while jostling with the complexity of integrating multiple open source software, I had put the following update on my LinkedIn profile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Cq5NECohMusDCxcG" /></figure><p>This was just the beginning of the journey, and more frustrations were in store as is evident by the next few updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3R2pM0loc4l-m4IQ" /></figure><p>The reason for going back and looking at the past updates was because of two exciting announcements last week, which when coupled together, can reduce some of these frustrations that I had encountered. These announcements (one big and another small) that caught my attention were:</p><ul><li>VMWare acquisition of Bitnami: VMWare has finally caught up with application orchestration and is trying to become relevant for developers with the acquisition of <a href="https://cloud.vmware.com/community/2019/05/15/vmware-to-acquire-bitnami/">Bitnami</a>. For a company who was at the forefront of virtualization, it has been a tough time to stay relevant in the cloud age. Most of their efforts to make a dent have fallen short. In my opinion, this acquisition is at least three years late.</li><li>Launch of AI-based database: Huawei launches <a href="https://techcrunch.com/2019/05/14/huawei-cloud-database/">AI-based database</a> to target enterprise customers: a database with Machine Learning capabilities for Indexing, caching, tuning, etc.</li></ul><p>I am sure Huawei’s announcement is just the beginning of a Self Driving Software Stack movement where an AI-based system will circumvent the problems encountered during the integration, operationalization, and subsequent optimization of open-source software.</p><blockquote>The orchestrator which can look at the condition of running system and automatically tune the configuration of infrastructure software( database, message queues, cache, replication) on which business application is working will be a worthy investment.</blockquote><p>The idea for VMWare will be to play a long game, as it did with virtualization and use Bitnami to build the next generation orchestration/monitoring system; one with more broader capabilities than Huawei has announced. Too much OpEx is being spent on just making on-premise distributed system work. A well thought out Bitnami evolution for the future will be beneficial to all.</p><h3>Afterthought</h3><p>While going through my twitter feed I encountered the following tweet about the spend from Microsoft on what they call as a “New Stack”.</p><h3>Value_Biased on Twitter</h3><p>MS continuing to do good work on the &quot;New Stack&quot; that is rapidly emerging within the application development &amp;amp; deployment software market.</p><p>This emerging stack is what is poised to enable the agility in enterprises. In the past, it took a few years to train an average developer to be productive on Highly Available carrier-grade enterprise application. The cloud promises that the developers trained in writing native applications on New Stack with ingredients of Self Driving, as suggested in this writeup will become a genuinely agile playing ground.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5776f2965ac6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Twelve Labors for a Software Leader]]></title>
            <link>https://medium.com/@vibhu.pratap/twelve-labors-for-a-software-leader-7101ea80171e?source=rss-74ad10731069------2</link>
            <guid isPermaLink="false">https://medium.com/p/7101ea80171e</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Vibhu Pratap]]></dc:creator>
            <pubDate>Wed, 17 Oct 2018 13:47:15 GMT</pubDate>
            <atom:updated>2018-10-17T13:47:15.056Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*u8qBtcDTPYT40S2uVpPk0A.jpeg" /><figcaption><a href="http://01greekmythology.blogspot.com/2015/01/twelve-labors-of-hercules.html">http://01greekmythology.blogspot.com/2015/01/twelve-labors-of-hercules.html</a></figcaption></figure><p>The <a href="https://en.wikipedia.org/wiki/Labours_of_Hercules">Twelve Labours of Hercules</a> are a series of episodes concerning a penance carried out by <a href="https://en.wikipedia.org/wiki/Heracles">Hercules</a>, the greatest of the Greek heroes. They were accomplished over 12 years at the service of King <a href="https://en.wikipedia.org/wiki/Eurystheus">Eurystheus</a>.</p><p>The similar extent of labors, albeit a tad different, is required from a leader during Software Product Development. In this piece, I am going to share my experiences, especially over the last five years. These salient points have helped me in providing to my team, a balance between innovation &amp; execution on one side and reducing friction &amp; enhanced productivity on the other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/0*5iBrc7etOp2Idnmb" /></figure><ul><li><strong>Team Building</strong>: Attracting the right talent into your team is a remarkably laborious and exhausting process. You have to show perseverance and flexibility to assemble a balanced and resilient execution engine. A leader incapable of building a team sooner or later will become incapacitated. The goal is to find individuals who solve problems evenhandedly, systematically &amp; permanently. Once done, a cycle of delegation, trust and debrief can be repeated.</li><li><strong>Platformification of Architecture</strong>: The role of a platform is succinctly put in this highly recommended <a href="https://www.amazon.com/Platform-Revolution-Networked-Markets-Transforming/dp/0393354350/ref=sr_1_1?ie=UTF8&amp;qid=1538693051&amp;sr=8-1&amp;keywords=platform+revolution&amp;dpID=51JE4mwww0L&amp;preST=_SY291_BO1,204,203,200_QL40_&amp;dpSrc=srch">reading</a>.</li></ul><pre>The technicalities of a platform, a business thinking that enables <br>a value-creating ecosystem between eternal participants - producers <br>and consumers - as an antithesis of a traditional pipeline business. </pre><pre>These stakeholders &quot;connect and conduct interactions with one another <br>using the resources provided by the platform. In the process, they <br>exchange, consume, and sometimes co-create something of value&quot;&quot;.</pre><p>The architecture of the system needs to be thought in terms of shared services and repetitive patterns which need to be made available in a horizontal layer of functionality. New functionality added therein should continue extending this horizontal layer. This activity in due time leads to economies of scale and for the product to thrive.</p><ul><li><strong>Bookending</strong>: The complexity of bringing a system together and the constraints it needs to exist within should be specified early on. Architecture/ design/ implementation decision falling outside the realm of these constraints need to be addressed. Read my detailed thoughts on this topic <a href="https://www.linkedin.com/pulse/bookending-your-problem-domain-vibhu-pratap/">here</a>.</li><li><strong>Developer Experience</strong>: One of the most critical resources in teams developing products is the developer’s time. It needs to be guarded with the same zeal as you guard the simplicity of the product and accrual of Technical Debt. The environment in which the developer can be most productive has to be available with little to no friction. Read my detailed thoughts on this topic <a href="https://www.linkedin.com/pulse/developer-experience-what-art-thou-vibhu-pratap/">here</a>.</li><li><strong>User Experience</strong>: Google’s spectacular success had led all products owners to realize that they need to simplify the interfaces rather than complicate it. The technical prowess of the backend system should be simplified to a large extent and encapsulated into intuitive workflows for the users. Manage the power users who form a vocal minority and keep demanding complex features.</li><li><strong>Documentation Experience</strong>: Documentation is a critical touch point with the customer. Developers aversion to context switch to other tools regularly results in documentation becoming obsolete. Identification of tools within developers Integrated Development Environment(IDE) can enable contribution, hence creating Documentation As A Code (DAAC) environment.</li><li><strong>Agility</strong>: The nonlinear nature of product development resulted in the rise of Agile methodology. With agility in the mix, the development is iterative, can be continuously refined, made chunkable and less disruptive. It also makes sure the frequent checkpoints bubble up specific problems, and teams keep improving with continuous feedback.</li><li><strong>Automation</strong>: “Automate or Die” is not a slogan anymore, in the world of microservices and distributed systems where failures of components are the norm. The automation framework developed in an early phase of the project can be a difference between success and failure. The success of the automation framework depends on how easy it is to enhance and add new test cases, preferably in a data-driven way.</li><li><strong>Jenkinsification</strong>: Paul Graham from Y Combinator has four prophetic words, “Make Stuff People Want.” To develop the knack for building stuff people want, you should understand their needs profoundly. Jenkinsification (as I define it) is a process when your team members are proactively turning their modules, tools, and utilities into useful consumable entities for the rest of their colleagues. They also actively recruit internal customers, get feedback and enhance their creations. This results in raising the level of empathy towards the final customers.</li></ul><blockquote>Jenkins is a tool used for Continuous Integration of a software product.</blockquote><ul><li><strong>Marketers</strong>: Today’s software companies are striving to build a frictionless funnel for their teams to unleash creativity and innovation to get the finished product in front of their customers. To achieve it you need an intrepid team which can understand the customer pain points, iterate continuously and delivers what’s useful. The way to accomplish this would be to turn selective folks among designers, architects and technical leaders into marketers for their respective domains. Exposing them to customers, product management and other entities lead to unhinged value creation.</li><li><strong>Co-creation</strong>: For any product to be successful, it’s necessary to have its share of external participation during the creation process. These participants include product managers who interface with the customers, solution teams who test the product from the customers perspective, support engineers who provide first level support, an initial set of friendly customers and a hungry ecosystem partners who can innovate in and on the product.</li></ul><h3>The 12&#39;th Labor</h3><ul><li><strong>Achieving the Flow</strong>: “Flow-based Product Development suggests that our development processes can be both efficient and responsive in the presence of variability. To do this, we must make resources, people, and processes flexible.” An organization must strive to achieve this.</li></ul><blockquote><em>Excerpt From: Donald G Reinertsen. “The Principles of Product Development Flow”</em></blockquote><ul><li><strong>Culture Of Completion</strong>: Working in the team is more about optimizing and achieving better results which reach the customer. What needs to be calibrated and celebrated is a culture of doing and completing this impactful work.</li><li><strong>Norms of the Product Team</strong>: A set of commonsensical norms guiding the day to day execution. Read my detailed thoughts on this topic <a href="https://www.linkedin.com/pulse/norms-product-team-vibhu-pratap/">here</a>.</li><li><strong>The Delivery Gladiators</strong>: “It’s not the will to win that matters — everyone has that. It’s a will to prepare to win that matters”. The quote is by Paul William Bryant, arguably one of the best college football coaches in the history of the game. This job for a product is done by release managers who slug out daily in similar preparation to get the product to the market. Make sure you identify them early and empower them enough.</li></ul><h3>After the Labours</h3><p>The success of a product depends on a multitude of factors, other functional areas, customers, markets, strategic company direction, and internal politics. The team engaged in the creation of it needs to enjoy the journey and be a collector of experiences, experiences which you can tap into for future challenges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7101ea80171e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Future on the Edge]]></title>
            <link>https://medium.com/@vibhu.pratap/future-on-the-edge-c56b14f96d86?source=rss-74ad10731069------2</link>
            <guid isPermaLink="false">https://medium.com/p/c56b14f96d86</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[edge-computing]]></category>
            <dc:creator><![CDATA[Vibhu Pratap]]></dc:creator>
            <pubDate>Thu, 06 Sep 2018 02:16:37 GMT</pubDate>
            <atom:updated>2018-09-06T02:16:37.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*KY28IkHS-63H5fNHu69hrw.jpeg" /></figure><p><a href="http://www.johnhagel.com/">John Hagel</a>, one of the foremost strategists of our time, runs a fascinating blog called <a href="http://edgeperspectives.typepad.com/">The Edge Perspective</a>. One of his posts, <a href="http://edgeperspectives.typepad.com/edge_perspectives/2008/05/innovation-on-t.html">Innovation on the Edge</a>, is pure gold and is worth every minute of your time. The post is a summary of six articles he did for Business Week regarding his take on innovation. Quoting him verbatim “<strong>Over time, I have focused more sharply and explicitly on the importance of the edge as a source of value creation and strategic advantage.</strong>” Being a technologist and observing the new trends bubbling up, it seems John’s ideas around innovation literally and figuratively are mapping directly to the next-generation of computing waves ready to shore up the edge infrastructure. The commoditization<strong> </strong>of the edge is not a pipe dream anymore, it’s morphing, and it’s morphing fast into reality. To top it all off, edge computing now has real use cases behind it as is evident by the figure below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KFe0Su9PHAoLj1zW" /></figure><blockquote>Source : Unknown (Cannot defend the numbers)</blockquote><h3>Trends in the market</h3><p>Recent technology trends in the market are further fueling the ‘edge’ and helping it evolve as a wider funnel into the public cloud :</p><ul><li>Mobile Network evolution to <a href="https://en.wikipedia.org/wiki/5G"><strong>5G</strong></a>.<a href="https://5g.co.uk/guides/what-is-network-slicing/">Network slicing</a> required for the variety of use cases is already underway.</li><li>Massive <a href="https://www.forbes.com/sites/louiscolumbus/2016/11/27/roundup-of-internet-of-things-forecasts-and-market-estimates-2016/#600d200a292d"><strong>IoT proliferation</strong></a> including mission-critical ones like connected cars, health monitors, etc.</li><li>More intelligent <strong>IoT application</strong>(s) conjoined with purpose build IoT devices.</li><li><strong>The explosive growth of data, analytics</strong> and continuous demand for <strong>low latency as well as reducing bandwidth costs.</strong></li><li><strong>Distributed cloud</strong> models with concepts like fog computing.</li></ul><h3>Why is edge required?</h3><p>If the above trends are any indication, the next logical question to be asked is why these will require an edge evolution. The following are some of the reasons why an intelligent edge will be a necessity :</p><ul><li><strong>Compute:</strong> Latencies may deem computation on the centralized cloud useless.</li><li><strong>Storage:</strong> Not all data needs to go to the cloud, not all data has time to go to the cloud, not all data can go to the cloud.</li><li><strong>Networking:</strong> Security, Acceleration, Compression &amp; Aggregation.</li></ul><p>Not only the IaaS services mentioned above, but there will be a slice of PaaS services that will be demanded from the edge. The evolution path of the edge will follow the public cloud trajectory albeit at a limited scale.</p><h3>How is edge going to evolve?</h3><h3>Structural Elements of the edge</h3><p>In my opinion, the edge itself will be composed of the two structural elements defined below:</p><ul><li>CloudEdge: A distributed edge with close proximity to user endpoint satisfying it’s immediate IaaS needs.</li><li>CloudExchange: An exchange, facilitating brokerage of compute to CloudEdge.</li></ul><blockquote>A blockchain verified introduction into the edge for a new CloudExchange and its capabilities seems too quixotic right now, but would be interesting :)</blockquote><h3>Core Technologies required for intelligent edge</h3><ul><li>Mobile Technology with sufficient bandwidth and Network Slicing.</li><li>Compute/Storage proximity to End Points.</li><li>On-demand orchestration, metering and flexible resource extraction layer from available compute, storage &amp; networking on the edge.</li><li>Edge having right uniform abstraction to advertise it’s capabilities so that it can be dynamically tapped into.</li><li>Ephemeral Multi-Tenancy throughout the stack.</li></ul><h3>Key Characteristics of a smart edge</h3><p>Depending on the type of application following characterizations will be expected from the edge infrastructure:</p><ul><li>Highly secure: Imperative, non-negotiable.</li><li>Low Latency: Table stakes and a primary reason for edge to exist.</li><li>Reliability:<strong> </strong>Extremely important especially for mission-critical applications.</li><li>Highly Available: Challenges galore especially for critical use cases.</li><li>Data Handling: Store, Cache, Process, and Stream.</li></ul><h3>Unleashing the Developers</h3><p>In this day and age, no infrastructure is good enough if you are not able to unleash developers onto it. The future of distributed applications will include the edge as an integral part of the equation. The following figure shows how future applications might be laid out on a combination of edge+cloud infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*casFVcmDliCQtJIa" /></figure><p>For march of the cloud to go on unabated, it’s imperative that the foundation on edge is strengthened. <strong>All in all,</strong> <strong>the moment is ripe for the journey to begin.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c56b14f96d86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Escaping the Bell Curve]]></title>
            <link>https://medium.com/@vibhu.pratap/escaping-the-bell-curve-8a30641ecaf6?source=rss-74ad10731069------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a30641ecaf6</guid>
            <category><![CDATA[performance-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <dc:creator><![CDATA[Vibhu Pratap]]></dc:creator>
            <pubDate>Thu, 08 Feb 2018 04:02:24 GMT</pubDate>
            <atom:updated>2018-02-08T04:02:24.751Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VH5dDozoTZG7RiHnd-fdWA.png" /></figure><p>Waiting for the boarding call for my flight to Frankfurt couple of weeks back, the person sitting across from me was on the phone (presumably with their co-worker). “<strong>They don’t like me</strong>” he says, in a fired up tone. “<strong>I am sure he’s trying to get rid of me</strong>”, I overhear. It was in plain earshot and I could not help wonder- why was I not shocked to hear that? After all, it spoke volumes about how the person felt at their workplace.</p><p>According to latest <a href="http://news.gallup.com/reports/199961/7.aspx">Gallup</a> survey, of the 100 million full-time employees in America, <strong>51 percent aren’t engaged at work</strong> — meaning they feel no real connection to their jobs, and thus they tend to do the bare minimum. <a href="https://www.cbsnews.com/news/why-so-many-americans-hate-their-jobs/"><strong>Another 16 percent</strong> </a>are “actively disengaged” — they resent their jobs, tend to gripe to co-workers and drag down office morale as a result.</p><p>Even on a day to day basis, the hackneyed existence of a professional in a corporate setting is something easy to spot. You can sense some of the listlessness when you encounter such trapped individuals, the presence of an emphatic ear in their vicinity can open them up to a litany of complaints. When you talk to them (like I’ve experienced several times), you get the feeling that they are the chosen ones against whom the world is conspiring.While that is true in some cases, the majority of times that’s not the reality.</p><p>It was not meant to be this way, not at all, the shape that their career took was different than how it was imagined, they dreamt about changing the world with energies, passion, and commitment. In all earnestly they tried over the years to make the necessary efforts but all they succeeded in, is becoming a dot in their organization’s defined Bell Curve.That dot on the Bell Curve which is jostling with the adjacent dots, trying to displace them before the next round of appraisals, without realizing the fruitlessness of the whole exercise.</p><h3>Developing Bell Curve Escape Velocity</h3><p>Below are some of the salient practices that I have stuck with while trying to escape this bell curve.Each one of these different dimensions of activity provides with some velocity to break out and do work which is gratifying on a day to day basis.</p><ul><li><strong>Don’t over-estimate your significance</strong>: The world is not out to get you, <strong>you are nothing but an insignificant blip in someone else’s life. </strong>As suggested in <a href="https://www.fs.blog/2017/04/mental-model-hanlons-razor/">Hanlon’s Razor</a> model :</li></ul><blockquote>Never attribute to malice that which can be adequetaly explained by neglect.</blockquote><p>Use it to become more rational and less judgemental.</p><ul><li><strong>Fear of the unknown can be paralyzing:</strong> The weak moments of uncertainty about the future plague us, makes us stick to the status-quo, stops us from venturing out from our comfortable confines and prevents us from observing, learning &amp; taking a long-term view of the future, a future which is not constrained by the bell curve. In my opinion: “<strong>The uncertainty is here to stay, you have no other option but to befriend it. Be a seeker and always extract the best from the day, week, month ahead</strong>”.</li></ul><blockquote>Inadverentaly, the best learning during a day for me,has always involved access to clean whiteboard and folks brainstorming on a new problem or rethinking a problem whose previous solution has either been abandoned or has to be refined (Ideally a single problem or limited to a handful)</blockquote><ul><li><strong>Collaborate fearlessly:</strong> Develop collaboration as a fundamental tenant to give an impetus for your escape.<strong>Collaborate with the right dots and strive for collective velocity.</strong></li></ul><blockquote>Have not been able to figure out the best collaborative way, keep experimenting and figure out the right tools for your organization.The right model will definitely be a refinement on the current adopted one.</blockquote><ul><li><strong>Find the team, find the need: </strong>Identify the seekers working in your organization and forge strong relationships with them.</li></ul><pre>According to me, there are three types of professionals you <br>will encounter in a workplace:</pre><pre>- The first ones, can see through and feel the future.These are far <br>and few within an organization.</pre><pre>- The second ones who can sense that the direction is right and continue <br>to be iterative about getting collective clarifications after their <br>initial milestones have come to a fruition.</pre><pre>- The third ones are in a perpetual direction seeking mode the <br>above two will have to get him/her in the right direction and finally <br>to the right destination in all earnestness.</pre><blockquote>You will know when you meet a seeker who is trying to move upwards on the above scale.They are the catalysts who will provide you with the right perspective.</blockquote><ul><li><strong>Agility and impact are your friends:</strong> Last but not the least, in the spirit of agile, be your own <a href="http://whatis.techtarget.com/definition/scrum-master">scrum master</a> and do a daily standup (you can do this in any position) with your thoughts at the beginning and end of the day.This meeting can include an amalgamation of personal and professional progress.</li></ul><blockquote>No suggestions for the questions you can ask during this time.Feel free to adjust your compass and see if you are doing enough to escape the Bell Curve, and working towards a long term sustainable future for yourself.</blockquote><p><strong>PS: Feel free to share your experience(s) if you are employing different strategies to escape the bell curve.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a30641ecaf6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developer Experience : What art thou?]]></title>
            <link>https://medium.com/@vibhu.pratap/developer-experience-what-art-thou-b51297eda7d3?source=rss-74ad10731069------2</link>
            <guid isPermaLink="false">https://medium.com/p/b51297eda7d3</guid>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Vibhu Pratap]]></dc:creator>
            <pubDate>Sun, 30 Jul 2017 02:54:33 GMT</pubDate>
            <atom:updated>2017-07-30T02:54:33.620Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7afU_IRcF7zMfzu7-3Mbg.png" /></figure><p>You have seen this play out a million times before slow pace of software development cycle, endless meetings to define the perfect set of use-cases, and then the first MVP comes. All this time, your sales team keeps customers enamored with marketecture, slideware, and some slicing and dicing of road maps to present something they <em>think</em> the customer wants to see.</p><p>The decision makers that commiserate with you, patiently waiting for your solution to develop and be deployment ready are on verge of extinction. They are being replaced by the ones who are on the hook to keep their businesses running under strained budgets, all the while restless to solve their immediate problems and eager to participate in providing the requirements for the product they will own &amp; deploy.</p><blockquote>This is the active and engaged decision maker, influencer and customer that shares their success outcomes with you and expects you to enable theirs- in real time.</blockquote><p>The amplifying effect it has on companies making these product offerings is to move at a faster pace more than ever to make it happen, it’s not a far fetched world when your replacement is just a Google search away.</p><blockquote><em>The days of coercive monopolies are well and truly behind us in today’s world of aware customer with monotonically increasing sequence of expectations.</em></blockquote><p>I started thinking about this deeply when I was chartered to roll out the internal Developer experience (DevX) in our organization. So what is the most critical resource in development organizations today? Talent you might say, leadership others might say. Product direction, Strategy, Customer insights…Yes, all of the above have a role, but the most critical resource in today’s teams developing software products is the <strong>developer’s time</strong>, it needs to be guarded with the same zeal as you guard your product.</p><p>With that thinking, my goal of DevX is all about enabling the developer — providing tools, methods, and procedures to ease the life of your developers followed by requirements to the developers to have products which are API ready. DevX tools need to go the extra mile to work and remove obstacles so that you get untapped productivity gains that were not possible before.</p><blockquote><em>Similar to how agile software development have to adapted to the needs of organization,so will be the case with Developer Experience.</em></blockquote><p>These tools need to optimize available infrastructure and provide it for frictionless consumption on demand.With the advent of ‘<a href="https://www.linkedin.com/pulse/software-clusters-future-vibhu-pratap">Software Clusters for the future</a>’, the building of the developer experiences will lead the pace of innovation that your developers can unleash on to your customers.</p><p>Over the years, IDE’s have played an important role in enhancing developers productivity.The DevX tooling needs to be made part of the same IDE to make sure the gains to be extracted are available to the developers within their preferred environments.</p><blockquote>A Customer Centric strategy has to be followed closely by a Developer Centric culture for every product team that wants to be on the path of customer penetration.</blockquote><p>In closing, while you can do a lot to improve your product teams processes, improving your customer insights, hire and retain the best talent- the single most important investment you will make will be in your developers time. Enable them to be ultra productive and prioritize their time like you prioritize your executive’s time and the products will come out exceeding all benchmarks- and the customer experience will be excellent.</p><p>Being new to this I am eager to learn more from you and your experiences in this area. Am open to buying you a coffee (in bay area) for a healthy conversation around this topic.Feel free to ping me at vibhu.pratap (at) gmail.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b51297eda7d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>