Writing code -- TDD style

Or should I say 'typing'?

"The best way that I know how to write code is to shape it from the beginning with tests."
~ Ron Jeffries

The quote was found on Scott Bellware's Webflog:
TDD, Java and the Microsoft Visual Developer

To paraphrase Scott,

"TDD is about coding. You can't drag and drop TDD. Code generation and TDD are largely at odds."

"Don’t think for an instant that the Java people are doing things differently from the .NET people because they face such different challenges. Nothing could be further from the truth. The Java people do things differently because they have a head start on .NET people.

Java developer culture is leading the .NET developer culture in terms of practice maturity. But, we're catching up. Well, in truth, we're catching on - our technologies will take us in subtly different directions, so we're never really gonna meet at the exact same place."

Hehe, don't blame me for plagiarism. I learnt this from my senior, Orangie. Anyhow I'm paraphrasing Scott on the aspect which resonates deeply with my brain. So much so that I'm still shaking of the effects of the reverbrations. ;-)

Assumptions in everything

Microsoft Takes it on the Chin Over Test-Driven Development

Very interesting entry from Scott Bellware, a MVP. It does provide insightful opinion as to how the mechanism of agility is to be implemented and the various flavours and dialects in which it arrives in.

A thought springs to mind; The path to knowledge is to question and find. However, how do we know to even question if there is no awareness of a topic at all? Coincidentally enough, a similar line of discussion was going on between me and my buddy very recently. It is about not showing someone information they are not ready to see. As quoted by Orange, "Never teach someone something they are not ready to accept"..... well, more or less la. Orange himself also cannot remember.