How My Wife Became a TDD Fan
My wife, Sasha is not (yet) IT person. Living with developer for 5 years, she knows only few details of developers job (like, they do code and sitting late nights to make it work). My bad, I never spent much time to explain what really my job is.
Recently she joined the training courses on software testing, to find the job in IT area in perspective.
After her second lesson she got back home and we had a talk about what she is actually studying there. It appeared they started with a software development processes, understanding how the software is actually created. So, they described waterfall (even if nobody using it any more) and some agile frameworks (scrum of cause), and left with a homework, to read what else practices exists.
- So, did you find anything interesting?
- I read about few, but I think I found the most interesting one..
- What’s that?
- Its called Extreme Programming..
- Hm, I never heard about it. Tell me more (trolls face on).
- Alright, so it’s a different practices as Code review, Pair programming, Collective code ownership.. But you know, what’s the greatest one?
- No, what’s that?
- Its called Test Driven Development, or TDD.
- What’s the point of this TDD? (troll face is still on).
- Can you imagine that you create the test before you create any application code, make sure it doesn’t work and after you fix it, so you always sure that application works fine! That’s sound so interesting and so valuable, I can’t wait to try it!
I had to put my troll face off, after that. I could not believe what I’m hearing. That was simply amazing!
- Do you know, I’m a big TDD fan and the training courses I do from time to time are “TDD in .NET”, so we teach people of using TDD practices in real projects.
- Fantastic, I never thought your job is so interesting!
The big disappointment to her was that testers are not doing TDD (she though it’s actually the testers job). Nethertheless, I got one interesting thought.
During the trainings on TDD we try hard to explain people the value of TDD and usually there some guys who just deny the idea, seeing absolutely no value in it. That actually show some human feature called “open mindness”.
As less you know, as easy to you to get new ideas.. As much you know, as less agile your brain could be, as hard you can adopt anything new.With more experience you got, it’s harder and harder to adopt new things. This is only the matter of discipline and hard working to stay update and actually try things out. It’s also a big patience till some tool or technique became beneficial to you.
The point of my story is. Developer have to be open minded person during whole career. Something you did yesterday, may became obsolete tomorrow. There are many things outside your comfort zone you might missing, staying in comfort zone for long time.
Back to Sasha, I always knew she is very bright lady. Now I hope she became bright engineer, good luck to you, honey.
My wife, Sasha is not (yet) IT person. Living with developer for 5 years, she knows only few details of developers job (like, they do code and sitting late nights to make it work). My bad, I never spent much time to explain what really my job is.
Recently she joined the training courses on software testing, to find the job in IT area in perspective.
After her second lesson she got back home and we had a talk about what she is actually studying there. It appeared they started with a software development processes, understanding how the software is actually created. So, they described waterfall (even if nobody using it any more) and some agile frameworks (scrum of cause), and left with a homework, to read what else practices exists.
- So, did you find anything interesting?
- I read about few, but I think I found the most interesting one..
- What’s that?
- Its called Extreme Programming..
- Hm, I never heard about it. Tell me more (trolls face on).
- Alright, so it’s a different practices as Code review, Pair programming, Collective code ownership.. But you know, what’s the greatest one?
- No, what’s that?
- Its called Test Driven Development, or TDD.
- What’s the point of this TDD? (troll face is still on).
- Can you imagine that you create the test before you create any application code, make sure it doesn’t work and after you fix it, so you always sure that application works fine! That’s sound so interesting and so valuable, I can’t wait to try it!
I had to put my troll face off, after that. I could not believe what I’m hearing. That was simply amazing!
- Do you know, I’m a big TDD fan and the training courses I do from time to time are “TDD in .NET”, so we teach people of using TDD practices in real projects.
- Fantastic, I never thought your job is so interesting!
The big disappointment to her was that testers are not doing TDD (she though it’s actually the testers job). Nethertheless, I got one interesting thought.
During the trainings on TDD we try hard to explain people the value of TDD and usually there some guys who just deny the idea, seeing absolutely no value in it. That actually show some human feature called “open mindness”.
As less you know, as easy to you to get new ideas.. As much you know, as less agile your brain could be, as hard you can adopt anything new.With more experience you got, it’s harder and harder to adopt new things. This is only the matter of discipline and hard working to stay update and actually try things out. It’s also a big patience till some tool or technique became beneficial to you.
The point of my story is. Developer have to be open minded person during whole career. Something you did yesterday, may became obsolete tomorrow. There are many things outside your comfort zone you might missing, staying in comfort zone for long time.
Back to Sasha, I always knew she is very bright lady. Now I hope she became bright engineer, good luck to you, honey.