Skip to main content

Your Conscience (Part-2) and Test-Driven-Development

... contd. from Part -1: Your Conscience is Your Compiler

Friend: Ok, got it. I used to think these are instincts.

Me: Well, you can hack it, i.e. ignore your conscience, but then you're corrupting your "code" and it affects your "program" behavior. And soon, you can't fix it anymore.

It's gone, unless you do major "refactoring".
Or a complete rewrite- which for humans is death and rebirth... and what does anyone know about death and beyond anyway?

In this life, you can only do refactoring, there's no rewrite.

Friend: Nice analogy. TDD!

Me: Well, TDD- Test-driven development is to ensure you are always following your conscience...But at the same time, allowing yourself the oppportunity to learn and the privilege to change your mind some day as you mature. TDD lets you easily incorporate lessons you learn as you grow and mature. It helps you change more easily than would be otherwise possible for you. It helps you easily figure out what went wrong- and how to fix it! And in fact, it would be so obvious and simple that even someone who doesn't know you much can help pinpoint it to you. I can go to a stranger and discuss some of these issues... and they'll say a thing or two that'll tell me immediately what I was thinking or doing wrong. It helps me change myself with objective criteria.

Friend: yeah

Me: TDD, my friend, is the best thing that happened to software since software was created...

Test-driven-development is turning the software "animal" into a software "human"!

TDD is the conscience of Software!


[Originally posted on my personal blog at muralikd.blogspot.com, September 27, 2010]

Comments

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint: Manage Unfinished Work - Split user stories ( new link ) Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):   This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying accept

Venture Quotes for a softening economy

Guess who said the following? "There's a lot of hot air and arrogance in the (VC) business that we all would be better off without" "...useless pontificating in front of entrepreneurs working harder than (VCs)..." "...VCs who constantly speak of deals and projects , reveal their self-interest and slight the labor and dreams of the entrepreneurs" If you think it's some disgruntled entrepreneurs who don't "get it", think again. In the past, I've made some pretty strong but heartfelt things, and I could have said the above, but I didn't . Read on here to learn who uttered these pearls of wisdom.

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is. Allow me to explain. The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with. Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria. Describing all the requirements as User Stories for a decent sized product is