Category Archives: Uncategorized

Testing WordPress

Call me confused… when I “View Site” from word press, I see the original movabletype blog.

In wordpress I see blog posts from may, june, july, october, october 2009.

I also see comments from WP posts. But now I cannot see those posts at all.

In movable type I see no posts between Feb 2009 and Feb 2010.


Something screwed up with web config on server?

Truth Hurts

Check this out…

A Better Team

and take the quiz!

My current team and I need to work to improve ourselves :-

But that was just my assessment… I’ll try to get the whole team to collaborate on the “team” answers and see how that compares.


An agile modeling poster:

How does agile prevent stovepipe systems and implementations. My inquisitor seems to think that agile development processes actually increase the incidence of stovepipe systems and thinking. (I’m paraphrasing here)

Agile is recursive.

Just as the power of components, objects, interfaces is applicable in the small or in the large…

The parallel being: the mere existence of the “tools” to avoid poor solutions doesn’t mean that poor solutions will not happen. We still have excellent code and poorly-written code.

The overarching agile requirement is to use good old-fashioned, smart thinking.

Agile neither precludes nor promises brilliant designs and abject failures. Only people can do that.

Apply the tenets of agile development recursively “upward” and you might be able to avoid stovepipe thinking.


Building an application is a lot like gardening, or better, farming.

Are you doing a quick app (maybe a flower pot), or a mission-critical app — where you need sustainable farming techniques?


Scott Ambler shared this link

agile schmagile…

The first slug of slides (which i have not gotten past yet) pointing out realities of some development efforts being lousy has nothing to do with agile and everything to do with people doing a lousy job at software development. News flash: anyone can screw up doing a project or misinterpret principles of development. Is that somehow the fault of the Agile Manifesto? I propose to consider it be the responsibility of the people involved…

If I get the stamina to respond I will, but here is just one stupid example: