3 ms·

I'd go further: - knowing how to make the solution "the right level of good", as opposed to "academically perfect" or "unmaintainable hack". - being able to d

I'd go further: - knowing how to make the solution "the right level of good", as opposed to "academically perfect" or "unmaintainable hack". - being able to design and implement a "good enough" solution that is still reasonably maintainable (if needed) much better and/or faster than others

huffmsa 7y ago
"Correct enough" is the phrase I usually use here. Knowing where on the scale to set that mark requires being able to bridge speed of implementation, execution, maintainable, upgradability and the overarching business goals you're building for. So really a broad range of understanding that only "excellent" senior developers will possess