Kyle Burns

Finish this sentence: Advising teams who do not write tests when developing software to adopt Trunk Based Development is akin to ____________________

1

3 Comments

As Enterprise Leaders, we need to develop and create holistic experiences across the organization and ecosystem. Influencing strategies and shaping outcomes is essential at all levels, achieved by linking diverse perspectives  and components (views and elements of an enterprise) within an organization’s ecosystem. Successful leaders strive to create a vision that influence strategies and continually refine them based on the changing landscape, culture, and the transformational needs. A framework like the one below supports enterprise leaders to implement successful strategies to empower the mission, vision and values of the organization and its role in the larger ecosystem.

6

1 Comment

Most digital transformations fail not because of bad software—but because no one questions the story behind the investment. It’s not about tech. It’s about alignment.

8

AEMC just released a proposed rule to help AEMO manage minimum system load. It’s a signal: The low-demand challenge is no longer a fringe scenario, it’s becoming an operational norm. The Minimum System Load Reserve Service (MSLRS) would give AEMO a structured way to call on reserves when demand drops too low, especially during high rooftop solar output. Why does this matter? Because most utilities are still preparing for peak loads. Very few are truly ready for minimum load events. This flips the script on how we think about system risk. To play a role in this reserve, or even stay ahead of it, utilities need to ask: → Can we locate and aggregate flexible load in real-time? → Do we have telemetry from DER, AMI, and market-facing systems that sync? → Can we prove response capability when AEMO needs it? → Are we building the integration foundations for participation, not just compliance? MSLRS isn’t about adding a new system. It’s about whether your current systems actually work together when it matters most. This is a chance to get proactive, not reactive. DM me if you're building toward operational readiness for emerging reserve and flexibility services. We’ve been working on this behind the scenes for a while. #Energy #AEMO #Australia

14

People often think integration is a technical milestone. I see it as a trust milestone.    If your Core ERP, Digital Twin, Maintenance Logs, and Asset Data Store still feel like separate tools, you don’t have integration — you have stitched software.    In architecture discussions at AsInt, Inc., I keep asking my team: “Can the user move between actions without thinking about which system they are in?”    That’s what a true ecosystem feels like — no drop-off, no context loss, and no tech fatigue.    My belief is simple: The more seamless your architecture, the less users talk about the platform. And that’s a good thing.    To fellow architects and technology leaders: What’s harder in your experience: building the feature, or getting users to forget it’s a feature? Jarret | Jeremy | pruthvi | Rohan | Michael | Raunak | Prateek #EnterpriseArchitecture #IntegrationArchitecture #UserExperience #TechnologyStrategy #ThoughtLeadership

53

𝐓𝐡𝐞 𝐑𝐞𝐚𝐥 𝐌𝐨𝐝𝐞𝐫𝐧𝐢𝐳𝐚𝐭𝐢𝐨𝐧 𝐏𝐫𝐨𝐛𝐥𝐞𝐦 Many IBM i modernization challenges aren’t about technology limitations. They’re about application structure. Over time, RPG systems often evolve into tightly coupled designs where business rules, data access, and process flow are all intertwined. This makes integration difficult — even when the platform itself is capable. 𝗧𝗵𝗲 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 𝗺𝗶𝘀𝘁𝗮𝗸𝗲 𝗶𝗻 𝗜𝗕𝗠 𝗶 𝗺𝗼𝗱𝗲𝗿𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻 Companies start with the UI. Green screens become web screens. Start here instead: • Extract service programs • Define domain boundaries • Expose business logic through APIs Once the architecture is modern… the UI becomes easy. Breaking functionality into service programs is often the first meaningful step toward modernization. It allows logic to become reusable, testable, and ready for API exposure. 𝑾𝒉𝒂𝒕 𝒎𝒐𝒅𝒆𝒓𝒏𝒊𝒛𝒂𝒕𝒊𝒐𝒏 𝒔𝒕𝒆𝒑 𝒈𝒂𝒗𝒆 𝒚𝒐𝒖 𝒕𝒉𝒆 𝒃𝒊𝒈𝒈𝒆𝒔𝒕 𝒘𝒊𝒏?

23

7 Comments

When consuming a REST endpoint from #PeopleSoft, do you have to declare every response attribute? To answer that question, I have to ask: Do you want the framework to parse the response? If you want Integration Broker or Application Services to parse the response for you, then, yes, you must declare all of the attributes. But if you are happy to parse the response yourself (JsonParser), then no. You don't have to declare any attributes. Considering that some API's return several dozen attributes, we can save a lot of time by just parsing the response ourselves! We teach tips like this in our three-day Integration Tools Update course. Check it out! https://lnkd.in/gRVAx3PA

6