Lets Stop Making Acronyms and Just Do It!

So, while scanning through my Google Reader this morning, I came across a post which mentioned TSD. Which is a new one to me..

“What the heck is TSD” I thought.. Turns out it is Test Supported Development. The idea of the post is that they were arguing that TSD is not TDD (Test Driven Development).

OK geek boys and girls, I have a crazy idea. How about we stop coming up with silly new names for slightly different approaches?

I think TDD and BDD (Behaviour Driven Development) have their place. They are both essentially the same, but BDD comes at it from a different angle in an attempt to shift the focus from testing to understand the required behaviour.

But a new acronym called "TSD”? WTF?

Now, I am currently working on a project that has no unit tests at all. Yup, zero. I hate it. But would I say “I’m not using TSD”? No, I would say “this project sucks as it has no unit tests”.

“TSD” should not be a “style”. Everyone should be doing it anyway. To me there is no such thing as “test supported development” as a methodology, ALL development should be test-supported!! You don’t say “I am surfing the web OHP” (over HTTP protocol) – How else would you surf the web?

So, can we please stop trying to come up with new fandangled buzzwords and acronyms to try and sound cool, especially when it is only describing something that should be a standard.

Now, I am going to go about my EFL (energy-fueled life).

Comments

  1. Anonymous6 February 2009 at 00:14

    LOL.

    Easy dude. I'm thinking the person who wrote that probably just wanted yet-another-abstraction-layer for whatever practices whe wanted to describe.

    Of course I get your point that we don't need no stinking new abstraction layers.

    ReplyDelete
  2. Unknown6 February 2009 at 01:11

    Actually a NUT project has a certain ring to it. (NUT = No Unit Tests).

    ReplyDelete

Post a Comment

Popular posts from this blog

GTD: Biphasic Sleep Experiment – Day 4

Physical State/Tiredness Same as yesterday really, awoke feeling really fresh and alert first thing in the morning. I again took a nap at work at 1230-1300. There has been a fair bit of interest about the napping at work so I thought I would take a minute to talk about it here (see below). Other than that, I did awake from my afternoon nap rather tired and groggy (took me 15-20 mins to get head together) but I actually think this is related to food since I ate a rather large pizza before sleeping.. :\ I have also found that even though it is great having the brain running longer, it can equally be hard to shut off. I have started going to bed with a book at 0200 so I can start to wind down to sleep mode for 0300. Staying up to 0300 is NOT a good idea, you really need to be going to sleep “ FOR 0300 ” not “ AT 0300 ”. Napping at Work Here’s what I do: At about 1200, I do a quick scoot around the team to see if there is anything they need from me, I then tie off any loose end...
Read more

Visual Studio: Unknown Build Error (HRESULT 0x80131515)

Image
If you are receiving this really informative error message in Visual Studio and looking for a solution, I hope the following can help you. I spent wasted a fair bit of time trying to figure this out. Funny thing is, it’s actually quite common in the post-XP(i.e. Vista and Windows 7) era (I’ve had it myself several times now).. The Cause After much digging, it turns out the issue is caused by the file blocking placed on downloaded assemblies. For example, I had the following after downloading the binaries for Autofac and adding it to my project: Error    1    Unknown build error, 'Could not load file or assembly 'file:///c:\{Project}\lib\Autofac.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)'     {Project} To Fix The good news, is this is pretty easy to fix (as are most problems when you know the cause!). Open up the file properties dialog (right click in Explorer ...
Read more

TDD – Getting Started with Test-Driven Development

I have been expressing interest in getting up and running with TDD for quite some time, probably the best part of nearly two years in fact! (wow). I have always struggled to get going though. In my previous job I was pretty much flying solo, and even though I am in a 6-man team in my new job, we still are pretty isolated (not my choice!). Every time I have gone to the programming community and asked “how do I get started?” I pretty much got the same response wherever I went - “Just do it”. This was real frustrating because it can be so overwhelming, if you don’t know where to start, how can you start? So I started to dig deeper for as many TDD/Automated Testing sites as I could, even if it was pages and pages of stuff that I didn’t want to know, if I got one little snippet of something useful, I would be happy. I came across some great sites (links will follow). Some were very, very simple. Almost so simple that they don’t really cover the testing, they cov...
Read more