Paul Geffen

This is a very valuable way to think about process...

2010-02-02T15:19:17.203-08:00

This is a very valuable way to think about process that would greatly enhance the productivity of an organization. Rather than fumble and experience growing pains, growth can be smooth and much less frustrating. An interesting application that is well thought out, cogently expressed, and very useful.

Tom, software is probably the most popular form of...

2010-02-01T19:26:18.877-08:00

Tom, software is probably the most popular form of engineering these days but it's really not so different from any other kind of science. There are ways to work systematically from ideas to results and these methods apply in many fields.

I am glad to know that you find this useful - and I will continue to share what I know.

The software conversation you are sharing here is ...

2010-02-01T18:23:45.748-08:00

The software conversation you are sharing here is showing why what people can do with it is still very valuable in this economy. I talk to friends that develop gov., security and engineering softwares that are having record years.... but unlike other business there is a barrier to entry of being brilliant.

The only way that I am able to figure things out like this is to know people that know it and trust them as friends to give me the straight answers on how things really work in the world of software. You are building an incredbile base of information that really shows you know what you are talking about.

"The effect on test was simply that no unit test was needed for this part of the implementation. It either worked or it didn't."

This reminds me of biotech molecular studies they either work or they do not and the situation for moving forward becomes... what is the word? Binary?

The work that you are sharing seems to be workable for a variety of different businesses because what it really comes down to in my opinion is trusting your systems.

I think you will do great by blogging about this because it really then falls into the grouping of

"do things that others are unwilling to do"

You have some of the best stuff I have seen on software.

Thank you for sharing these concepts.

A client asked if I had a sample of a “requirement...

2010-02-01T17:22:24.809-08:00

A client asked if I had a sample of a “requirements map” that I could share, or something else that would help her to think through that phase.

Here is what I wrote:

There are many ways to draw the map. Requirements are typically written as English text in a document. Outline form can be helpful. If you want to go all the way to a "mind map" that's fine too. There are no rules for the form. It all depends on how you can best express yourself clearly and completely.

The key is to include everything you want to consider - not all the details but a complete overview - so that your developer can start to imagine the structure of the project. The worst thing you can do is give it to him piecemeal. Filling in details later is much better. Whatever you can do to get the highest level view, however approximate, will be your best method. Start with the outline and don't worry about the amount of detail. Fill it in as you need to and as long as you don't change the overall plan you will have a happy developer.

I am amazed that someone is reading while I write!...

2010-01-24T06:54:38.288-08:00

I am amazed that someone is reading while I write! Are we on Google Wave?

You have a great blog keep it up. I enjoyed readi...

2010-01-24T06:52:59.585-08:00

You have a great blog keep it up. I enjoyed reading your archives too it is clear you understand technology at a deep level.

Kindest regards,
Tom Bailey