Don't Lose the Forest for the Trees

I think that's very equivalent in business software where you can lose sight of what are we actually trying to deliver to the customer. For me my approach to code is normally write something that works first and then go back and optimize it later on. And if I run into anything catastrophic along the way then that's assigned to go back and rewrite a couple of things or reorganize stuff there. But fortunately I don't have like a real go to answer of that in production that would be a little more terrifying.