3 ms·
> The craft is not the code, but the product. These two are not disjoint, but instead quite related. > Your job is to deliver good product, not good code. If
by AdieuToLogic 3y ago
> The craft is not the code, but the product.
These two are not disjoint, but instead quite related.
> Your job is to deliver good product, not good code.
If your job is software engineering, then "good code" is what facilitates "good product." It boils down to maximizing the "abilities":
- Understandability
- Applicability
- Testability
- Maintainability
- Flexibility
- Durability
- m00x 3y agoYup, good code helps to deliver a good product, but you should not focus on the code, rather focus on how the code influences the product. Better to have hacky code that delivers value than to deliver nothing.
- AdieuToLogic 3y agoThis is a false dichotomy IMHO. "Hacky code" is most often a result of those responsible for delivery having gaps in their understanding of the product need. When engineers have a deep understanding of what is needed, there is rarely a need for hacks. Of course, the obvious exception to this is when libraries and/or external services mandate them.