#149 TG-NET Meeting

🕕 18:00 : Damian Płaza – You can be full-stack again – using hypermedia to drive your .NET applications and save the world with C#

🕖 19:00 : Łukasz Jarmułowicz – Jak AI zmienia produkt (i zabiera pracę innym)

🕗 20:00 : Adam Furmanek – Basics Designs and How We Got Them Wrong

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 Presentation 1:
18:00 — Damian Płaza – You can be full-stack again – using hypermedia to drive your .NET applications and save the world with C#

🧾 Description:
Imagine that a product owner comes and says we are going to build a new product - and you are the one to make a decision. It's mostly lists, texts, some images, a bunch of buttons here and there. What would you pick? React? Angular? Vue? Solid? Probably you already have front-end engineers, so something that they need to later maintain.
Picking SPA framework just because it's modern, brings quite interesting challenges - now you need to synchronize the work between "backend and front-end" (do you recall "we are waiting for other side" symptom?), maintain security vulnerabilities of the packages you barely heard of, resist the strong urge to introduce yet-another-flashy-package in your ecosystem, because front-end influencers told so on X, discuss over and over various state management libraries and their superiority, React introduces weirder and weirder hooks...
...But what the end user really needs is lists, texts, some images and bunch of buttons here and there. What could possibly go wrong? Turns out that we don't need this all of this to build highly-interactive, modern-looking web products. Merchants of complexity wanted us to believe that we need all of that to ship fast, maintain for centuries and delight our users. We can bring the simplicity of HTML back.
And that's where hypermedia-driven applications can help! Various communities noticed the madness of modern, overcomplicated, bloated SPAs - and they understood that "application/json" is not the only content-type that can be provided! Tools like Hotwire, LiveWire, LiveView, Datastar and finally - HTMX, can bring back the joy of building backends that serve as front-ends, but not in a clunky, "everytime-render-everything" way.
In this presentation you will learn the superpowers of hypermedia-driven apps, HTMX and what HATEOAS actually means. And why you can be true full-stack, again.

👨‍💻 BIO:
Engineer, currently doing web development. Functional programming and Machine Learning enthusiast. Baptized in control engineering.
https://talesfrom.dev/

───────────────────────────────────────

🎯 Presentation 2:
19:00 — Łukasz Jarmułowicz – Jak AI zmienia produkt (i zabiera pracę innym)

🧾 Description:
Przygody i doświadczenia z dodawania funkcjonalnosci AI do działającego produktu. Opowiem o tym jak dodawaliśmy kolejne funkcje AI do naszej platformy. Z jakimi wyzwaniami i problemami to się wiązało.
Oraz pokażę jak AI i produkty z AI zabierają pracę i będą ją zabierać innym produktom i usługom.

👨‍💻 BIO:
Programista z ponad 15 letnim doświadczeniem. Od 5 lat Head of Software Engineering w XtraMile. Odnoszącej sukcesy platformy do automatyzacji nauki w organizacjach.

───────────────────────────────────────

🎯 Presentation 3:
20:00 — Adam Furmanek – Basics Designs and How We Got Them Wrong

🧾 Description:
We want to write clean code and design software that can last years. However, even basic constructs of programming languages are broken. Strings, collections, async, private members, equality checks and many more – all these things are ill-designed and should be reworked. Do you know why and how?
In this talk, we’re going to revisit the basics of programming languages. We’ll see why our interfaces are wrong, why async shouldn’t use coroutines, why we shouldn’t encapsulate with private members, or why we should replace strings with something better. We’ll see the problems and then consider solutions that lead to better language design and better code quality.

👨‍💻 BIO:
Software Engineer interested in systems programming, .NET and JVM internals, big data and machine learning. Sometimes I have a piece of code which might be interesting so instead of putting it in the drawer I share it on this page. If you would like to argue with me just leave a comment or drop me an e-mail. You can find contact information here.