528
Uncle Bob becoming even worse: (lemmy.world)
submitted 4 days ago by to c/programmer_humor@programming.dev
226 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 3 days ago (1 child)

Except that then you'll shape your interfaces to drive tests nicely, instead of being, you know, sane and useful (been there, done that).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 days ago (1 child)

    Unit tested test for accuracy, if your code isn't "shaped to drive tests nicely", it's bad code.

    They enforce requirements. You do start with code, you start with the "shape", you architect how your application should be developed and you write unit tests for the functions you already know you want but haven't written the logic to yet, the unit test validates the logic so you don't spend 2 hours hunting down a missing negative sign.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 days ago* (1 child)

    Read my comment again, instead of half way through.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 day ago

    I did, and I responded to your comment in its entirety. If there's a point you made that I missed, try rephrasing it instead of being snarky...

    Unit tests tests known facts and validate requirements, good unit tests are defined after you define your requirements and as you design your infrastructure, not after you write your code. They ensure your code does what you require it to do.

    I don't know what part of your comment I missed reading...

  • permalink
  • fedilink
  • source
  • parent