Prashant Musale

🎙️ “You Have to Be Seen and Heard” - Tushar Kulkarni In this inspiring moment, Tushar Kulkarni opens up about pushing past his natural shyness - even as a CEO - and embracing the discomfort of visibility. He reminds us that leadership isn’t just about building products; it’s also about showing up, speaking out, and creating space for others to do the same. “If you are living an entrepreneurial life, a good part of your job is to be seen and heard. And to do that, you have to get out of the comfort zone, meet people, talk to people, explore every channel.” Even after years of running a company, Tushar still works to “force” himself to post, connect, and share - because someone out there may benefit from hearing your story, or at the very least, avoid repeating your mistakes. This clip is a rallying cry to the community: don’t wait until you feel ready. Be seen. Be heard. Start now. 🔔 Subscribe for more real conversations from the voices shaping the Silicon Heartland: https://lnkd.in/gSKEt2Cf 🎧 Full episode drops Friday! #SiliconHeartlandSessions #SiliconHeartland #Podcast #CloudNirvana #TechLeadership #Innovation #IdeaToAction #Inspiration #ProfessionalDevelopment #AI #CloudComputing #TechCommunity Ben Blanquera Steve Gruetter Aaron Littlejohn Trent Taylor Nathan Case Jonathan Erikson James Gehring 🌥 Joseph Emison Matthew Randle Barton Murphy Robert Zwink Cindy Leavitt Bryan Mundy John Bishop Murali Sundararajan Warner Moore Srini K. Rehgan Bleile (Avon) Dan Manges 🗝Connie Matthews Reynolds 🗝 Chris Berry Todd Kaufman Angelo Mazzocco Doug McCollough Tonjia Coverdale, PhD Michael Farrar, MBA Disha Patel Swathi Jillella Cam Avent Michael Chorey Hope Yanling Yin, PCC Mick Miller Marlene O'Neil Scott Lesinski Alfred G. Michael Fulton Scott Shafer Tushar Kulkarni Cloud Nirvana

24

2 Comments

I posted earlier a discussion on RAG Systems’s Hidden Constraint -  ended with a generic comment about “Engineered Knowledge” as a solution. I was expecting someone to hit my head in the comments section, saying “That’s all right, RR. It’s okay to rant, especially since you are recuperating. But what is the real solution beyond the coined term “Engineered Knowledge”? How would anyone turn that term into an action?” If someone asked, that would be perfectly alright, and if I were the reader, I would definitely ask the writer that question. What I was thinking when I used the term “Engineered knowledge” is more along the lines of domain ontology-based canonical representations. Certain healthcare domains, such as clinical, already have it, like in the form of FHIR + SnowMed-CT. Continue to read .. https://lnkd.in/e-5tCJPs #RAG #LLMs #KnowledgeEngineering #PromptEngineering #AI

12

⛰️ The biggest challenge for software engineers isn't learning AI, it's unlearning old habits… 🧩 Adopting and integrating generative AI is about building compound AI systems that seamlessly integrate multiple models, tools, and existing systems. 🧑‍💻 It's not about replacing engineers—it's about equipping them. 🎶 Engineers must orchestrate a symphony of models, APIs, and traditional code to tackle complex challenges, elevating their role from builders to orchestrators of intelligent solutions. 🔑 The key is moving beyond simple AI tools and embracing Compound AI Systems. #GenerativeAI #AI #SoftwareEngineering #Developer #Innovation #AIStrategy #CompoundAISystems

9

𝗛𝗼𝘄 𝘁𝗼 𝗱𝗼 𝗺𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲 𝗽𝗿𝗼𝗽𝗲𝗿𝗹𝘆? 𝗦𝗲𝗹𝗳-𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗱 𝗦𝘆𝘀𝘁𝗲𝗺𝘀 (𝗦𝗖𝗦) is a software architecture approach that prioritizes the decentralization of applications into independent systems, each with its domain logic, UI, and data storage. Unlike Microservices, smaller services focused solely on business logic, SCS are larger and encompass a broader scope within a specific domain. SCS are systems that represent 𝗮𝘂𝘁𝗼𝗻𝗼𝗺𝗼𝘂𝘀 𝘄𝗲𝗯 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀, which include web UI, business logic and database, and it might have a service API. A single team usually owns them. The main 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 of such systems are: 𝟭. 𝗔𝘂𝘁𝗼𝗻𝗼𝗺𝘆 - Each SCS operates independently with its database, business logic, and user interface. 𝟮. 𝗗𝗼𝗺𝗮𝗶𝗻-𝗮𝗹𝗶𝗴𝗻𝗲𝗱 - SCS is structured around specific business domains, ensuring each unit represents a coherent and meaningful set of functionalities. 𝟯. 𝗗𝗲𝗰𝗲𝗻𝘁𝗿𝗮𝗹𝗶𝘇𝗲𝗱 𝗗𝗮𝘁𝗮 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 - Individual databases per SCS ensure data consistency within its boundary, reducing cross-service dependencies. 𝟰. 𝗧𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 𝗗𝗶𝘃𝗲𝗿𝘀𝗶𝘁𝘆 - Allows for different technology stacks to be used across other SCS, suiting the specific needs of each domain. 𝟱. 𝗘𝘅𝗽𝗹𝗶𝗰𝗶𝘁𝗹𝘆 𝗣𝘂𝗯𝗹𝗶𝘀𝗵𝗲𝗱 𝗜𝗻𝘁𝗲𝗿𝗳𝗮𝗰𝗲 - Well-defined interfaces for interactions with other systems, maintaining a clear contract while preserving encapsulation. 𝟲. 𝗜𝗻𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝘁 𝗗𝗲𝗽𝗹𝗼𝘆𝗮𝗯𝗶𝗹𝗶𝘁𝘆 - Each SCS can be deployed, scaled, and updated independently without affecting other systems. Such systems go well along with 𝗗𝗼𝗺𝗮𝗶𝗻-𝗱𝗿𝗶𝘃𝗲𝗻 𝗗𝗲𝘀𝗶𝗴𝗻 (𝗗𝗗𝗗). The first step in creating such systems is domain analysis, which can be conducted by identifying bounded contexts that align with specific business domains. Each bounded context is then encapsulated within an SCS, which comprises its own data management, business logic, and user interface, ensuring each system is autonomous yet able to interact with others through well-defined APIs when necessary. Why Self-contained Systems (SCS) has the 𝗲𝗱𝗴𝗲 𝗼𝘃𝗲𝗿 𝗺𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀: 🔹 𝗕𝗿𝗼𝗮𝗱𝗲𝗿 𝘀𝗰𝗼𝗽𝗲: SCS has a broader scope encompassing the UI, business logic, and data storage within a bounded context 🔹 𝗥𝗲𝗱𝘂𝗰𝗲𝗱 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗖𝗼𝗺𝗽𝗹𝗲𝘅𝗶𝘁𝘆: Microservices can lead to a high level of operational complexity due to the management of many smaller, interdependent services, while SCS is more significant and more autonomous. 🔹 𝗗𝗮𝘁𝗮 𝗖𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝗰𝘆: SCS manages their data, leading to better data consistency within each system, while Microservices often rely on a shared data store. Check the full link in the comments. #technology #softwareengineering #softwaredesign #techworldwithmilan #microservices

34

Developed the initial messaging application for our client leveraging AWS   AppSync and Event Handler architecture. The system processes incoming  messages through the Event Handler and broadcasts them via EventBridge.  AppSync significantly simplified the implementation compared to  alternative solutions like API Gateway with WebSocket integration.

24

1 Comment

As we approach the fourth quarter of 2025, India’s economy appears positioned for a consumption-led recovery. US H-1B Visa Revisions: The policy introduces a $100,000 fee for new applications, effective from the March 2026 lottery cycle, but spares renewals and existing holders. Visa issuances to leading Indian and India-centric firms have decreased from 14,792 in 2015 to 10,162 in 2024, representing less than 1% of their workforce. We anticipate limited overall impact, with potential shifts toward alternative staffing models. This may accelerate offshoring and the expansion of Global Capability Centers in India, supporting sustained growth in the technology services and back-office sectors. GST Overhaul: Implemented on September 22, the reform simplifies the regime into a two-tier structure, reducing rates on mass-consumption goods and phasing out compensation cess on most luxury items. Government estimates suggest an injection of approximately INR 2 trillion into the economy, fostering broad-based consumption. The automobile sector is particularly well-placed to benefit, with rate reductions including small cars and compact SUVs from 29-31% to 18%, two-wheelers from 28% to 18%, and tractors to 5%. These changes are expected to enhance affordability and stimulate demand across urban, semi-urban, and rural markets. Festive Season and Budget Support: Coinciding with India’s festive period—a traditional peak for discretionary spending—the GST adjustments align with the February 2025 Union Budget’s personal income tax reductions under the new regime. These measures aim to increase disposable income for middle-class households, with effects likely to materialize more prominently in the latter half of the year. We foresee positive implications for Q4 2025 earnings in consumer-oriented sectors such as automobiles, retail, and discretionary goods. In aggregate, these developments underpin a constructive view on India’s economic trajectory, with domestic demand offsets potentially mitigating external pressures from visa policy changes.

17

Who said insurance cannot be fun and exciting - Here is my Insurance Innovators 2025 take so far: Transforming Risk with Tech, Trust & Talent Big shifts are reshaping the insurance industry, and this year’s event is all about future-ready transformation so far! Key takeaways so far: * Customer-Centric Innovation: From dynamic coverage updates to personalized digital journeys. * Modular Tech Ecosystems: Flexibility is the future—plug in, scale up, adapt fast. * Data-Driven Decisions: Trustworthy, governed data is the backbone of effective AI. * AI with Purpose: From risk modeling to climate resilience—AI is moving from pilot to production. * Upskilling Humans: Agentic AI isn’t replacing agents—it’s enhancing them. * Compliance & Governance: As tech grows, so does regulatory responsibility—especially with cyber and AI. * Innovation That Delivers: Real gains seen in predictive analytics, cost efficiencies, and risk interconnectivity. Yes - "Change is an opportunity, not a threat.", and that mindset is what will define the next era of insurance. #InsuranceInnovators #AI #DataDriven #FutureOfInsurance #Insurtech #DigitalTransformation #RiskManagement #CustomerExperience

80

2 Comments

Lessons from Migrating 200+ Insurance Products to Duck Creek Over the past few years, I have been involved in a large-scale core insurance modernization initiative, consolidating 200+ financial lines products across multiple policy administration systems into the Duck Creek platform. Programs like this are not just technology upgrades — they are enterprise transformation efforts that impact underwriting workflows, operations, and customer experience. Here are a few lessons that stood out during this journey. ⸻ 1. Product Rationalization Comes First Before touching technology, organizations must address product complexity. Many insurers accumulate hundreds of product variations over decades. Migrating them directly into a new platform often recreates the same complexity. A successful modernization effort requires: • Rationalizing product definitions • Standardizing underwriting rules • Consolidating redundant product variations This step alone can dramatically simplify the migration effort. Platform Strategy Matters More Than Configuration Core systems are extremely powerful, but the biggest value comes from defining the right platform architecture. A strong platform strategy should focus on: • Reusable product components • Configurable rating and rules engines • Standardized integration patterns • Clear inheritance and product hierarchy models This helps ensure the platform remains scalable and maintainable over time. ⸻ 3. Integration Architecture Is Critical Core insurance platforms rarely operate in isolation. The Duck Creek platform needed to integrate with few downstream systems, including: • Claims systems • Billing platforms • Document management systems • Analytics platforms Designing a robust integration architecture using APIs, event-driven patterns, and messaging frameworks was essential for long-term scalability. ⸻ 4. Automation Unlocks the Real Value One of the biggest benefits of modernization comes from automation. Example, Renewal Automation Framework helped reduce manual processing in the policy renewal lifecycle by enabling straight-through processing. This allowed underwriting teams to focus on risk assessment rather than administrative tasks. ⸻ 5. Technology Is Only Part of the Transformation The biggest challenge in large modernization programs is not technology — it is organizational alignment. Successful transformations require: • Strong collaboration between business and technology teams • Clear governance models • Continuous communication with stakeholders When business and technology leaders move together, modernization becomes a true enabler of innovation. ——— Core system modernization remains one of the most impactful initiatives insurers can undertake. With emerging technologies like Gen AI, the next wave of transformation will focus on accelerating development, improving productivity, and enabling smarter underwriting decisions. Exciting times ahead for the insurance technology space

15

2 Comments

Canvas Apps: From Rapid Prototypes to Enterprise-Grade Platforms Low-code doesn’t mean low-standards. Canvas Apps have become a powerful lever for accelerating digital transformation, but only when built with enterprise discipline. Poorly designed apps can lead to slow load times, governance gaps, and user resistance. In contrast, well-architected apps deliver speed, security, and scale. Our latest presentation outlines what separates tactical apps from strategic platforms: 🔹 Performance by Design Optimized startup logic, delegable queries, concurrent data loading, and control discipline ensure apps launch fast and remain responsive—even at scale. 🔹 Security & Governance First Deep integration with Microsoft Entra ID, role-based access, connection references, and environment separation (Dev/UAT/Prod) provide audit-ready control without hindering innovation. 🔹 Data & Integration Strategy Smart connector usage, Dataverse-first architectures, and gateway-based on-prem integrations reduce risk while enhancing performance and maintainability. 🔹 User Experience that Drives Adoption Modern Fluent UI controls, responsive layouts, accessibility-first design, and consistent visual hierarchy ensure apps are intuitive—not just functional. 🔹 Built for Longevity Source control, naming conventions, reusable components, and lifecycle management transform Canvas Apps into sustainable assets—not disposable tools. Executive takeaway: Canvas Apps succeed when treated as products, not experiments. With the right architectural guardrails, they become a scalable extension of your enterprise platform strategy. If you’re evaluating Canvas Apps for mission-critical workflows or scaling beyond pilot use, this framework helps ensure your investment delivers measurable ROI, governance confidence, and user adoption. #DigitalTransformation #PowerApps #LowCode #EnterpriseArchitecture #CTOStrategy #CXOInsights #Governance #ScalableSystems

6

AI Companion vs. AI Assistant vs. AI Agent: What’s the Real Difference? Artificial intelligence is evolving rapidly, and understanding the distinctions between an AI Companion, AI Assistant, and AI Agent can help you leverage these technologies effectively. AI Companion: Your Thought Partner An AI Companion is designed to think with you — it remembers your preferences, adapts to your style, and supports your creative and strategic thinking. Remembers and adapts over time Helps brainstorm, plan, and learn Engages in natural, flowing conversations Examples: Microsoft Copilot/Chat GPT as a conversational partner, Replika-style companions for emotional support. AI Assistant: Your Reliable Helper An AI Assistant executes commands and completes tasks efficiently, responding to your instructions. Sets reminders, drafts emails, retrieves informationBoosts productivity and organization Examples: Siri, Google Assistant, Alexa. AI Agent: Your Autonomous Executor An AI Agent acts independently to achieve goals by breaking down complex tasks and taking actions on your behalf. Runs multi-step workflows Uses tools and APIs autonomously. Examples: Copilot Actions, AutoGPT-style agents. These AI types complement each other, offering powerful tools to think with, help you, and act for you.

18

1 Comment