I wrote a post for the LateRooms.com Engineering blog, focusing on using the Elasticsearch completion suggester to drive filtered autocomplete results.
Read it here .
These days, my default approach for writing tests is to construct the system under test using the builder pattern. Delegating construction of the SUT to a fluent builder has a number of benefits:
Done right, feature toggles are a powerful way of postponing the activation of features in a continuous delivery workflow.
Done wrong, though, they can be a burden, bringing unnecessary complexity, obscuring broken code and becoming difficult to remove when the time comes.
The difference between whether feature toggles are a help or a hindrance hinges on two key things: when you apply them and where in your codebase they’re managed.
There’s a little motif that I’ve seen dotted around async C# code. It seems to surface when developers find themselves needing to consume an asynchronous API without yet having fully grasped how async works.
The specifics differ, but the gist is always the same. There’s a service layer, which makes an async call to a third party with
I’ve recently started working with CouchDB and am finding it to be a really elegant way of storing and retrieving data. In my adventures around the Internet in search of related resources, I have found that - in spite of the maturity of CouchDB and similar document databases - there still seems to be a lot of confusion about reduce functions and, in particular, their mysterious
The documentation around reduce functions can be a bit obscure so, in this post, I’m going to talk through the process of building a CouchDB reduce function from the ground up. I’ll build a simple view to report on the numbers of books in a multilingual “digital library” application and then discuss the mysterious
parameter, what it is and its importance.
Blog content © Anthony Plant 2015. If you'd like to use any of the content you see here, please let me know .