or subscribe with
Join 20,300+ readers for one email each week.
Digests » 217
The O'Reilly Velocity Conference will help you stay ahead of important trends in systems performance, cloud infrastructure, security, and more. You'll learn from experts and practitioners like Jaana Burcu Dogan (Google), Alice Goldfuss (GitHub), Stephanie Hurlburt (Binomial), and scores of others. Use code CDIG20 to save 20% on your Gold, Silver, or Bronze pass. That's a savings of up to $599 when you register during Early Price, now through August 17!
this week's favorite
The main issue with the use of mocks is that they encourage focusing on collaborations. That, in turn, often leads to coupling your tests to implementation details as those collaborations are usually not part of the SUT’s public API.
This C# tutorial describes approaches for making methods/functions more honest. A more honest method makes it easier for readers to understand what the method does by reading its signature, i.e., without reading its implementation.
You’ve implemented some of your performance critical code using the new platform intrinsics API. The code is now running 10x or even 100x faster than before, and you might think that it can’t get any faster. This post will show you some less obvious (but almost universally applicable) techniques for improving the performance even further.
Ever since I first heard about Span<T>, I’ve been wanting play around with using it. It’s a ref struct, so the semantics of using this type and the restrictions that go along with it are best understood by actually trying to use it. So I decided to build a simple CSV parser and see how the performance compared to other mainstream CSV parsers.
Jan 21, 2015 is one of the most important days in the C# modern history. On this day, the C# Gurus like Anders Hejlsberg and Mads Torgersen and others have discussed the future of C# and considered in which directions the language should be expanded.