I found that no single "pure" paradigm is a best response to development needs. By pure I mean pure OOP, FP, TDD, etc. Instead I am currently working on mixing

I found that no single "pure" paradigm is a best response to development needs. By pure I mean pure OOP, FP, TDD, etc. Instead I am currently working on mixing various paradigms together to achieve better result. Some examples: -- I use OOP to flesh out the domain model of my application, but use FP for most of the infrastructure and application around it. Some processes within OOP model are implemented using FP. I use OOP for its strength in bringing meaning and clarity to the most important part of the model. -- I use unit tests only for the important, non-trivial constraints on the tricky parts of the code. For the rest I prefer functional tests -- focusing on testing external application behavior lets me refactor the code easily without spending time on a huge mass of unit tests that need to be brought to shape after every refactoring. I still test the application -- the test suite ensures I will get notified if application misbehaves, but now it is not tied to actual internal implementation.