sheetsj’s avatarsheetsj’s Twitter Archive—№ 4,903

          1. Good thread. I definitely fall into the gray area here... I love TDD when fixing bugs. Love how it validates the fix, and prevents future regressions. @GeePawHill/1556825728326553600
        1. …in reply to @sheetsj
          I'm test-after for new dev though. Need creative room to roam to achieve the goal, but always write tests before PR is ready. I treat new feature tests like my own personal PR review. And glad I do, because I nearly always find an edge case or bug somewhere off the critical path
      1. …in reply to @sheetsj
        I'm a believe in having code with a reasonably high degree of coverage. But I don't believe in metrics to enforce or even measure it. It's more of a feel and an art to me
    1. …in reply to @sheetsj
      *believe(r) ugh
  1. …in reply to @sheetsj
    And hey, nobody would enforce how many happy trees are in each Bob Ross painting. Can't really keep a metric on them because it could skew the resulting product.
    1. …in reply to @sheetsj
      We're drawn to languages and frameworks that have thought deeply about the unit test developer experience
      1. …in reply to @sheetsj
        spockframework.org/ and testing-library.com/ are so so good at DX
        1. …in reply to @sheetsj
          There's a scale of code maturity that I look for when evaluating any new-to-me legacy codebase... Are there good tests? are they easy to run? are they passing? does the team trust the results? You can learn so much from tests, and it doesn't matter if TDD was used