Sergiy Teplyakov 🇺🇦 🇺🇸
@STeplyakov
Principal Software Engineer at Azure Physical Networking. Ukraine → US
Hey #dotnet people! Exciting news! I've launched my YouTube channel: "Dissecting the Code". It's going to be very similar to my blog, where I'll cover .NET internals, performance tips & tricks, and more deep dives. #csharp I've already published the first two videos: ➡️ Episode…
Hey #dotnet folks! Please share latest deep-dive video to spread the knowledge about async internals and tips&tricks on debugging .NET code! Your support means the world! /cc: @migueldeicaza, @jaredpar, @dotnet, @davidfowl, @davidpine7 and every other member of .net community!
Async/await in C# can feel tricky, but it’s simple when you step through it! In my latest video, I debug async methods line-by-line to show exactly how async/await works under the hood. Watch now at: youtu.be/oHKyzgGjKHQ?si…
Async/await in C# can feel tricky, but it’s simple when you step through it! In my latest video, I debug async methods line-by-line to show exactly how async/await works under the hood. Watch now at: youtu.be/oHKyzgGjKHQ?si…
An absolutely fantastic talk by @KentBeck on software design. If you ever want to understand what coupling and cohesion is, just watch this talk. And it’s funny, and easy to watch, super enjoyable and gives one of the best definitions of coupling/cohesion I’ve ever seen! (yep,…
Hey #dotnet community! Please share and let's simplify the way we deal with resources in .NET! @davidfowl, @dotnet, @jaredpar, @migueldeicaza and other folks, I love to discuss this topic! You might disagree with my take! But its time to reconsider some old patterns.
Posted another episode on YouTube: "The way Dispose Pattern Should Be Implemented". It’s time to reconsider the Dispose Pattern and abandon Dispose(bool disposing) nonsense. Let’s move to a simpler approach and never mix managed and native resources. youtu.be/E6tQDczhrUM?si…
Posted another episode on YouTube: "The way Dispose Pattern Should Be Implemented". It’s time to reconsider the Dispose Pattern and abandon Dispose(bool disposing) nonsense. Let’s move to a simpler approach and never mix managed and native resources. youtu.be/E6tQDczhrUM?si…
Just published a new issues of .NET R&D Digest! Thanks to @unmeshjoshi, @martinfowler, @andrewlocknet, @meziantou, @DamianEdwards, @STeplyakov and other great authors for their amazing content! olegkarasik.wordpress.com/2025/07/04/net… #dotnet
From the amazing author of PolySharp. In a beer future the InernalsVisibleTo workaround won’t be needed! Nice!
Thank you for the shout-out for PolySharp! Also, about that issue with internals visible to, I'm working on a fix for that to avoid those conflicts entirely, by marking the generated types as embedded instead. PR is here: github.com/Sergio0694/Pol…. Will be in the next release 🙂
Hey @davidfowl, @dotnet, @VisualStudio, @jaredpar, and other #dotnet community members. Could you share this tweet about how to unlock most of the C# productivity features even targeting .NET Framework or .netstandard2.0. Let's spread the word to a wider community!
Posted another episode on YouTube: "Unlocking Modern C# Features Targeting .NET Framework". Quite a few devs limit themselves with C# 7.3 when they target full framework or .netstandard2.0. You still can leverage most of the latest C# features in this case. This video shows…
Posted another episode on YouTube: "Unlocking Modern C# Features Targeting .NET Framework". Quite a few devs limit themselves with C# 7.3 when they target full framework or .netstandard2.0. You still can leverage most of the latest C# features in this case. This video shows…
We've added a browser to GitHub Copilot coding agent. It can now: - Run and navigate your web apps. - Post screenshots of changes it's made. github.blog/changelog/2025…
The C# team is considering "closed enums, closed hierarchies, case classes, and nominal union types." github.com/dotnet/csharpl…
Personal / professional life update: I'm one of the lucky thousands to be made redundant from MSFT last month (due to UK redundancy laws, I'm actually still there for now) Next up: I'm joining the good folks at Redis, as part of the client library team. So: fun times ahead!