Andrew E. Rhyne
Aug 28, 2017 · 1 min read

I’m not sure so much that’s “hard”, it’s more that most serious projects (with 30k+ LOC, 30+ developers, very complicated workflows, etc) are going to require something more than “pure functions” at the unit level. It’s easy to apply such constraints at early-stage startups building basic CRUD apps, but not for serious software projects where “one size fits all” programming approaches no longer work. The same goes for almost all backend development, where most of what you are doing is interacting with a database and avoiding process state. Most of your test value there is in integration land, not unit land, since your backend code is mostly just marshalling data to/from your database and likely also depending on logic that is applied from other services (microservices architecture). I don’t think the approach you are suggesting stands up to realistic demands in larger projects, especially on the backend.

)

    Andrew E. Rhyne

    Written by

    Founder & CEO @BoltSourceIO