MikeWitters.com
My $0.02 on stuff.
java
Unit Testing: The proving grounds for the team
May 8th
After weeks of development a change in a fundamental aspect of the domain has surfaced. To outsiders (read: the business) this change may seem insignificant, but to people who write lines of code, it is understandably a relatively big issue.
Value Objects vs Tool/Framework Bean Req’s
May 8th
A recurring scenario is annoying me. The scenario is this: Create a value object, in the Domain-Driven Design sense, and use it in a Hibernate persisted domain model. Following the DDD style, a value object shouldn’t have a default constructor, because its state should be present upon it’s creation as arguments to its constructor. It should be immutable and have no setters for its state. This won’t work if you’re using any tools/frameworks that require default constructors on the objects in your domain model. Read the rest of this entry »
I’ll be heading to Agile ITX this summer
May 1st
For a long time my career had me doing a whole lot of product installations and integrations where domain models and agile development didn’t necessarily fit. Any conferences or training I attended was based on specific product issues Read the rest of this entry »
Project Breakdown in [Eclipse] Workspaces
Mar 19th
Yesterday, I was doing some refactoring on some code in Rational Application Developer (a derivative of eclipse) and I ended up creating a couple of new projects to house some of it. When I told my colleague he’d need to synchronize with CVS and pull down the new projects he expressed some concern about why I had created the new projects. It made me revisit why I actually did it.
Read the rest of this entry »
Checking out the dynamic language scene (Briefly)
Mar 8th
Here in the midwest we were inundated with a massive snow storm this weekend. I took the time I was stuck inside to finally give Groovy (and Grails) a day long once over. Recently I have checked out Scala and JRuby. I have to say, I like them all at this point. I definitely haven’t spent enough time with any of them to endorse one over the other, but it is exciting to see that the JVM is being ‘extended’ beyond plain ol’ Java.
If I was pegged down and had to pick one considering the limited time I have spent with them , I’d say I’d go with Groovy. All other things being equal, I like its closure style and Grails simply rocks. All the playing I did was really simple, but I tried enough scenarios to determine it would be capable of handling some of the database and domain scenarios I would like to throw at it.
I’m definitely going to get more into these dynamic languages for the JVM.
