Idea: Innovation or absurdity regarding phoenix testing

[StefanHoutzager]

I feel like for my personality planning too hard is dangerous because I am not that smart and I often uncover fatal conceptual mistakes which require refactoring.

What I do when a piece of software is too complicated to write at once is as Lamport says:

There are two things I specify about programs: what they do and how they do it. Often, the hard part of writing a piece of code is figuring out what it should do. Once we understand that, coding is easy. Sometimes, the task to be performed requires a nontrivial algorithm. We should design the algorithm and ensure it is correct before coding it. A specification of the algorithm describes how the code works.

The whole text is a highly recommended read https://archive.li/2zZKy#selection-335.0-335.409
Testing follows after writing specs and code. That can be an IO.puts / console.log till an end to end test, whatever I think gives me the most return of investment. I never felt the need for a unit test suite with x percent coverage to get enough confidence (hence maybe Robert Virding’s renaming TDD to terror driven development Is TDD Dead? - #2 by rvirding).