Just wondering….

So I am busy pounding out the code for what I hope will be my successful startup,  TransparentPolitics. I have been avoiding writing any code that is paying attention to saving data.

To date this has been a big advantage. It has allowed me to move methods and member variables around with no effort, something that is not possible if I have to redo any sort of database layer or hibernate configuration file. As a result, it has allowed me to focus on getting the UI flow right without any distractions. Getting the UI right has been important for producing a series of progressively more capable demonstrations.
This has made for some very agile programming. One of my research projects will be to figure out how to maintain that same agility once the database layer is in place.
Building a migration strategy into the code from the beginning could have a number of advantages, but that will be for later!

I have been working on this for about 3 weeks scattered time with kids and other activities taking up time.

I am really appreciating more and more the XP methodology for building code. On an earlier version, I spent time with data models, hibernate, etc. first not the UI. This go-around I decided to follow the more XP model of doing things and build the demo UI first and then fill in the backend.

One positive thing so far is that it is easier to focus on what is most important — it is simply what is required for the next demo!

Feature complete list so far:

1. Basic Message display handling and insertion.
2. Basic MessageHandling code complete but test suite will need to be written next.
3. Primitive message entry (almost)

so I have this idea that is getting strong positive response amongst the people I ask. But how do I tell if these people are representative of a wider sea of customers or just the biggest fish in a very small pond?