Ask HN: I'm less productive with TDD. Am I doing it wrong?
Hi guys,
I've been programming for about four years now. I was taught on the job by a friend, and I've always learned to make one small piece before connecting everything
For example, if I need to make a simple 2D game, I put together the rendering function, then a separate function for handling key-events etc.
The gist is that I don't really have a blueprint on paper, it's all in my head, the blueprint comes together when I glue everything together.
I've been taking an introductory programming course and it's been asking me to jot out every function I need, all the variables, and write all the tests before hand before implement the actual code. I've been finding this challenging. I've not found a case where writing tests actually helped with writing the program. For me, it's been a hindering process. Am I doing something wrong here?
I've been programming for about four years now. I was taught on the job by a friend, and I've always learned to make one small piece before connecting everything
For example, if I need to make a simple 2D game, I put together the rendering function, then a separate function for handling key-events etc.
The gist is that I don't really have a blueprint on paper, it's all in my head, the blueprint comes together when I glue everything together.
I've been taking an introductory programming course and it's been asking me to jot out every function I need, all the variables, and write all the tests before hand before implement the actual code. I've been finding this challenging. I've not found a case where writing tests actually helped with writing the program. For me, it's been a hindering process. Am I doing something wrong here?