🅰️ Michael Egger-Zikes 🇦🇹 🇪🇺 🇺🇦

@MikeZks

Trainer, Consultant & Speaker powered by ANGULARarchitects.io | Web enthusiast | Micro Frontend Architect | Software entrepreneur @intauria

Graz, Styria, Austria

ANGULARarchitects.io

Joined July 2020

2,177 Following

1,651 Followers

Replies Reposts Media

Pinned
🅰️ Michael Egger-Zikes 🇦🇹 🇪🇺 🇺🇦
@MikeZks
Dec 27, 2025
Always an absolute highlight being on the @ngPolandConf stage with all those brilliant guys from the @angular team. 👏
Dariusz Kalbarczyk
@ngKalbarczyk
Dec 27, 2025
🎥 Q&A Session With Google’s Angular Team – @ngPolandConf 🎤Panelists: Simona Cotin @simona_cotin Alex Rickabaugh @synalx Paweł Kozłowski @pkozlowski_os Jeremy Elbourn Jens Kühlers Matthieu Riegler @Jean__Meche 🎙️Moderated by: Michael Egger-Zikes @MikeZks youtu.be/OpprrzvyqEc
🅰️ Michael Egger-Zikes 🇦🇹 🇪🇺 🇺🇦
@MikeZks
Sep 18
Just gave a talk at #WTS2026 #AngularDay in #Skopje: From Probabilistic AI to Deterministic Applications – with Angular Signal Forms
1
🅰️ Michael Egger-Zikes 🇦🇹 🇪🇺 🇺🇦
@MikeZks
Jul 30
I am really proud, @UEFA - this was so important. ❤️💪
UEFA
@UEFA
Jul 30
Statement on behalf of UEFA and its 55 National Associations
🅰️ Michael Egger-Zikes 🇦🇹 🇪🇺 🇺🇦
@MikeZks
Jun 18
Great initiative by @GeromeDEV et al. 👇
Gerome Grignon 🅰️ @AngularDevsFr
@GeromeDEV
Jun 18
Replying to @GeromeDEV
That’s why a group of Angular community members and I have teamed up to create a new GitHub organization dedicated to collective open-source governance and long-term maintenance. The GitHub Organization, OpenNG Foundation, is still empty.
1
🅰️ Michael Egger-Zikes 🇦🇹 🇪🇺 🇺🇦
@MikeZks
May 14
This is a long awaited feature I and some of my customers use already for more than half a year. Also, @ngrx_io has opened an RFC recently. I called it delegated() #Signal. This way, we get two-way binding for unidirectional store implementations back. 💪 Same for the data
Mateusz Stefańczyk
@m_stefanczyk
May 14
linkedSignal with set() - what's the point? What are your use cases? Looking at the PR github.com/angular/angula… , the first thought is simple: why would I need this when I can just call update(...) directly on the source signal? And honestly, at first glance it looks like
2