Laws, JUnit, and Hamcrest

Came across a couple of different laws this week, 

The robustness principal / Postel's law, interesting idea on how it can be used within software construction although originally for use in networking. 

Be conservative in what you do, be liberal in what you accept from others (often reworded as "Be conservative in what you send, be liberal in what you accept").

Command query separation (CQS), the idea for what I write would be a function or method should return a value for query and for command which would change the system's state in some way should return void.

Installing JUnit for IntelliJ 14, although IntelliJ does come with JUnit installed and a test runner, JUnit has a dependency on Hamcrest. It was not entirely clear where what and how was going wrong, so...

1. Hamcrest at Google code.
2. IntelliJ -> File -> project structure
3. Modules -> Dependencies -> + icon top right
4. Point to hamcrest, YAY!

Book read this month, The software craftsman, has some good ideas, I did like the whole job searching and what to look for, generally that a dev would have written the job description and more concerned about what the dev can deliver. I often see degree only, 10 or more years experience.