2 ms·
This. Engineers are hired to solve problems. Sometimes beautiful code and clean architecture are part of the requirements to solve the problem at hand. Sometime
by baq 2y ago
This. Engineers are hired to solve problems. Sometimes beautiful code and clean architecture are part of the requirements to solve the problem at hand. Sometimes… they aren’t.
- debarshri 2y agoBeauty 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.