Writing about TDD because all my attempts to organise my life have shattered tonight

What a disaster. Rather than reading about TDD and cramming more information into my already overstuffed brain I am going to try to remember everything I know about TDD or test driven development

What do I know about TDD. I used to know stuff 

Okay bro okay bro

How many tests do you have to write for your work to be considered TDD. No it’s not a bad joke. It’s just a legit question

The answer is one. (Also I have to go in a second to make some tea for my flatmate). Not bad not bad okay so what else do I know about TDD. Bro nothing

OK so TDD is where you write your tests before you write your code? Right? Right? Because ONCE YOU KNOW THE DESIRED OUTCOME OF YOUR CODE

THEN YOU CAN WRITE TESTS FOR IT

AND ONCE YOU KNOW THE DESIRED OUTCOME OF YOUR CODE

THEN YOU CAN WRITE YOUR CODE TOO BRO

But isn’t TDD a better way to know what the desired outcome is of your code before you write it

If I ever doubted I was a software engineer 

I no longer doubt it any more

Because I would never write about this stuff if I didn’t care about it SO MUCH

Okay

Doesn’t forcing ourselves to write the tests first force us to clearly define our outcome

Okay I should read about this

But that would require me to be well behaved

Which I most definitely am not 

But wait I remembered one thing - my mentor (or one of 3-4-5-6 of them). Said that we would do TDD examples in our next weekly session

Bro I am scared 

But let’s goooooo

I am convinced that TDD might be an answer to all of my struggles 

And now tell me

Why am I thinking of mermaids 

But more importantly

What if working backwards were the solution