Ayan's TechTalk

  Ah, the enduring saga of modernization! After years navigating its currents across diverse industries, one truth resonates deeply: while the terms 'modernization' and 'transformation' often intertwine, their essence, particularly within the realm of software and applications, holds distinct nuances. Let us focus on the former, leaving the broader scope of transformation for another tale. In its nascent stages, application modernization was largely about breathing new life into systems forged in the technological landscape of prior decades. The aspiration was clear: to harness the agility and efficiency of the cloud, to deliver features with greater velocity, and to fortify the non-functional pillars upon which robust systems stand. This journey has unfolded in waves, from the architectural shifts of Service-Oriented Architecture (SOA) to the dynamic world of cloud-native microservices and the imperative of automated pipelines. Yet, even now, defining its scope, securi...

This has been marinating in my head for a while, it's time to spit it out. I will cover my approach at F****A around why, what, who and how I helped mature the organization. To give a brief background, when I landed there, I spent some time meeting with my peers, leaders and team to gauge the current state software architecture and delivery. I was also given a list of objectives from my leadership team, most of which were multi year scope, but I was able to start on the top few priority items immediately. I decided to jot these down so that I could spread this across the organization. The What and Why? This set the foundation of the capabilities and why they are important for the organization.  Why Not? I also decided to create some distinction of why we decided to move towards Platform Engineering from DevOps . It was important to capture this distinction for everyone.  Who did What? The next big question was how to structure the team around these capabilities (What). It's n...