I see a lot of projects where everything is just a vast context based decisions. If you factor out all of the things that are not related to databases or handli

I see a lot of projects where everything is just a vast context based decisions. If you factor out all of the things that are not related to databases or handling user input there's very little left. However I can imagine having that logic built up "abstractly" by imagining user input and database output objects and fully tested is something that would really help a project. Having only 20% code coverage or less is nothing to be ashamed of as long as that code is the code that matters and it's better, more abstract and more readable because you started writing it TDD. Before things got ugly with user input and database results.