🌞 Join us for another awesome meetup before the summer! 🌞
We are thrilled to announce an exciting lineup of speakers for this upcoming event.
Prepare to be inspired by some of the best minds in the industry. Chris Klug, the Developer Badass-as-a-Service, will be sharing his insights on Actor-based Development with Project Orleans.
Tess Ferrandes-Norlander, a renowned developer and data scientist from Microsoft, will guide us through the intricacies of effective code reviews in her talk titled “How to ruin a code review in 20 ways.”
In addition to the enlightening talks, we have arranged for delectable food and drinks during the break, offering you the perfect opportunity to network and mingle with fellow enthusiasts. 🍕🍺
Here are the practical details you need to know:
Location: Voyado c/o DoSpace Link
Address: Gamla Tanneforsvägen 92, Linköping
Time and date: 17.00, Tuesday the 20th of June
Language: English (or Swedish if everyone prefers that)
Whether you are a seasoned professional, a curious learner, or simply someone looking to connect with like-minded individuals, this meetup promises to be an enriching experience. We can’t wait to see you there!
17.20 Lecture 1
18.20 Food & drinks
18.50 Lecture 2
Session 1 – Chris Klug, Developer Badass-as-a-Service
Chris Klug is a developer badass-as-a-service that either creates or solves problems depending on who you ask. He loves creating and building things. Whether it be a new application, a new kitchen or a new RC helicopter, you will see him building things all the time. Most of the time, that means writing code and solving problems for clients at a company called Active Solution in Stockholm though. Except for the many days he spends at conferences and usergroups, talking about doing things he is passionate about, and for the days he goes mountain biking, IPSC shooting, kiteboarding or RC helicopter flying.
For the last 15-something years, he has been solving problems for customers, and loving it. But if he gets to choose, he’ll go to the beach and kitesurf every day!
Introduction to Actor-based Development with Project Orleans
There are some domains that are really hard to model using your standard n-tier architecture. Domains like real time vehicle tracking, auctions and many IoT scenarios. Sure, they might look easy enough, and “work on my machine”, but when you start throwing some load at it, it can start to crumble quite quickly. And going down the good ol’ “Eventual Consistency Road” isn’t always an option, as consistency is actually important in some cases.
However, these aren’t new problems, and smart people have already created solutions for them. Solutions like the Actor pattern, which solves the problem by using in-memory “actors” to make life simpler. Unfortunately, the Actor pattern introduces another set of challenges. Things like instance proxying, state management, clustering, actor distribution and so on. Topics that most of us don’t feel like solving on our own. Luckily, Microsoft has already built all of this for us, in something they call Project Orleans.
Why not join Chris Klug, as he explains how Project Orleans can help you to solve scenarios like the ones described above. It might be worth noting though, that if you like slide heavy presentations with lots of theory and little practice, you should probably stay away. This session uses lots of demos to show you the practicalities of getting started building solutions using Project Orleans, and the features is offers. So please come well rested, and ready for a lot of coding.
Session 2 – Tess Ferrandez-Norlander, Developer
Tess is a developer/data scientist working at Microsoft. Over the past 20 years she has changed the way we do .net debugging, developed a large number of mobile apps. As of a couple of years ago she moved into the world of data science and machine learning working with a lot of the largest companies in Europe and beyond on really tough ML problems.
She has spoken at lots and lots of conferences around the world on a wide variety of topics including deep .net debugging, UX, web development and Machine Learning.
Better Code Reviews FTW
Is the best way to make someone’s code better, really to bombard them with 50 things they did wrong? Maybe there is a more human way to give feedback on code that not only leads to better code but to better collaboration.