<?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 Ola Sonola on Medium]]></title>
        <description><![CDATA[Stories by Ola Sonola on Medium]]></description>
        <link>https://medium.com/@olasonola?source=rss-d84e55121bb5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hoMQ73fxQXdFKp72tyagRA.jpeg</url>
            <title>Stories by Ola Sonola on Medium</title>
            <link>https://medium.com/@olasonola?source=rss-d84e55121bb5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 21:10:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olasonola/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[Will AI Replace Infrastructure Engineers — Or Just Change the Job?]]></title>
            <link>https://olasonola.medium.com/will-ai-replace-infrastructure-engineers-or-just-change-the-job-115c1db10f41?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/115c1db10f41</guid>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Tue, 02 Jun 2026 07:34:36 GMT</pubDate>
            <atom:updated>2026-06-02T07:34:36.682Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wO6TSuUJHmwATi43FREnJA.jpeg" /></figure><p><em>“The biggest risk facing infrastructure engineers isn’t AI replacing them. It’s assuming their job won’t change.”</em></p><p>Every week brings another headline about AI writing code, automating operations, or managing cloud environments. For infrastructure engineers, it’s natural to wonder:</p><p><strong>Am I building the future — or training my replacement?</strong></p><p>It’s a fair question. But history suggests the answer is more nuanced than a simple yes or no.</p><p>Infrastructure engineering has always evolved through automation.</p><p>Twenty years ago, provisioning servers was largely manual. Then came virtualization. Many feared it would reduce the need for infrastructure teams. Instead, engineers adapted and learned to manage environments at a scale that was previously impossible.</p><p>The same happened with cloud computing.</p><p>Then Infrastructure as Code.</p><p>Each innovation automated tasks, but it didn’t eliminate the profession. It changed the profession.</p><p>AI is likely to follow the same pattern.</p><p>Let’s be honest: some infrastructure tasks are highly repetitive. Writing routine scripts, generating documentation, analysing logs, creating change records, and building standard configurations are all activities that AI can increasingly perform faster than humans.</p><p>And that’s not necessarily a bad thing.</p><p>Businesses don’t hire infrastructure engineers to spend hours searching logs or formatting reports. They hire them to deliver secure, reliable, and resilient systems. If AI removes repetitive work, engineers can focus on problems that matter more.</p><p>Because the hardest infrastructure challenges aren’t usually technical.</p><p>They’re organisational.</p><p>They’re contextual.</p><p>They’re human.</p><p>An AI can recommend the technically correct solution. An experienced engineer understands why that solution may fail because of budget constraints, legacy systems, regulatory requirements, business priorities, or operational risk.</p><p>Infrastructure doesn’t exist in isolation. It exists within a business.</p><p>Understanding that context is where engineers continue to add value.</p><p>The engineers who thrive over the next decade won’t necessarily be the ones who know the most commands or scripting languages. They’ll be the ones who know how to combine AI with expertise.</p><p>Skills such as systems thinking, architecture, risk management, communication, and decision-making will become even more important. As AI handles more routine execution, engineers will spend more time designing solutions, evaluating trade-offs, and guiding strategic decisions.</p><p>In many ways, the role may become more valuable, not less.</p><p>The real threat isn’t AI.</p><p>The real threat is standing still.</p><p>We’ve seen this before. Engineers who ignored virtualization fell behind. The same happened with cloud computing and Infrastructure as Code. The technology itself wasn’t the problem. Refusing to adapt was.</p><p>AI presents the same choice.</p><p>Treat it as a competitor, or treat it as a force multiplier.</p><p>Those who embrace it will automate more, troubleshoot faster, learn quicker, and ultimately deliver greater value to their organisations.</p><p>So, will AI replace infrastructure engineers?</p><p>For some tasks, absolutely.</p><p>For the profession as a whole, probably not.</p><p>More likely, AI will do what every major technology shift has done before: automate routine work while increasing the value of people who can solve complex problems.</p><p>The infrastructure engineer of 2035 may look very different from today’s engineer.</p><p>But organisations will still need people who understand systems, manage risk, and make sound decisions when technology meets reality.</p><p>And that’s a job worth preparing for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=115c1db10f41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Meets vSphere: Understanding Tanzu in the Context of Cloud Foundation]]></title>
            <link>https://olasonola.medium.com/kubernetes-meets-vsphere-understanding-tanzu-in-the-context-of-cloud-foundation-2971f6bf783e?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2971f6bf783e</guid>
            <category><![CDATA[cloud-foundation]]></category>
            <category><![CDATA[tanzu]]></category>
            <category><![CDATA[hybrid-cloud]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Wed, 15 Apr 2026 11:01:01 GMT</pubDate>
            <atom:updated>2026-04-15T11:01:01.614Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vMCoIni0IcOYBvvpirpQTA.jpeg" /></figure><p>Over the past decade, enterprise infrastructure has undergone a fundamental shift. Traditional virtual machines (VMs), once the backbone of application deployment, are increasingly being complemented — or in some cases replaced — by containerised workloads orchestrated by Kubernetes. This transition, however, has not been a clean break. Most organisations still operate large, business-critical VM estates. The challenge has been clear: how do you modernise without abandoning what already works?</p><p>This is where VMware Tanzu, particularly within the VMware Cloud Foundation (VCF) ecosystem, plays a pivotal role.</p><p><strong>The Evolution of Tanzu</strong></p><p>Tanzu didn’t emerge as a single product but as a portfolio shaped by VMware’s response to the Kubernetes revolution. Initially, organisations adopting Kubernetes often built parallel environments — one for VMs (vSphere) and another for containers (often public cloud or bespoke platforms). This created operational silos, duplicated tooling, and fragmented skill sets.</p><p>VMware’s strategy evolved to bring Kubernetes directly into the vSphere environment. The turning point came with the introduction of <strong>vSphere with Tanzu</strong>, which embedded Kubernetes natively into the hypervisor layer. Instead of treating containers as external workloads, they became first-class citizens alongside VMs.</p><p>This shift reframed vSphere from being purely a virtualisation platform into a unified application platform.</p><p><strong>Bridging VMs and Containers</strong></p><p>At its core, Tanzu bridges two worlds:</p><ul><li><strong>Traditional VMs</strong>: Stable, predictable, and widely understood by infrastructure teams.</li><li><strong>Kubernetes Containers</strong>: Agile, scalable, and favoured by modern development practices.</li></ul><p>Tanzu enables both to coexist on the same infrastructure, managed through a single control plane. This is achieved through several key capabilities:</p><ul><li><strong>Supervisor Cluster</strong>: A Kubernetes control plane running directly on ESXi hosts, exposing Kubernetes APIs alongside traditional vSphere management.</li><li><strong>Tanzu Kubernetes Grid (TKG)</strong>: Provides upstream-compatible Kubernetes clusters that can be deployed and managed consistently across environments.</li><li><strong>Namespaces and Resource Policies</strong>: Allow platform teams to allocate resources to developers in a controlled, self-service manner.</li></ul><p>The result is a platform where developers can request Kubernetes clusters or deploy containerised applications, while infrastructure teams retain governance, security, and visibility.</p><p><strong>Tanzu in the Context of Cloud Foundation</strong></p><p>When Tanzu is integrated into VMware Cloud Foundation, its value becomes even more compelling. VCF provides a full-stack, software-defined data centre (SDDC) that includes compute (vSphere), storage (vSAN), networking (NSX), and lifecycle management.</p><p>Adding Tanzu into this stack delivers:</p><ul><li><strong>Consistent Operations Across Private and Public Cloud</strong><br> Tanzu-enabled workloads can run on-premises or in VMware-based public clouds with minimal changes, supporting hybrid and multi-cloud strategies.</li><li><strong>Integrated Lifecycle Management</strong><br> VCF automates the deployment and patching of both infrastructure and Kubernetes components, reducing operational overhead.</li><li><strong>Enhanced Security and Networking</strong><br> NSX enables micro-segmentation and advanced networking for both VMs and containers, ensuring consistent security policies.</li><li><strong>Developer Self-Service Without Losing Control</strong><br> Platform teams can define guardrails while enabling developers to provision and manage Kubernetes environments independently.</li></ul><p><strong>Why This Matters</strong></p><p>The significance of Tanzu within Cloud Foundation lies in its ability to modernise without disruption. Rather than forcing a migration from VMs to containers, it enables a gradual, pragmatic evolution.</p><p>For many enterprises, this means:</p><ul><li>Running legacy applications on VMs while building new services in containers</li><li>Using a common platform for both, reducing complexity</li><li>Aligning infrastructure and development teams around shared tools and processes</li></ul><p>This convergence is particularly valuable in regulated or risk-averse industries where wholesale platform changes are not feasible.</p><p><strong>Final Thoughts</strong></p><p>Tanzu represents a strategic bridge between past and future. By embedding Kubernetes into vSphere and extending it through Cloud Foundation, VMware has created a pathway for organisations to adopt cloud-native practices without abandoning their existing investments.</p><p>In practical terms, it’s not about choosing between VMs and containers — it’s about enabling both to thrive on a single, consistent platform.</p><p>And in a world where hybrid is the norm, that balance is exactly what many enterprises need.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2971f6bf783e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hidden Cost of Misalignment: Why Consistent vSphere Versions Matter Across Cloud and Edge]]></title>
            <link>https://olasonola.medium.com/the-hidden-cost-of-misalignment-why-consistent-vsphere-versions-matter-across-cloud-and-edge-cdde44d468a8?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdde44d468a8</guid>
            <category><![CDATA[sre]]></category>
            <category><![CDATA[edge-computing]]></category>
            <category><![CDATA[it-operations]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 09:31:01 GMT</pubDate>
            <atom:updated>2026-04-07T09:31:01.437Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*320GWYxhi0q9jEqvDePpNA.jpeg" /></figure><p>Hybrid cloud promises flexibility — running workloads where they make the most sense: on-prem, in the cloud, or at the edge. But that flexibility often comes with a hidden cost: misalignment.</p><p>It rarely happens all at once. A delayed upgrade here. A legacy edge deployment there. A cloud environment patched ahead of schedule. Individually, these decisions seem harmless. Together, they create a fragmented estate where consistency — key to operational efficiency — starts to slip.</p><p>This is configuration drift in action.</p><p><strong>The Rise of Version Sprawl</strong></p><p>In most organisations, different teams manage different environments. Core data centres, edge sites, and cloud platforms all operate on separate timelines. Change windows don’t align, and priorities differ. Over time, multiple platform versions emerge.</p><p>At first, it’s manageable. But cracks appear:</p><ul><li><strong>Inconsistent behaviour</strong>, complicating troubleshooting</li><li><strong>Feature gaps</strong> between environments</li><li><strong>More complex upgrades</strong> as version differences grow</li><li><strong>Support challenges</strong> when alignment is expected</li></ul><p>What was once a unified platform becomes a collection of “almost identical” systems.</p><p><strong>When It Matters Most</strong></p><p>The real impact shows up during incidents.</p><p>Picture a performance issue isolated to a single edge site. The setup looks consistent, but the underlying version differs slightly. Logs don’t match expectations, known fixes don’t apply, and resolution takes longer than it should.</p><p>Multiply that across dozens of sites, and mean time to resolution (MTTR) increases — not due to lack of skill, but lack of consistency.</p><p><strong>Security and Compliance Risks</strong></p><p>Version sprawl also creates less visible risks.</p><p>Patching becomes uneven. Some environments are up to date; others lag due to operational constraints. This leads to a fragmented security posture, where vulnerabilities persist longer than expected.</p><p>From a compliance standpoint, inconsistency raises red flags. It’s not just about having policies — it’s about proving they’re applied uniformly.</p><p><strong>Why Consistency Wins</strong></p><p>Consistency isn’t about limiting flexibility — it’s about enabling predictability.</p><p>When environments are aligned:</p><ul><li><strong>Operations standardise</strong></li><li><strong>Automation becomes dependable</strong></li><li><strong>Troubleshooting speeds up</strong></li><li><strong>Security is easier to manage</strong></li></ul><p>The platform behaves as one system, not many variations of the same.</p><p><strong>Managing Lifecycle with Purpose</strong></p><p>This is where structured lifecycle management matters. Upgrades shouldn’t be isolated events — they need coordination across the estate.</p><p>Tools like SDDC Manager provide a centralised approach, orchestrating upgrades in a validated sequence. Instead of manually tracking dependencies, teams follow a consistent, repeatable process.</p><p>It shifts lifecycle management from reactive to intentional.</p><p><strong>The Edge Challenge</strong></p><p>If misalignment starts in the core, it multiplies at the edge.</p><p>Edge environments often run with limited oversight and constrained resources. Without strong lifecycle control, they drift quickly. Each site becomes unique, making management harder.</p><p>Keeping edge aligned requires standardised deployments, controlled versioning, and central governance — not just ad hoc updates.</p><p><strong>Bringing It Back Together</strong></p><p>The cost of misalignment builds over time:</p><ul><li>Longer troubleshooting cycles</li><li>Increased security exposure</li><li>Slower adoption of new features</li><li>Higher operational overhead</li></ul><p>These issues rarely appear overnight — but they compound quickly.</p><p>The answer isn’t simply upgrading more often. It’s treating version alignment as a priority from the start.</p><p>In a world spanning cloud, core, and edge, consistency isn’t optional — it’s what keeps everything working together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdde44d468a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Broadcom Pulls the Plug on DIY vSphere: Your VCF Survival Guide]]></title>
            <link>https://olasonola.medium.com/when-broadcom-pulls-the-plug-on-diy-vsphere-your-vcf-survival-guide-3a41f1950e0c?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a41f1950e0c</guid>
            <category><![CDATA[vmware-cloud-foundation]]></category>
            <category><![CDATA[it-infrastructure]]></category>
            <category><![CDATA[vmware-vsphere]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[private-cloud]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Thu, 26 Mar 2026 10:01:01 GMT</pubDate>
            <atom:updated>2026-03-26T10:01:01.378Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How to navigate the forced migration to VMware Cloud Foundation without losing control of your infrastructure</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GeYZ5GKWXNFr6-Rz2zInlg.jpeg" /></figure><p>For years, many organisations ran “DIY” vSphere environments — carefully architected clusters, custom storage configurations, and bespoke networking setups. These DIY stacks gave IT teams flexibility, control, and the freedom to innovate without being locked into a full-stack solution. Teams could tailor infrastructure to business needs, optimise costs, and implement unique integrations.</p><p>But things are changing. Broadcom is now bundling vSphere modules into<strong> </strong>VMware Cloud Foundation (VCF) and signalling the withdrawal of standalone DIY support. In other words, organisations face a stark choice: adopt VCF or run unsupported DIY stacks. This isn’t just a technical shift — it’s a strategic headache for IT teams, especially those who have invested years in DIY systems.</p><p>VCF is a powerful platform. It delivers integrated compute, storage, and networking, automated lifecycle management via SDDC Manager, and multi-tenant operational consistency. For organisations with large estates and complex workloads, it promises a more predictable, managed environment.</p><p>But for teams used to DIY vSphere, the change feels restrictive. Suddenly, you have opinionated architecture constraints, enforced hardware and storage standardisation, and reduced flexibility for custom networking designs. Essentially, what was optional is now mandatory, leaving IT teams to balance operational pain against strategic compliance.</p><p>The risks of a forced migration are real. Operational overhead is the first challenge — lifecycle automation is great, but only if your team is trained in SDDC Manager, NSX, and vSAN. Without proper skills, updates, patching, and troubleshooting can become time-consuming and stressful. <strong>Cost </strong>escalation is another factor: bundled modules often come with higher licensing, stricter hardware requirements, and potential over-provisioning. Flexibility is also impacted — legacy applications, custom network topologies, or niche storage setups may not fit neatly into VCF, forcing redesigns. And finally, change fatigue can set in as teams try to roll out a full-stack migration while keeping services stable.</p><p>Despite the challenges, there are strategies to make the transition smoother. Start with a workload audit — not every VM or application needs immediate migration. Identify critical workloads and plan for lower-priority systems to move later. Invest in training early: upskill teams on NSX, vSAN, and SDDC Manager before migration begins. Engaging certified partners or consultants can save significant time and reduce the risk of costly mistakes. If some legacy DIY systems are stable, consider a hybrid approach, running them alongside VCF temporarily. And finally, document every process: migration projects can get messy, and accurate records keep teams aligned and reduce downtime.</p><p>Another important consideration is governance. With VCF, IT teams should define clear policies for upgrades, patching, and change management. The platform enforces structure, but without internal governance, teams may struggle to align operations with business requirements. Similarly, monitoring and reporting become even more critical: VCF provides tools, but proactive oversight ensures performance and cost efficiency.</p><p>Being forced into a platform isn’t ideal, but VCF isn’t inherently bad — it simply changes the rules of the game. The key is to approach the migration strategically rather than reactively. Understand what VCF does well, where it introduces constraints, and plan around both. Often, the smartest move isn’t resisting the mandate — it’s making the platform work for your team, not against it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a41f1950e0c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Soft Skills That Will Still Matter When AI Takes Your Job]]></title>
            <link>https://olasonola.medium.com/the-soft-skills-that-will-still-matter-when-ai-takes-your-job-3e81f5eb0f3d?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e81f5eb0f3d</guid>
            <category><![CDATA[workplace-trends]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[soft-skills]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Mon, 16 Mar 2026 13:32:56 GMT</pubDate>
            <atom:updated>2026-03-16T13:32:56.080Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nPLV-SYBmc5DQDumHDtjWw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@omilaev?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Igor Omilaev</a> on <a href="https://unsplash.com/photos/two-hands-touching-each-other-in-front-of-a-blue-background-FHgWFzDDAOs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>If you spend any time on LinkedIn or in tech circles lately, you’ll notice a common theme: AI is coming for our jobs. Automation, generative AI, machine learning — every new tool promises to do faster, cheaper, and sometimes even better what humans used to do.</p><p>It’s an unsettling narrative.</p><p>Developers see AI writing code. Analysts see AI generating reports. Designers see AI creating images in seconds. Even roles that once felt safe from automation are starting to feel the pressure.</p><p>And naturally, people start asking the same question: <em>what’s left for us?</em></p><p>But that question assumes something important — that work is just a collection of tasks.</p><p>In reality, most jobs are far more than that.</p><p>Yes, AI will replace certain tasks. In many cases, it already is. But the parts of work that rely on human judgement, empathy, creativity, and collaboration are much harder to automate.</p><p>In fact, the rise of AI may actually make those skills more valuable.</p><p>One of the most important is judgement.</p><p>AI can generate answers incredibly quickly. It can summarise documents, analyse data, and suggest recommendations. But it doesn’t truly understand context the way humans do.</p><p>It doesn’t grasp organisational politics. It doesn’t understand long-term consequences. And it doesn’t always recognise when the data it’s working from is flawed.</p><p>That means someone still needs to ask the important question: <em>Is this actually the right decision?</em></p><p>That’s judgement — and it’s something machines still struggle with.</p><p>Communication is another skill that will become even more valuable.</p><p>AI can generate emails and presentations, but communication is about much more than producing text. It’s about understanding the audience, reading the room, and knowing how to influence or reassure people.</p><p>A great communicator can take a complex technical issue and explain it clearly to executives, customers, or non-technical colleagues. That ability to translate between worlds is incredibly powerful.</p><p>And incredibly human.</p><p>Adaptability will also separate people who thrive from those who struggle.</p><p>Technology is evolving rapidly, and AI is accelerating that change. Tools will improve, workflows will shift, and new roles will appear while others fade away.</p><p>The people who succeed won’t necessarily be the ones who know a single tool inside out.</p><p>They’ll be the ones who can learn quickly, adjust their thinking, and stay comfortable working in environments that keep changing.</p><p>Curiosity is another underrated skill in the age of AI.</p><p>AI is excellent at recognising patterns based on existing data. But curiosity is what pushes people to explore beyond those patterns.</p><p>Curious people ask questions that others don’t.</p><p>Why does this process exist?<br> Is there a better way to do this?<br> What happens if we approach the problem differently?</p><p>Those questions often lead to innovation.</p><p>And finally, emotional intelligence will continue to matter.</p><p>Workplaces are built on relationships. Teams collaborate, leaders motivate people, and customers choose companies they trust.</p><p>AI can simulate conversation, but it cannot genuinely understand human emotion or build meaningful relationships. It can’t sense tension in a meeting or encourage a struggling colleague.</p><p>Those are deeply human abilities.</p><p>The real shift AI is bringing isn’t just automation. It’s a change in what makes someone valuable at work.</p><p>For years we focused heavily on technical expertise. And while those skills still matter, they’re increasingly being augmented by AI.</p><p>What’s harder to replicate are the human capabilities that sit around the work — judgement, communication, curiosity, adaptability, and empathy.</p><p>Ironically, the more advanced our technology becomes, the more valuable those human traits become.</p><p>AI might take parts of your job.</p><p>But the skills that make you human are likely to matter more than ever.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e81f5eb0f3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Real Reason Your Side Hustle Isn’t Making Money]]></title>
            <link>https://olasonola.medium.com/the-real-reason-your-side-hustle-isnt-making-money-fbf7f15600a4?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbf7f15600a4</guid>
            <category><![CDATA[business-growth]]></category>
            <category><![CDATA[startupş]]></category>
            <category><![CDATA[making-money-online]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[side-hustle]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Wed, 11 Mar 2026 12:03:19 GMT</pubDate>
            <atom:updated>2026-03-11T12:03:19.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_Nwx_GqkFM9b-n77c-UZg.jpeg" /></figure><p>You started your side hustle with excitement.</p><p>Maybe it was supposed to create extra income. Maybe it was your path to financial freedom. Or maybe it was the first step toward leaving your 9-to-5.</p><p>But months later, the results are underwhelming. Sales are inconsistent. Engagement is low. And the question starts creeping in:</p><p><strong>“Why isn’t this working?”</strong></p><p>Most people assume the problem is effort. They think they need to post more on social media, build a better website, or buy another course.</p><p>But in reality, most side hustles fail to make money for a much simpler reason.</p><p><strong>They don’t solve a clear, valuable problem.</strong></p><p>Many side hustles start with passion instead of demand. Someone enjoys baking, designing logos, photography, writing, or building websites, so they turn that skill into a business.</p><p>Passion is helpful. But passion alone doesn’t create customers.</p><p>A profitable side hustle sits at the intersection of three things:</p><ul><li><strong>A real problem</strong></li><li><strong>A specific audience</strong></li><li><strong>A solution people are willing to pay for</strong></li></ul><p>When one of these pieces is missing, the hustle struggles.</p><p>Take a simple example. Someone starts selling handmade candles online. The product looks great, the branding is nice, and the effort is there.</p><p>But candles are already everywhere.</p><p>Without a clear difference — such as eco-friendly materials, allergy-safe ingredients, or targeting a specific community — it becomes just another option in a crowded market.</p><p>Another common problem is <strong>trying to appeal to everyone</strong>.</p><p>When your message is too broad, it becomes forgettable. People respond to businesses that clearly understand their needs.</p><p>Compare these two statements:</p><p>“I help businesses with IT.”</p><p>“I help small accounting firms prevent downtime and protect client data.”</p><p>The second message is more powerful because it is specific. It immediately signals expertise and value.</p><p>Focus matters.</p><p>Consistency matters too. Many side hustlers constantly switch strategies. One week they focus on social media. The next week they try paid ads. Then they build a new website or pivot to a different idea entirely.</p><p>Each new strategy resets the clock.</p><p>Most channels need consistent effort over time before they produce results. Momentum doesn’t happen overnight.</p><p>Pricing is another hidden issue. Many people underprice their services because they worry no one will buy.</p><p>Ironically, low pricing can actually reduce trust. Customers often associate price with quality. If something looks too cheap, people assume it might not deliver real value.</p><p>Finally, many side hustles focus on <strong>features instead of outcomes</strong>.</p><p>Customers rarely buy features.</p><p>They buy results.</p><p>A website designer isn’t really selling a website. They’re selling credibility, more enquiries, and a better online presence. A fitness coach isn’t selling workouts. They’re selling confidence, health, and transformation.</p><p>When your offer clearly communicates the outcome it creates, people understand why it matters.</p><p>The truth is that most side hustles don’t fail because people lack talent or work ethic. They fail because the offer isn’t clearly connected to a real problem yet.</p><p>The good news is that this can be fixed.</p><p>Ask yourself three simple questions:</p><ol><li>What problem am I solving?</li><li>Who exactly has this problem?</li><li>Why is my solution valuable enough for someone to pay for?</li></ol><p>When those answers become clear, your side hustle stops feeling like guesswork.</p><p>It starts becoming a real business.</p><p>And that’s usually the moment when the money finally begins to follow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbf7f15600a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Being “Busy” Is the Most Dangerous Productivity Trap]]></title>
            <link>https://olasonola.medium.com/why-being-busy-is-the-most-dangerous-productivity-trap-f673747c46c5?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f673747c46c5</guid>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[career-growth]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Tue, 03 Mar 2026 18:36:00 GMT</pubDate>
            <atom:updated>2026-03-03T18:36:00.700Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UHL-fApQ6at-x2DU6_Iivw.jpeg" /></figure><p>“How are things?”</p><p>“Busy.”</p><p>That’s become the default answer, hasn’t it? Almost a badge of honour. If we’re busy, we must be important. In demand. Valuable.</p><p>But here’s the uncomfortable truth:</p><p>Being busy and being productive are not the same thing.</p><p>And the more we confuse the two, the more we trap ourselves.</p><p>The Cult of Busyness</p><p>Modern work rewards visible activity.</p><p>Full calendars.<br> Quick replies on Slack or Teams.<br> Back-to-back meetings.<br> Emails sent late at night.</p><p>It looks impressive. It feels productive.</p><p>But a lot of it is just motion — not progress.</p><p>Busyness gives us a small dopamine hit. We clear the inbox. We tick off tasks. We respond fast. It feels like momentum.</p><p>But pause for a second.</p><p>If everything you did this week stopped, what real value would be missing?</p><p>That question can be uncomfortable. Because it forces us to separate activity from impact.</p><p>Busy Work vs. Real Work</p><p>Let’s be honest.</p><p>Replying instantly to emails feels efficient. But does it solve the underlying problem?</p><p>Attending every meeting feels responsible. But are you actually driving decisions?</p><p>Perfecting slides feels like progress. But are you influencing outcomes?</p><p>A lot of modern knowledge work has quietly shifted toward coordination instead of creation. We manage updates, workflows, and communication loops. We stay “on top of things.”</p><p>But we don’t always move things forward.</p><p>And in an AI-powered world, that’s risky.</p><p>The tasks that make us look busy — updates, summaries, scheduling, formatting — are exactly the kinds of things software can handle. If your value is based on being responsive and available, you’re competing with automation.</p><p>The Hidden Cost</p><p>The danger of busyness isn’t obvious at first.</p><p>Over time, though, you notice it:</p><p>You stop thinking strategically.<br> Deep work becomes rare.<br> You’re always reacting.<br> Creativity fades.<br> Energy drains faster than it should.</p><p>You end most days tired… but unsure what actually changed.</p><p>That’s the trap. You’re working hard. You’re just not working on the right things.</p><p>And the people who move ahead? They’re not always the busiest in the room. They’re the ones creating movement.</p><p>A Better Question</p><p>Instead of asking, “How much did I get done today?” try asking:</p><p>“What changed because of me today?”</p><p>That question shifts everything.</p><p>It pushes you toward outcomes, not optics. Decisions, not discussions. Leverage, not labour.</p><p>The highest-impact people protect thinking time. They say no more often. They focus on the few things that actually move the needle.</p><p>Interestingly, they often look less busy.</p><p>How to Escape the Trap</p><p>If this feels familiar, try a small reset:</p><p>Audit your week. Which tasks create value and which just maintain it?</p><p>Block two focused deep-work sessions. Even 90 minutes can outperform hours of scattered effort.</p><p>Cancel one recurring meeting. If it can be an update, make it one.</p><p>Delay non-urgent responses. Not every ping deserves priority.</p><p>And most importantly, define your three value drivers. If you disappeared tomorrow, what would actually break? Focus there.</p><p>Final Thought</p><p>Busyness feels safe. Impact feels uncomfortable.</p><p>One keeps you occupied. The other moves you forward.</p><p>So before you open your next tab or check your inbox again, pause.</p><p>Are you truly moving forward — or just moving around?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f673747c46c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How AI Is Quietly Replacing White-Collar Jobs — Including Yours]]></title>
            <link>https://olasonola.medium.com/how-ai-is-quietly-replacing-white-collar-jobs-including-yours-1620d5259a5c?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1620d5259a5c</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 12:05:45 GMT</pubDate>
            <atom:updated>2026-03-02T12:05:45.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aL4KSVY4QHuOJKOiCI_iuQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@hdbernd?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Bernd 📷 Dittrich</a> on <a href="https://unsplash.com/photos/an-office-with-a-lot-of-desks-and-chairs-pYlBAu3de0w?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>When people first warned that AI would take jobs, we pictured factory robots.</p><p>Assembly lines. Warehouses. Manual labour.</p><p>We didn’t picture marketers. Lawyers. Developers. Consultants. Analysts.</p><p>We didn’t picture ourselves.</p><p>And yet, here we are.</p><p>The shift isn’t loud. There aren’t dramatic headlines about entire office floors being replaced.</p><p>It’s happening quietly.</p><p>And that’s what makes it powerful.</p><p><strong>It Doesn’t Need to Replace You</strong></p><p>AI doesn’t need to take your whole job.</p><p>It just needs to take 30% of it.</p><p>Think about your average day. How much of it involves:</p><ul><li>Writing emails</li><li>Drafting reports</li><li>Building slide decks</li><li>Summarising meetings</li><li>Analysing spreadsheets</li><li>Researching information</li><li>Creating content</li></ul><p>That’s structured, repeatable thinking.</p><p>And AI is getting very good at structured, repeatable thinking.</p><p>So the change doesn’t look like, “You’re fired.”</p><p>It looks like, “We don’t need three people for this anymore.”</p><p>One person using AI well can suddenly produce what used to require a small team.</p><p>That’s the quiet replacement.</p><p><strong>It Starts as “Productivity”</strong></p><p>Every wave of automation begins as efficiency.</p><p>Spreadsheets didn’t eliminate finance teams overnight — they made them faster.</p><p>Email didn’t remove admin roles instantly — it streamlined communication.</p><p>AI feels similar at first. A clever assistant. A productivity boost.</p><p>But there’s a difference.</p><p>It doesn’t just make you faster.</p><p>It reduces how many people are required.</p><p>If one marketer can now generate ideas, copy, analysis, and reports in a fraction of the time, what happens next hiring cycle?</p><p>Hiring slows.</p><p>People who leave aren’t replaced.</p><p>Teams shrink without announcement.</p><p>No drama. Just “restructuring.”</p><p><strong>The Middle Is Most Exposed</strong></p><p>The squeeze isn’t usually at the very top or bottom.</p><p>It’s in the middle.</p><p>Mid-level analysts. Writers. Developers. Operations managers.</p><p>Because mid-level work often involves drafting, synthesising, reviewing, structuring, optimising.</p><p>Exactly the kind of work AI can support — or partially automate.</p><p>It doesn’t need to be perfect.</p><p>If it’s 70% accurate and significantly faster — with one human overseeing it — that’s often good enough for a business.</p><p>And that changes team maths.</p><p><strong>Some Skills Are Losing Scarcity</strong></p><p>Basic copywriting.<br>Standard contract drafting.<br>Data summaries.<br>Slide decks.<br>Routine coding tasks.</p><p>These used to be differentiators.</p><p>Now they’re becoming starting points.</p><p>If your main value is producing structured information, you’re exposed.</p><p>If your value is deciding what to do with that information, you’re safer.</p><p>There’s a big difference between producing and owning.</p><p><strong>What Survives</strong></p><p>Judgment.<br>Relationships.<br>Ownership.</p><p>AI can generate options. Humans carry consequences.</p><p>AI can draft the email. It can’t build long-term trust.</p><p>AI can create outputs. It doesn’t own outcomes.</p><p>If you’re accountable for revenue, strategy, compliance, or delivery, your leverage increases.</p><p>If you’re formatting the deck, that layer is thinner than it used to be.</p><p><strong>The Real Question</strong></p><p>This isn’t about panic.</p><p>It’s about positioning.</p><p>What percentage of your job could AI already handle with supervision?</p><p>Are you mainly producing — or deciding?</p><p>If your whole team mastered AI tomorrow, would you still need the same headcount?</p><p>AI isn’t eliminating ambition.</p><p>It’s eliminating average output at scale.</p><p>And it won’t happen loudly.</p><p>It’ll happen quietly.</p><p>The real question is whether you adapt before the maths adapts around you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1620d5259a5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everyone Is Burned Out. Here’s Why — and What High Performers Are Doing Instead]]></title>
            <link>https://olasonola.medium.com/everyone-is-burned-out-heres-why-and-what-high-performers-are-doing-instead-b71b284867e9?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b71b284867e9</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[high-performance]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[career-growth]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Thu, 26 Feb 2026 11:14:26 GMT</pubDate>
            <atom:updated>2026-02-26T11:14:26.173Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/728/1*Zqiz-7LIymWxGjcR1XlQQg.jpeg" /></figure><p>You feel it too, don’t you?</p><p>That 11:47pm Slack ping you feel obligated to check.<br> The Sunday-night dread that sneaks in no matter what you’re doing.<br> The constant background hum of “I should be working, learning, or improving.”</p><p>This isn’t just being tired.<br> It’s burnout. And it’s everywhere.</p><p>Here’s the kicker: burnout isn’t just about working too hard.<br> It’s about working in a way that slowly breaks your operating system.</p><p>The people who seem to thrive? They haven’t escaped pressure. They’ve just figured out a smarter way to deal with it.</p><p>Let’s break it down.</p><p><strong>Why Everyone Feels Drained</strong></p><p><strong>We’re never really “off”</strong><br> Work used to end when you left the office. Now it follows you in your pocket.</p><p>Even when you’re “relaxing,” your brain is buzzing: emails, notifications, news, messages. That constant low-level stimulation prevents real recovery.</p><p>Burnout isn’t always about 12-hour days. It’s about 12-hour activation cycles.</p><p><strong>We confuse busyness with progress</strong><br> Replying quickly. Jumping into every meeting. Being “on top of things.”</p><p>It feels productive, but it rarely moves the needle. So we stretch ourselves longer to compensate. And guess what? That gap between effort and impact is exhausting.</p><p><strong>We built careers on urgency</strong><br> Maybe you became the reliable fixer, the one who says yes to everything. Over time, that becomes a trap. You’re the escalation point for everything — but without protected focus time, stress builds up.</p><p><strong>Rest feels like a reward, not a requirement</strong><br> “I’ll take a proper break once this project finishes.”<br> “I’ll switch off after quarter-end.”</p><p>Spoiler: things don’t calm down.</p><p><strong>What High Performers Are Doing Differently</strong></p><p><strong>They optimise for energy, not time</strong><br> Instead of managing calendars, they manage energy. Deep work happens when they’re sharp. Admin gets squeezed into low-energy periods. Focused blocks over a scattered day. Simple, but powerful.</p><p><strong>They treat recovery as strategy</strong><br> Athletes don’t apologise for rest days. High performers don’t either. Walks, hard stops in the evening, device-free moments — it’s all part of sustainable output.</p><p><strong>They cut noise aggressively</strong><br> Notifications off. Threads muted. Meetings declined without agendas. They’re not trying to know everything — just think clearly.</p><p><strong>They move from reactive to intentional</strong><br> Burnout loves reactivity. High performers define 1–3 meaningful outcomes for the week and measure success by progress, not busyness.</p><p><strong>They detach identity from output</strong><br> Most of us tie self-worth to productivity. High performers tie it to standards and values. “Did I work in alignment with what matters?” beats “How much did I produce?” every time.</p><p><strong>The Takeaway</strong></p><p>Burnout isn’t weakness.<br> It’s the predictable result of constant stimulation, shallow work, unbounded responsibility, and zero intentional recovery.</p><p>You don’t fix it by working harder.<br> You fix it by redesigning how you operate:<br> Clear priorities, protected focus, reduced noise, planned recovery, and a healthier relationship with output.</p><p>Everyone is tired.</p><p>But the people who last long-term know this:<br> The goal isn’t to squeeze more out of yourself.<br> It’s to build a system that doesn’t squeeze you in the first place.</p><p>Ask yourself: <em>what am I doing out of habit that’s quietly draining me?</em></p><p>Sustainable performance isn’t about intensity.<br> It’s about intelligent design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b71b284867e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architecting Multi-Tenant Environments in VMware Cloud Foundation (Without Making It Painful)]]></title>
            <link>https://olasonola.medium.com/architecting-multi-tenant-environments-in-vmware-cloud-foundation-without-making-it-painful-324e5cf60689?source=rss-d84e55121bb5------2</link>
            <guid isPermaLink="false">https://medium.com/p/324e5cf60689</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[vmware-cloud-foundation]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <category><![CDATA[multitenant-architecture]]></category>
            <category><![CDATA[managed-service-provider]]></category>
            <dc:creator><![CDATA[Ola Sonola]]></dc:creator>
            <pubDate>Mon, 23 Feb 2026 10:26:00 GMT</pubDate>
            <atom:updated>2026-02-23T10:26:00.682Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibVsfx3SvhOlrd81cEtvQA.jpeg" /></figure><p>Let’s be honest — “multi-tenant architecture” sounds simple in theory and messy in reality.</p><p>If you’re a consultant working with MSPs or large enterprises, you’ve probably heard some variation of this:</p><p>“We want full isolation.”<br>“We want shared infrastructure.”<br>“We want it secure.”<br>“We want it cost-efficient.”<br>“And we don’t want operational headaches.”</p><p>That’s exactly where VMware Cloud Foundation (VCF) can shine — if you design it properly from day one.</p><p>First things first: don’t treat multi-tenancy as just resource carving. It’s not about slicing up CPU and RAM. It’s about isolation, predictability, and repeatability across compute, storage, networking, and lifecycle management.</p><p>Start with workload domains. This is your biggest architectural lever in VCF.</p><p>You’ve essentially got two models.</p><p>Option one: one tenant per workload domain.<br>This is clean, simple, and highly isolated. Each tenant gets its own vCenter, its own NSX instance, and dedicated clusters. It’s ideal for regulated industries, finance, or premium MSP offerings where separation isn’t negotiable.</p><p>Option two: multiple tenants in a shared workload domain.<br>More efficient. More density. But also more responsibility on you as the architect. Now you’re relying heavily on NSX segmentation, distributed firewall policies, and carefully designed resource pools. This works well for internal business units or tiered MSP services where hard isolation isn’t mandatory.</p><p>The mistake I see most often? Underestimating networking.</p><p>If you’re still thinking in flat VLAN terms, you’re already behind. NSX is your isolation engine. Each tenant should have its own overlay segments, Tier-1 gateways, and tightly scoped firewall rules. Done properly, tenants can’t see each other — even though they’re running on the same physical hardware.</p><p>Storage is the next lever. If you’re running vSAN, lean into storage policies. Instead of physically separating hardware tiers, define Gold, Silver, and Bronze policies. Different failures-to-tolerate, stripe widths, or performance characteristics. It lets you sell differentiated services without building separate clusters for every tier.</p><p>Now let’s talk about the “noisy neighbour” problem.</p><p>Multi-tenancy falls apart quickly if one tenant consumes everything. Use vSphere resource pools. Define reservations and limits where appropriate. Be intentional. Performance predictability is just as important as security isolation.</p><p>One of VCF’s biggest strengths is lifecycle management. SDDC Manager handles full-stack patching across vSphere, NSX, and vSAN. But timing matters. Don’t onboard a massive tenant deployment right before a platform upgrade window. Align onboarding with lifecycle cycles — your future self will thank you.</p><p>Identity and access control is another area people gloss over. Don’t rely on naming conventions to enforce separation. Integrate with Active Directory or another central identity provider. Use clear RBAC boundaries so tenants can’t accidentally (or deliberately) step outside their lane.</p><p>And don’t forget visibility. Monitoring should be tenant-aware. Whether you’re using Aria Operations or another tool, tenants should only see their own performance data. In MSP environments especially, reporting drives trust, SLAs, and billing accuracy.</p><p>Finally — design for scale.</p><p>Even if you’re starting with two tenants, architect like you’re going to have twenty. Plan IP schemes properly. Size NSX edges correctly. Think about cluster growth. The worst outcome is having to re-architect because the original design assumed “small and static.”</p><p>At its core, multi-tenancy in VMware Cloud Foundation is about balance. Isolation versus efficiency. Density versus predictability. Governance versus agility.</p><p>Get that balance right, and you’ll deliver something powerful: a platform that feels dedicated to each tenant — even though it’s shared underneath.</p><p>And that’s when VCF stops being just infrastructure… and starts becoming a true cloud platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=324e5cf60689" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>