Sriram Krishnan

AI Tip of the Week: I was chatting with Saishridhar Balamurali about what happens when an LLM seems to go down a rabbit hole while I’m working on a problem. My usual reaction is to clear the context and start over. Sai suggested a different perspective: the model isn’t “stuck,” it’s just missing a key piece of information needed to solve the problem. Instead of restarting, pause and think about what might be missing and feed that in. That clicked for me — it opens up a whole new way to revisit some of my work-in-progress solutions! #GenerativeAI #AI #ChatGPT #MachineLearning #LLM #ArtificialIntelligence #FutureOfWork #Innovation #TechTrends #Productivity

37

8 Comments

Final AARC-TREE meeting🌳🌳🌳 With the AARC Blueprint Architecture (BPA) 2025 and the Policy Development Kit (PDK) v2, the AARC Community and the project delivers a solid, practical foundation for AAIs supporting research infrastructures. In plain terms: The BPA explains how an AAI should be built — the technical building blocks and how they fit together. The PDK explains how trust is organised — the policies, roles, and agreements that let organisations collaborate safely. Together, they help research infrastructures move from concepts to operations: clearer architecture, shared policy language, and more interoperable and trustworthy access across borders, with the European Open Science Cloud (EOSC) Federation is a key and very concrete use case. 🚀 #AARC #EOSC #AAI

30

ICYMI: The AI Center for Government™ recently posted two new features in their AI Bright Spots series ✨ The AI Bright Spots are incredibly well-written (shout out Madeleine McCullough) and really interesting. Follow along with this series to hear how government leaders, like Michael Baskin and Natalie Buda Smith, are leveraging AI solutions.

12

2 Comments

Principle #6: Insights Must Drive Action From the 10 Principles for Building a Resilient and High-Impact APM Program Knowledge has never been more available. From stories once passed orally across generations, to the printing press, to the internet, and now to large language models, humanity continues its quest to make knowledge instant and abundant. We’ve lived through the Information Age and now stand in a time where knowledge is increasingly commoditized. What once took decades to master can now be accessed in moments. Knowledge alone is no longer the differentiator. We are entering the Wisdom Age, a time where the true advantage lies in the ability to convert information into action. Wisdom, unlike knowledge, isn’t free yet. It must be earned. It requires experience, context, accountability, and a willingness to learn. As the saying goes: you must “pay” attention. In Asset Performance Management, the same truth applies. Insights, whether from condition monitoring, corrosion models, predictive analytics, or SIS verifications, must not remain passive. Awareness alone does not prevent failure. APM programs must be architected to translate signals into timely and accountable smart decisions. One of the clearest examples of wisdom in APM is the trade-off between planned and unplanned downtime. With the right insights, organizations can shift from reactive interventions to proactive actions, accepting a short, planned outage today, to avoid a prolonged, unplanned crisis tomorrow. This is an operational decision directly impacting the business, protecting throughput, cost structure, and safety. Work orders must be issued. Shutdowns must be justified. Investigations must be triggered. Safety reviews must be escalated. Each insight must lead to a structured response, documented, traceable, and continuously improved. When insights don’t drive action, organizations remain stuck in observation mode. They predict failure just to fail preventing it. When wisdom is embedded into the system, when APM is designed to detect and to respond, insights become results. Organizations become proactive, disciplined, and trusted stewards of asset performance. In short: Knowledge tells you what could happen. Wisdom ensures you do something about it, before it costs you more. #APM #AssetPerformanceManagement #IndustrialExcellence #Reliability #DigitalTransformation #MaintenanceStrategy #OperationalDiscipline

20

1 Comment

As COO at www.jaiinfoway.com this is an important signal for where agentic AI is heading. Non technical implementations are catching up fast but the real story is iteration speed and learning loops. Building Cowork entirely with Claude Code shows how agents are becoming first class workers not just assistants. At www.jaiinfoway.com we see this shift clearly as enterprises move from copilots to autonomous task execution with guardrails. UX will evolve tooling will mature but the direction is set. Curious how others here see non technical users adopting agent driven workflows this year. Are we ready for agents as coworkers. #Jaiinfoway #AgenticAI #Claude #AIAgents #EnterpriseAI #FutureOfWork #AIProductivity #AITransformation #AILeadership

2

GovTech is no longer emerging—it’s defining the future of public service. A new report, “The Silicon State: How GovTech is reinventing public services”, reinforces what has long been evident to those working closely with governments: the shift from e-Government to Government as a Service (GaaS) is well underway. Across the public sector, familiar patterns are accelerating: • The global GovTech sector is projected to reach $2.3 trillion by 2033, fuelled by rising citizen expectations, fiscal constraints, and rapid technological progress. • Countries like Estonia are setting the pace, demonstrating how digital ID, open architecture, and public-private collaboration can drive measurable impact—saving up to 2% of GDP annually. • Governments are increasingly thinking in platform terms, modernizing procurement to support agile delivery, SaaS solutions, and collaborative ecosystems. • At the same time, equity, transparency, and inclusion must remain top priorities as GovTech continues to scale. This evolution is no surprise. It reflects a long-building recognition that digital tools alone are not enough—governments must enable innovation, empower civil servants, and build trust with citizens. The opportunity ahead is enormous. And the most forward-thinking governments are already moving. Full report: https://lnkd.in/etPZEbUD #GovTech #PublicFinance #GovernmentasaService #DigitalGovernment #SmartGovernment #PFM #DigitalTransformation

15

Delighted to share that DexTech Inc. is one of the awardees of this year's Penn AITC opportunity. This $200,000 grant will enable us to develop an initial prototype of our wearable solution that we will test in a future study. Our solution will increase mobility and autonomy, and reduce fall injuries in people with Parkinson's Disease. This consortium has been funded by the National Institute of Aging (NIA). Dextech was one of 10 companies nationwide selected for funding. Our feasibility testing will be conducted with the help of collaborators Brian Wright at DePauw University and Jenae Bennington at The Towne House Retirement Community. We cannot wait to get started.

74

15 Comments

I love Rails. I've built my wealth on it. That's exactly why I think we need to have an honest conversation about its biggest blind spot. Eileen M. U. gave a brilliant talk at Rails World last year: "The Myth of the Modular Monolith." After 6 years of modularizing Shopify's monolith, she concluded: "You can't solve human and cultural problems by changing your architecture." She's right kinda of about the culture part. But stopped one step short. Rails doesn't just allow tight coupling. It incentivizes it. ActiveRecord makes every model globally accessible from anywhere. Any controller, any model, any job can reach into any table through any association chain. There's no boundary enforcement. No import restriction. No compilation step that says "this module shouldn't know about that one." When your framework makes coupling the path of least resistance, blaming developers for coupled code is like blaming water for flowing downhill. Shopify tried to fix this with Packwerk. It just give you a map not a real solution. Rails Engines? Been there, done that. They are miniature apps that provide functionality to their host applications. They don't enforce real isolation and they weren't designed for progressive extraction. But this isn't a Rails problem. It's a missing tool problem. Look at what Nx did for the Node/TypeScript ecosystem: → Module boundaries enforced at the import level, not via YAML to-do lists → Dependency graph visualization built in → Affected-only CI: only test what actually changed → Clear public API per module, everything else is private by default → A real path from monorepo module to extracted service Nx didn't replace Node. It gave Node developers the guardrails to build modular systems naturally. The right thing became the easy thing. By default. Rails deserves the same. Imagine a Rails-native tool that: • Enforces module boundaries through autoload paths, not opt-in linting • Gives each module a public API (explicit exports) while keeping internals private • Generates a live dependency graph from actual code usage, not manual YAML declarations • Runs affected-only CI based on that graph Not a replacement for Rails. A companion that makes Rails' conventions work at scale. Eileen is right: culture matters. Education matters. Leadership incentives matter. But culture alone didn't give us CI/CD. Tools did. Culture alone didn't give us code formatting standards. Linters did. Culture alone won't give us modular Rails applications. Rails gave us developer happiness for building products. Now we need the same philosophy applied to building organizations of code. The myth isn't the modular monolith. The myth is that we have the right tools for one. Who's building this? 🎥 Eileen Uchitelle — "The Myth of the Modular Monolith" (Rails World 2024) https://lnkd.in/dabvzHQm

13

A strong defense industrial base needs a thriving and diverse innovation ecosystem, with low barriers to entry for new companies and emerging tech. Join Matt Bigge, partner at Crosslink Capital and a panel of experts from Expedition Fund, Hanover, and General Innovation as they explore the drivers of private equity investment in defense technology startups at the Oracle Defense Tech Summit. https://lnkd.in/gBqxSCdS

1