5 ms·

Having some ADD tendencies, I love TDD for helping me focus and get started—without it I just daydream about software rather than write the software. Once I get

Having some ADD tendencies, I love TDD for helping me focus and get started—without it I just daydream about software rather than write the software. Once I get going then I’m okay (though I still use TDD) but TDD and pair programming are both great for me, to get me started. I also have two young kids and can absolutely relate to the author.

tccole 4y ago
Yeah, I have diagnosed ADHD and I struggle staying focused and on task (and it occasionally gets me in trouble). But TDD gave me a framework to get things done and focused in a doable fashion.
- bcassedy 4y ago
  For me switching between code and tests is a context switch. TDD approaches that I'm familiar with encourage frequent swapping between them which really drains my productivity. It's much easier for me start something and hyperfocus than it is to swap back and forth.
  - antifa 4y ago
    > For me switching between code and tests is a context switch Not as big as the context switch that is between code and browsing the GUI of your app.
  - tccole 4y ago
    I think the true struggle of ADHD is that you’re in fact constantly context switching. There’s the great theory that being adhd is an evolutionary advantage because it made hunting easier.
7speter 4y ago
It seems quite overwhelming and daunting to me
- papito 4y ago
  I would say overwhelming and daunting is not knowing why your software becomes fragile and low quality without tests. TDD gives you a sense of control. You know that you are done once your tests (read: documented requirements) pass. And yes, I realize not doing TDD is not the same as not doing tests at all, but writing tests post-fact is just an excuse to wiggle out of writing them. "It worked when I coded it!"
- wpietri 4y ago
  I think it's harder to set up a project initially for it. And converting a brownfield project to tests is a bear. But once it's working, it's the opposite of overwhelming. The red-green-refactor cycle of TDD lets you take work in very small chunks. And because you get great test coverage as part of it, there are way fewer landmines. For me at least, TDD in a good code base is the most soothing and productive way to work I've found so far.
- Consultant32452 4y ago
  This is not intended to be snippy. What makes writing tests more overwhelming and daunting than writing any other form of code?
  - TylerE 4y ago
    It’s very difficult to know if it’s the test that’s wrong and not the logic.
    - randomdata 4y ago
      Tests merely document expected behaviour of your application. If you are unsure of what behaviour your application should exhibit, you need to step away from the code and talk to your customers for a while.
    - 7speter 4y ago
      This exactly
    - 4y ago

tccole 4y ago

Yeah, I have diagnosed ADHD and I struggle staying focused and on task (and it occasionally gets me in trouble). But TDD gave me a framework to get things done and focused in a doable fashion.

bcassedy 4y ago
For me switching between code and tests is a context switch. TDD approaches that I'm familiar with encourage frequent swapping between them which really drains my productivity. It's much easier for me start something and hyperfocus than it is to swap back and forth.
- antifa 4y ago
  > For me switching between code and tests is a context switch Not as big as the context switch that is between code and browsing the GUI of your app.
- tccole 4y ago
  I think the true struggle of ADHD is that you’re in fact constantly context switching. There’s the great theory that being adhd is an evolutionary advantage because it made hunting easier.

7speter 4y ago

It seems quite overwhelming and daunting to me

papito 4y ago
I would say overwhelming and daunting is not knowing why your software becomes fragile and low quality without tests. TDD gives you a sense of control. You know that you are done once your tests (read: documented requirements) pass. And yes, I realize not doing TDD is not the same as not doing tests at all, but writing tests post-fact is just an excuse to wiggle out of writing them. "It worked when I coded it!"
wpietri 4y ago
I think it's harder to set up a project initially for it. And converting a brownfield project to tests is a bear. But once it's working, it's the opposite of overwhelming. The red-green-refactor cycle of TDD lets you take work in very small chunks. And because you get great test coverage as part of it, there are way fewer landmines. For me at least, TDD in a good code base is the most soothing and productive way to work I've found so far.
Consultant32452 4y ago
This is not intended to be snippy. What makes writing tests more overwhelming and daunting than writing any other form of code?
- TylerE 4y ago
  It’s very difficult to know if it’s the test that’s wrong and not the logic.
  - randomdata 4y ago
    Tests merely document expected behaviour of your application. If you are unsure of what behaviour your application should exhibit, you need to step away from the code and talk to your customers for a while.
  - 7speter 4y ago
    This exactly
  - 4y ago