Andrei Karpov
@akarpov89
Developer on the JetBrains ReSharper Team | Husband | Father of Italian Greyhound Richie | Tweets about C# support | Opinions are my own
ID: 1892940943
22-09-2013 07:57:22
1,1K Tweet
531 Takipçi
203 Takip Edilen
To celebrate #20YearsOfReSharper, I need to highlight my greatest achievement at JetBrains. 10 years ago, I wrote a blog post about Clippy for ReSharper. The best bit was that it was a real plugin, and you lucky people, it's back for R# 2024.1 and above! blog.jetbrains.com/dotnet/2014/04…
ReSharper has turned 20! Dive deep into the evolution of ReSharper together with Andrei Karpov where he explores its new features and how it has become an indispensable tool for #dotnet developers. 👉 youtube.com/watch?v=tTyhU_… #JBDotNetDays #csharp
Wow! Thanks to Nick Chapsas's latest short about "The Most Cursed C# Library," I discovered that Anton Bergåker completed my old sketch of interpolated parsing as a NuGet package
Nick Chapsas My broader point is about a superficial style I see a lot online: tech reduced to random trivia. Too often we get a flashy fact, but no attempt to explain why it exists, when it’s useful, and what the tradeoffs are. Without context it teaches tricks, not understanding.
Migrating an entire legacy project to nullable reference types isn’t always realistic. Sometimes you just want all new files to start with `#nullable enable`. What if JetBrains ReSharper / JetBrains Rider offered a per-project or per-directory setting to enforce this?
