Wednesday, September 29, 2010

[TOOLS] Transparent development progress

One of the biggest movements in software development is that of transparency: telling all observers, especially stakeholders, exactly what the team is building right now.

For example, the Scrum development methodology suggests the use of a "burndown chart", a publicly visible graph that shows how much work is left to do in a sprint.

I found another cool example of this when following the Natural Selection 2 video game's blog. They released an alpha version of their game to people who have pre-ordered the game, and want to keep people updated on their progress towards completion and which features they're working on.

Through the use of Pivotal Tracker (I've never used the tool, so I can't say good or bad things about it) and a simple web page (actually the web page might be built through the tool) the company has created a great transparent window into their development process and increased the connection with their customers.


This is a huge step forward in communication with the customer. Anyone who has ever pre-ordered something still in development (a phone, some software, even startup capital in a new company) knows how frustrating it is to sink money into a black hole and not know what happens to it.

With a simple but effective interface like the one shown above, people can have faith that their money is actually being spent on real features and get a handle on the direction of the product. It also encourages new investment by displaying the progress of the team.

Tuesday, September 28, 2010

[TOOLS] Spring 3.0 - making life difficult

Just kidding. Kind of.

In Spring 3.0 they decided to break up the main spring.jar into a bunch of smaller jars. While I'm sure they had great reasons for doing so, it means that old examples are now broken since you have to figure out which jars they use.

Or, alternatively, you can just reference all of the jars. In Eclipse, create a new "User Library" called spring jars and just add all those spring jars into it. In whatever package needs spring, add your new user library to the build path.

Thursday, September 2, 2010

[TOOLS] Off-label use: ExtJS 2.3 with Managed IFrames

FYI:

The ExtJS extension "Managed IFrame" only lists support for ExtJS 1.1+, 2.0.X and 3.1.1+ only.

However, I can tell you from personal experience that the miframe_1_2_7 version (found here) definitely works with ExtJS 2.3.0. We use it at work in our widget system, and we found it to work perfectly.