I sometimes like to examine the structure of a program without looking at the code, to see how well and how coherently it’s written.
Isn’t jbehave a well-structured little thing!
Looking at the package hierarchy root-downwards, it has an appealing bump, at the top of which sits those packages that we would have expected to be at the top: parser, lexer, and analysis, all deep in the hierarchy and far (we hope) from the pesterings of lower, larger-grained behaviours. There’s just something so satisfying about coming across a piece of code that seems well-designed.
It’s almost aestethic. Worthy of a tee-shirt.
Now all I have to do is find out what behaviour-driven development is all about …
I sometimes like to examine the structure of a program without looking at the code, to see how well and how coherently it’s written.
Isn’t jbehave a well-structured little thing!
Looking at the package hierarchy root-downwards, it has an appealing bump, at the top of which sits those packages that we would have expected to be at the top: parser, lexer, and analysis, all deep in the hierarchy and far (we hope) from the pesterings of lower, larger-grained behaviours. There’s just something so satisfying about coming across a piece of code that seems well-designed.
It’s almost aestethic. Worthy of a tee-shirt.
Now all I have to do is find out what behaviour-driven development is all about …
.ed