Nowadays, Test Driven Development (TDD) is so popular that software engineers are a group of people full of curiosity and spend a lot of time on learning and testing, like unit testing, integration testing and system testing. They design the test interface, brainstorm test cases, especially corner cases and abnormal cases.
However, sometimes the problem is difficult enough and we have limited time and budget, it almost has to use up all the resources (time, money, head count) to figure out a workable solution and make customers happy. Even though you might not be the owner of the project, you should have the ownership which will help you get it done and make it better, since the most significant things is keep shipping, delivering results.
Big companies and famous hackers advocate unit testing and code review, but I don’t think testing and code review are not important, actually they do play a significant role in software engineering. What I mean is tech giants and famous developers are not always right although they insist on the highest standards usually to earn trust, we should have backbone and make our own decision respective the specific situation, if we disagree with them and decide to come out a working solution first and commit wholly, concentrate on diving deep to the problem itself, thinking big, inventing and simplifying until find the final solution. Sometimes we have to take risks to implement without testing, reusable code and may not expandable for future, just like running naked, but I can tolerate bias for this kind of action and achieve more with less.
In a word, done is better than perfect, make it work first, do not over engineering and focus on future, reuse and test overwhelmingly.