3 ms·
Beauty is in the eye of the beholder. I would argue you didn't use design patterns enough. Beautiful code and clean architecture is a rabbit hole. Code should
by debarshri 2y ago
Beauty is in the eye of the beholder. I would argue you didn't use design patterns enough.
Beautiful code and clean architecture is a rabbit hole.
Code should be clean enough to communicate. As long as team understand and accepts the risk, it is good enough.
- baq 2y agoI equate design patterns with language deficiencies, so not sure what to answer. I know 'beautiful' won't be part of the response, though. Code is a liability, unless you're selling it. The less you have of it, the better off you are in the long run. That doesn't mean I don't agree that it should be clean, as an engineer. As a customer making a decision whether to buy a product or not, I couldn't care less. If you're hunting for product-market fit, you can do it with clean code, nothing is stopping you, except perhaps if there's enough runway to make paycheck.