Tech Tribes Talks

There are plenty of talks on Observability and OpenTelemetry that are trying to convince you to jump on the bandwagon. But what happens when you actually do buy into it? What opportunities are there, and what challenges will you face? And most importantly: is it all actually worth the effort

At my customer, we moved our entire stack from Application Insights to OpenTelemetry and DataDog. That means 100+ services deployed on a variety of platforms, from IaaS Virtual Machines running websites in IIS to Azure App Services, Azure Function Apps and Azure Container Apps, all backed by various other Azure components. We defined SLA's, added monitoring and alerting and fundamentally changed the way we handled outages.

If you've never heard of Observability or OpenTelemetry this probably isn't the session for you. But if you want to hear a somewhat grizzled developer talk about his experiences with helping to move a whole organization and its technical stack forward along the path of Observability, this is one you can't miss.

In an ever growing world of data and a continuously increasing amount of services being used; the need for a reliable and clear performance testing framework rises. Although many solutions are available in the current technological landscape, many either require expensive licenses or fall short when it comes to test adaptability or reporting visibility. In this talk I will discuss the strengths and weaknesses of the open-source performance testing solution that is K6. Taking a look at its testing capabilities, integration in pipelines and reporting options.

Join us for an engaging session where we explore the powerful world of Grafana. We'll start with an overview of the diverse products and tools offered by Grafana, highlighting how they cater to various observability needs.

Dive into Grafana's "Big Tent" philosophy, which emphasizes inclusivity and flexibility, allowing seamless integration with over 100 data sources.

Finally, we'll showcase some of the latest and most exciting features recently announced, with practical demos to illustrate their capabilities in real-world scenarios.

DevOps is by now a widely accepted paradigm in Software engineering. As the realization that end-to-end ownership of an application consists of more than having push rights to the repository of both your backend and frontend is starting to settle in at even the most enterprisey of enterprises, you might start to feel lost on how to get started.

Are you feeling daunted by the idea of taking actual ownership? Or perhaps you've already recognized the benefits of taking charge of application delivery but find yourself entangled in the cogs of the software factory around you.

Join me as I guide you through my growth path from being a purely backend-focussed developer, to being the DevOps contact in my team.

I'll highlight key difficulties I've encountered and discoveries I've made along the way that helped me to achieve what I'm most passionate about: delivering better software, faster.

De talk richt zich op datagedreven werken in de zorg en laat zien hoe data op een slimme manier kan worden ingezet om zorgprocessen te verbeteren. We volgen een praktijkcase waarin we stap voor stap de route doorlopen: van een uitgebreide Data Health Scan, die inzicht geeft in de huidige stand van data binnen de organisatie, naar het ontwerp en de realisatie van een datagedreven oplossing die aansluit op de specifieke behoeften van de zorginstelling. Tot slot bespreken we de impact die deze aanpak heeft gehad op de organisatie, waarbij we ingaan op de veranderingen in werkwijzen, cultuur en resultaten die met deze transformatie zijn bereikt.

Starting from a c-style language (typescript), diving it common problems and solutions for them. Comparing them to other languages like go and rust, to better understand tradeoffs and maybe act as an eye opener for some

This talk will cover performance optimizations. Performance optimizations you're very unlikely to ever need. Performance optimizations you should probably not even consider. Performance optimizations that will get you fired. It will go lower down the stack than you'll probably ever need in your career, all for the sake of performance. For the sake of those juicy benchmark numbers, the slightly lower infrastructure bills, and the vague sense of superiority from knowing that your code runs just that little bit faster than everybody else's.