Weekly development links #10
Feature Rich debugging experience. Still in Beta but could be an extension worth watching. Good visualisations of your code values during debugging.
Features such as Magic Glance, Predict the Future, Predicting Exceptions, Search, Compare and more..
Export whole objects with values from the debugger to code. Useful for creating Testing Mother Objects or viewing your object populated. Exports to XML, JSON or C#
I try not to be prideful, as a rule, but darnit, I'm REALLY proud of my podcast. As of this writing I've done 526 episodes. Each one 30 minutes long. Every Thursday, for the last decade. That's over 250 hours of technology talk that promises not to waste your time.
At the Build 2016 Future of C# presentation Dustin Campbell and Mads Torgersen from Microsoft discussed a number of features planned for C#7. Before we begin it is important to note that all the features I will discuss are subject to change both in terms of syntax and indeed whether they make the cut for the final version so don’t be too surprised if there are a few changes still to come!
A CQRS architecture can be seen as a set of referentially transparent functions that model decisions and interpretation.
Time is Money. Understanding application responsiveness and latency is critical but good characterization of bad data is useless. Gil Tene discusses some common pitfalls encountered in measuring latency and response time behavior. He introduces how simple, open sourced tools can be used to improve and gain higher confidence in both latency measurement and reporting.
In 1964 Abraham Kaplan said: “Give a small boy a hammer, and he will find that everything he encounters needs pounding". Another famous version of this is known as Maslow’s hammer, and it goes like this: “if all you have is a hammer, everything looks like a nail".
Let's cut to the chase: you're adopting a microservice architecture and you're planning to use Docker. There's a reason it is so en vogue – it solves lots and lots of problems and has zero negative effect on our projects, right? Right? As with every tool, technology, or paradigm that is thrust upon us as we scrappily try to maintain our sanity while jumping from shiny to shiny; we need to learn the gotchas.