Skip to main content

Future Tech 2025

Last week I had the opportunity to participate and speak at Future Tech 2025. And although it was the 7th edition, it was my first time there, so I didn't know what to expect. The Future Tech team was very kind and walked with me to the speaker room (yes, free 'stroopwafels'). When the opening was announced, I entered the main room together with 700+ other software developers still unaware of what would happen next.

And then Anjuli Jhakry and Dennis Vroegop took the stage…

What started as a small introduction of the agenda, evolved in a story about fear and ended with the key message that we all should confront and embrace our fears. This all brought in such a vulnerable and strong way (no I will not spoil how they did it) that it will stick with me for the rest of my life. What a great intro and exceptional example of storytelling. Kudos to both Anjuli and Dennis!

After putting the bar so high, Roelant Dieben and his AI companion took the stage for his keynote to talk about how we’ll become AI centaurs, combining human and AI capabilities. They both did an amazing job, although I had the feeling that Roelant AI companion didn’t always wanted to follow the agreed script.

I missed the last keynote by Shawn Wildermuth as I had to get ready for my session. Sorry Shawn!

This is no longer the job I signed for

In case you missed my session, here what is was all about:

Every industry encounters moments of disruption, and for IT, that moment is now. With AI reshaping the landscape, the role of developers is undergoing a profound transformation. Whether you view this as a threat or an opportunity, one thing is clear: change is here. In this session, Bart will help you navigate the path to becoming an AI-native developer and uncover what this new era means for your career.


The future of your role starts here.

I will not go in depth as I have planned to write a few follow up posts going in much more detail. You can find the slides here and the session is recorded. When it will be shared I put the link here as well.

From Pixels to the Cloud: Mastering XR with Azure

After my session I decided to give 2 of my colleagues and fellow MVPs Saskia Groenewegen and Michiel Hamers some moral support. Knowing very little about XR, this was a great introduction for me to better understand what is possible today in XR development and how Azure (AI)  can help here.

I especially liked the many demos as it showed quite well what XR has to offer in a business context.

Extending GitHub Copilot: Building Agents and Skillsets

After lunch, I joined the session of Cecilia Wiren who showed us how it easy it is to extend GitHub Copilot by creating your own agents and skillset. In 45 minutes she succeeded in explaining all the required steps to get your own skillset or agent integrated. I immediately was hooked and have planned on using the information she shared to build my own agent soon.

More info to come…

10 years of Event Sourcing; thoughts and experiences

After working on multiple event sourced solutions myself, I was interested to learn on what the experiences and thoughts of Dennis Doomen were.  He took on the impossible challenge to share all his experience of practicing Event Sourcing in 45 minutes. He shared some of the lessons he learned along the way, some benefits and potential pitfalls (where I have experienced some of them myself) and what tools and technologies he would recommend when you want to apply Event Sourcing today.

Conclusion

I have to say that really liked the conference; well organized, not too big, a nice venue and of course great content and speakers. I had the opportunity to meet a lot of nice people and learned a lot.

Already looking forward to the next edition!

More information

Future Tech 2025 | The .NET Conference Future Tech

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...