3 ms·
>You can churn out way more features if you don't need to take quality into account. Creating quality code should not be at the expense of extra features. Just
by mojuba 7y ago
>You can churn out way more features if you don't need to take quality into account.
Creating quality code should not be at the expense of extra features. Just hire more competent, experienced engineers and there will be no need to sacrifice one for the other.
Quality is a function of experience and skill, it is not (or should not be) a function of development time.
- mobjack 7y agoThere are still tradeoffs to be made no matter your skill level. Good engineers choose between the minimal acceptable quality vs high quality code. Bad engineers struggle to get create minimal acceptable quality in the first place.
- koonsolo 7y agoI was talking about bug quality, not code quality. Sorry if that was not clear. And as any competent, experienced engineer knows, those two are less related than a junior would think. I agree you have to keep your code clean. But the absence of bugs is an entirely different thing.