As you may well know, a kata is a training exercise that is performed over and over to build muscle memory and generally improve at whatever it is that we’re practising. The term kata comes from martial arts, but us software guys/gals have started using the term to describe the solving of small problems repeatedly to get better at things like TDD and pairing.
Katas also have the added benefit of making non-geeks think we’re healthy individuals that don’t just sit in dark basements all day. In fact, we’ve started using the word dojo to make absolutely sure our new image sticks.
It’s a fresh September morning and I can’t quite believe it’s actually available – we’ve got a preview release of C# 6. Ever since the announcement at PDC2012 last month, I’ve been waiting to play around with a particular new feature. I remember it being a fairly average PDC until Anders shocked everyone with it – method group assignment.
Initially, I wondered what exactly it meant until someone on Twitter clarified it.
In the previous post in this series we saw how to render Spark views from handlers, looking at the use of view models and master page layouts. Finally, we took a more in-depth look at model binding support in Tinyweb.
In the final post, we’ll work through a to-do list demo which will pull together a number of the features already covered in the series into a complete application.
In the previous post in this series, we looked at Tinyweb’s support for dependency injection and saw how to use both handler and global filters to add processing steps to the execution pipeline.
In this post we’re going to see how to render views using the Spark view engine and take a closer look at how model binding works.
In the previous post in this series, we looked at how Tinyweb can be used to build HTTP APIs and examined each of the result types a handler may return.
The examples in the last post used made-up dependencies and you may have wondered how does the handler get these dependencies? In this post, we’ll look at how easy it is to have dependencies injected into handlers. We’ll also take a look at the use of filters to facilitate things like logging and error handling.
In the previous post in this series, I gave an introduction to the Tinyweb project and walked through a demonstration of how to get started.
We took a brief look at how handlers return content to the client, but in today’s post we’ll take a more in-depth look at how this works.
