The Apache Collections library is a great library for working with collections. However, the need to write verbose predicates that are sometimes difficult to read reduces the ease of use for that library.
Where a performance becomes automatic for the performer through practice, and where repeated performance has value, then there could well be a transition from amateur to professional for the performer.
One of the biggest challenges to efficiency for Android manufacturers is building, testing, and releasing machines for each version of Android OS, all while Android is constantly evolving under their feet.
One of the fundamental features of Apache Subversion is that it remembers every change committed to the central repository, allowing users to easily recover previous versions of their project.
If you are getting this error message when running the Windows App Certification Kit, don’t panic: This package was deployed for development or authoring mode. Uninstall the package and re-install it normally.
I’ve been experimenting with Gradle recently, and as part of the experiment, I wanted to get Sonar running and producing code metrics, including test coverage reports.
I had a hard time finding good articles about how to install icinga with the new web based PHP interface on Ubuntu 12.04.
Recently I finished reading a new book titled The Cucumber Book: Behaviour-Driven Development for Testers and Developers by Matt Wynne and Aslak Hellesoy. Aslak is the founder of the Cucumber project (which is what SpecFlow for .NET is based on), and Matt is one of its most active developers.
Resin's built in support is typically the fastest most scalable, most supportable option. To demonstrate this, let's show how we can use Resin built-in proxy cache (similar to Varnish or Squid) with Resin's REST admin support.
For those of us doing Java EE development with Maven (which by my own account as a former consultant is pretty much all Java EE/GlassFish adopters), getting our hands on the repository location for Java EE APIs is critically important.
Logging is an essential component of any system and helps you understand what's really going on in the system.
Having worked on a few data related applications over the last ten months or so Ashok and I were recently discussing some of the things that we’ve learnt.
By shifting mistakes in a system I can catch this exception -- but it means very bad code.
I thought I'd have a play with AWS's latest offering "OpsWorks" and see if they've done us all out of a job. Well, kinda.
When is our software neither over-encapsulated, with too many packages and classes, nor under-encapsulated, with too few? When is it just right?
The IT Ops team’s 4th sprint came to its conclusion recently… and we delivered all of our commitments! Huzzah!
About a month ago I had the good fortune of speaking at the London Web Performance meetup. This was one of the first talks I’ve done about our work at The Government Digital Service since the luanch of GOV.UK back in October.
In this ØREDEV session, Ryan McGeary explains how teams can improve communication (and results) through asynchronous collaboration.
Perhaps you’ve heard of “20% time.” In many ways, it or something like it are table stakes for many software folk, and perhaps other creative specialists as well.
Christine Day, the CEO of Lululemon, gave a compelling account at the Toronto Board of Trade of how Lululemon uses culture as a core competitive advantage.
In this ØREDEV session, Alan Parkinson discusses the unique benefits of testing in parallel.
In this ØREDEV session, Tim Berglund explains how to get started with distributed version control systems, and why it's changing the game.
LogStash fans (and fans-to-be) rejoice: James Turnbull's LogStash Book has been released into the wild.
Back in the days gone by, if you were part of the landed gentry, lording over your landholdings and the common folk who lived on said land, you’d look to becoming a patron of the arts as a way to ensure your name would live on after your death.
For four months during 2012 I was working on the GDS infrastructure team and one of the first tasks that Gareth suggested I do was update a diagram showing how all the different applications and databases worked together.