ChaosOne of the most popular reports people use to showcase failure of software development is the Standish’s chaos report. In 1994, Standish reported a shocking 16 percent project success rate, another 53 percent of the projects were challenged,and 31 percent failed outright.
This is what "software craftsmanship" gets us: an imposed segregation of those who "get it" from those who "don't" based on somebody's arbitrary criteria of what we should or shouldn't be doing. And if somebody doesn't use the "right" tools or code it in the "right" way, then bam! You clearly aren't a "craftsman".
Welcome back for episode 2! (Link to Part 1 included) It's time to implement our first real feature. And with that, comes a decision: what feature should we implement? Some map to fly around in? A way of keeping track of all the entities in the application? A game loop?
In this short video, Simon Maple and Andy Stanford-Clark show the new WebSphere Liberty Profile interfacing with Really Small Message Broker (RSMB) via an MQTT client (eclipse Paho). This results in MQ messages being sent to control devices 50 miles away on the Isle of Wight!
It’s time to look into the secret nuts and bolts of what actually makes retrospective meetings work. I’m stepping out to embrace a broader picture, as the subject of company culture — it’s exactly about the quality of this oil that makes the retrospective engines run — is limitless.
Most Java developers probably think of "contains" as describing if the String/Collection contains the provided characters/objects among other possible characters/objects. However, for Hamcrest matchers, "contains" has a much more specific meaning.
As I am always interested in testing RavenDB with different data sets, I decided that this would be a great opportunity to do that, and get some additional information about how things are working as well.