BloggEd

Do you know the (oddly) funny feeling of having understood something, only to understand later that you didn’t understand it the last time, though some of the stuff you understood was correct, AND having felt that way many times about the same subject? No?

Well, it was all new to me before learning about BDD. First I learned TDD of course. Then I relearned that about 4 times before I think I finally understood it (of course I knew immediately that it isn’t about testing, duh). Still, TDD seemed to be full of superficial subtleties that were crucial when you dove deeper in the subject. And at first I didn’t even notice those subtleties like importance of mock objects. First it seemed like using those was optional and unrelated to the concept of TDD. Later I realized they were obligatory if you wanted to do TDD right.

Then I learned about BDD. First I thought it was just TDD done right with more suitable vocabulary to equip developer with proper mindset. Then I learned that I had still missed subtleties in TDD which applied to BDD as well. Of course, all this is also due to TDD/BDD being relatively new ideas, but still. It’s fun though, especially as the concepts are not really hard to grasp, far from rocket science.