I've posted a short (12 minute) video on SlideShare that shows how you can use DataClass to eliminate duplication between the documents you used to define your database and your .net database client. I intend to hit Java in the near future.
Here is a link to the video.
Stay tuned and be sure to sign up for the beta if you want to be a part of it.
Saturday, June 19, 2010
DataClass 1.0 Beta Program Open
The DataClass 1.0 Beta program is now open. DataClass is the next generation of DataConstructor technology. It is smaller, faster, and does a heck of a lot more.
If you are interested, the sign-up form can be found below. You will get a beta license to the product to be used over the course of the month of July. You will then get a survey to fill out in August. When you fill out the survey, you will get a complementary 1-seat license to DataClass as a thank you.
Click here to go to the beta sign-up page.
Monday, June 07, 2010
Two Customers
In response to http://whitewaterprojects.com/2010/06/04/who-is-your-cutomer/.
I respectfully disagree with the concept of a "technical customer" in addition to a "business customer." It may just be a semantics thing but I think it's important to keep the customer's place special.
The customer is the customer. For the team closest to the customer, that is not difficult to see. For teams "behind" the teams on the "surface" of an organization, it gets a little cloudier. I think it makes more sense to think of the intervening teams between yours and the customer as downstream work-cells. As such, they have the power to specify what an upstream work-cell builds in the moment.
The mental difference, however, is that they are not considered customers when your organization is working to optimize the whole.
Now, if there are two kinds of customer, I would say that there is a business customer and a process customer. That is, you can spend time delivering value to your actual customers, or you can spend time increasing your organizations capacity or lowering its cost.
The process customer is going to be interested in any project that eliminates waste. This might be traditional process projects like training in the latest methodology. This might be the acquisition of a tool. This might be something we don't think of as process but that plays heavily into it, like refactoring or covering legacy code it tests.
The business customer just wants what it wants.
I respectfully disagree with the concept of a "technical customer" in addition to a "business customer." It may just be a semantics thing but I think it's important to keep the customer's place special.
The customer is the customer. For the team closest to the customer, that is not difficult to see. For teams "behind" the teams on the "surface" of an organization, it gets a little cloudier. I think it makes more sense to think of the intervening teams between yours and the customer as downstream work-cells. As such, they have the power to specify what an upstream work-cell builds in the moment.
The mental difference, however, is that they are not considered customers when your organization is working to optimize the whole.
Now, if there are two kinds of customer, I would say that there is a business customer and a process customer. That is, you can spend time delivering value to your actual customers, or you can spend time increasing your organizations capacity or lowering its cost.
The process customer is going to be interested in any project that eliminates waste. This might be traditional process projects like training in the latest methodology. This might be the acquisition of a tool. This might be something we don't think of as process but that plays heavily into it, like refactoring or covering legacy code it tests.
The business customer just wants what it wants.
Friday, May 28, 2010
Oblivion for One
By Max Guernsey, III
Stop all the clocks?
Why bother?
This is the end...
...of life.
...of love.
...of joy.
...of pain.
...of experience.
At least, for one. At 2:30 pm, today, one of our cats, Seelie, died.
For those of us left here, we go on; some more affected than others. Yet, that's not really the point... is it? Mourning is an inherently selfish thing. We lament our loss; our pain; our experience; but those things all pale in comparison to what Seelie has lost: existence itself.
She is no more. To her, there is no more "to be." There is no more her for there to be no "to be" to. Nothing. No experience. No love. No joy or hate. The world does not exist.
So I say "Stop all the clocks? No need. Prevent the dog from barking with a juicy bone? No call."
For Seelie, the clocks have stopped and the dogs have stopped barking. From her perspective, those things all happened and more: The entire universe, including herself, ceased to exist the moment she died.
Who will be next?
By Max Guernsey, III
Stop all the clocks?
Why bother?
This is the end...
...of life.
...of love.
...of joy.
...of pain.
...of experience.
At least, for one. At 2:30 pm, today, one of our cats, Seelie, died.
For those of us left here, we go on; some more affected than others. Yet, that's not really the point... is it? Mourning is an inherently selfish thing. We lament our loss; our pain; our experience; but those things all pale in comparison to what Seelie has lost: existence itself.
She is no more. To her, there is no more "to be." There is no more her for there to be no "to be" to. Nothing. No experience. No love. No joy or hate. The world does not exist.
So I say "Stop all the clocks? No need. Prevent the dog from barking with a juicy bone? No call."
For Seelie, the clocks have stopped and the dogs have stopped barking. From her perspective, those things all happened and more: The entire universe, including herself, ceased to exist the moment she died.
Who will be next?
Friday, May 21, 2010
DataClass is almost here!
The new version of DataConstructor, DataClass, is almost ready for prime-time. I've got all of the critical v1.0 features ready for release and all I have left is the packaging and tutorials. I'm looking for beta testers so, if you are interested, let me know.
Each beta tester earns one Agile team a license to use v1.x of DataClass.
Each beta tester earns one Agile team a license to use v1.x of DataClass.
Subscribe to:
Posts (Atom)