I’ve seen a couple of projects in the last few months that have needed
to cache data between requests. The developers, not wanting to write
their own caching module, decided that Apache Commons JCS fitted the bill and added it to their Maven POM using the...
This is an, let's call it accidental post. I was looking into
transactional CDI observers and playing around with GlassFish embedded
to run some integration tests against it. But surprisingly this did not
work too well and I am still figuring out, where...
“Are you pair programming?”
our manager asked in his snarky tone, while using exaggerated double
air quotes to emphasize his skepticism. He then walked away without
waiting for a response…
This is merely one example of numerous instances I’ve...
As discriminatory as this is going to sound, this one is for the
old-timers. If you started programming after the turn of the milennium, I
don’t know if you’re going to be able to follow the trend of this
post—not out of any serious deficiency on...
Last week saw the announcement
of Amazon Web Services NoSQL database as a service, Dynamo. Dynamo has a
number of very interesting features, not least that it runs as a
managed service with certain guarantees with regards to scalability,
Given that @patrickdebois is working on
improving data collection I thought it would be a good idea to describe
the setup I currently have hacked together.
(Something which can be used as a starting point to improve stuff, and I have to write documentation...
Tests developed during TDD can be classified into several levels, depending on the size of the object graph they need to work with. End-to-end tests span the whole application graph, while unit tests usually target a single public class at a time.
I blogged on Event Sourcing
and functional domain models earlier. In this post I would like to
share more of my thoughts on the same subject and how with a higher
level of abstraction you can make your domain aggregate boundary more
I recently came across Carl Erickson’s ‘small teams are dramatically more efficient than large teams‘ blog post which reminded me of something which my colleague Ashok suggested as a useful way for determining team size – the application footprint.