Yesterday was my first day in #efcore team (moving from .NET performance). If #efcore 9 becomes awesome, you know why. If not, it wasn't me, I'm new here.
I'm going to start new IP address definition. I'll call it IPv46, it will be in between IPv4's address size and IPv6's. It will be, wait for it, 48 bit. No possible confusion whatsoever.
Nerve-racking ~24 hours. Setting up new storage array and because I don't have enough disks for completely safe execution, I'm taking one from the old array and putting it in new one. So old is not fully protected and new is building.
"We're pleased to share that you've secured a spot in the top 3% of most active speakers for 2023! It's a source of pride for us to have you as a speaker, and we truly value the insightful perspectives you contribute to conferences and events utilizing Sessionize. Cheers for being such a stellar speaker!"
If you were going to implement something similar to Azure DevOps’ streaming of pipeline execution logs (i.e. user instigated short term processes) so people could see log entries in realtime or look back at them historically, what would your #azure technology stack be to accomplish it?
There’s no need to aggregate logs from separate executions together (à la DataDog, Mezmo, etc). Each short term process will be viewed separately.
