SpringOne 2GX – Final Day

SpringOne 2GX wrapped up yesterday, but I had to make a mad dash to the airport (only to sit and wait for the jet to have some mechanical work done) so I didn’t get to write my closing thoughts until today.

SpringOne 2GX – Day 3

It was another great full day of sessions at SpringOne 2GX in New Orleans. I attended 5 interesting sessions and got about as much technical info loaded into my brains as is reasonably expected in one day.

SpringOne 2GX – Day 2

Today was a great full day of sessions at SpringOne 2GX in New Orleans. I went to 5 sessions and had a great time at lunch and the evening reception meeting new people.

Messing with Selenium and Watir

Wow… long time since I posted. We have an application that is getting ready to go live for the customers of my customers and I wanted to do some load testing of the solution. The application was written by a contracting firm and was written using AJAX and RichFaces. The RichFaces and AJAX part adds complications to the conversation between client and server making it hard for tools to be used for automated activites. This posed a problem for me when I wanted to load test it.

Agile IT Experience… 5 closing thoughts.

I’ve been home from the Agile IT Experience for almost 24 hours now. I’ve had enough time to recover from the travel and lack of sleep. So, thinking back about the conference I have a few thoughts.

Unit Testing: The proving grounds for the team

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

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.

Value Objects vs Tool/Framework Bean Req's

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.

I’ll be heading to Agile ITX this summer

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

I'll be heading to Agile ITX this summer

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