A recurring respondents' theme is "TDD is irrelevant in front-end code". It's easy to offer/receive this comment combatively, but I think a little more rich discussion of the factors involved might bring us to new and different positions about UI and TDD.

Most folks who offer that are living in some sort of JS world: their code is client-side scripts attached to html pages to render various contents received from another application. Their browsers are in effect frameworks, inside of which all their code runs.

(Aside: One of the most prevalent trade problems caused by the explosive demand for software is the inexperience of your average geek on the street. It's easy to fall in to the "infinite now" and the "infinite here": assumptions that what one does now is what all do always.)

I want to step back from that JS world for a minute. Instead, I want to consider a bog-standard old-school single-computer single-program application, one that one user uses on one computer to perform multiple tasks, some of which are reasonably but not insanely complex.

Episode 37 is live! If you are interested in becoming a part of the conversation, Click here to join the Change-Harvesting Camerata Today!

---

If you have any feedback you can always tweet @GeePawHill on Twitter, or drop a voice message via the voice messages link here on Anchor. You can also read the full transcription of this podcast over on GeePawHill.org.

The Cost of Rework Avoidance Theory | #89

PawCast with GeePaw HillBy GeePaw HillSep 11, 2020