Developer productiveness is a type of matters that by no means goes away. How can we not solely make it simpler to ship code but in addition make that code extra dependable and resilient? As a outcome, we’re seeing one thing of a renaissance in developer instruments, from AI-based pair programming to low-level refactoring companies, and even higher methods of highlighting each syntax and errors earlier than we’ve even began to run a compiler or a debugger.
We’ve seen a whole lot of new instruments from advances in compilers and languages; .NET’s Roslyn compiler permits editors to look at what code will do, line by line, as you write it. At the identical time, it permits builders to edit code because it’s being debugged so you’ll be able to consider fixes or attempt novel approaches with out having to change context. It’s a extra environment friendly technique to work, utilizing debugging instruments concurrently an editor, so you’ll be able to see your code in a reside software when you’re writing it.
This is a wonderful means of working with enterprise logic, but it surely doesn’t work properly with a control-based structure device reminiscent of XAML. Here you’re working with interactions between code and structure, each working by means of totally different units of instruments in the identical IDE. With structure prerendered, you’re unable to make use of the default hot-reload instruments to alter design on the fly.