DEV Community

Discussion on: How Bad Software Gets Made

Collapse
 
jgranttuttle profile image
Grant Tuttle

This is a such a tough topic! I think you did a good job hitting the highlights, thanks for posting.

I want to throw my opinion out there and see what people think about it. I'm okay with sacrificing on code quality for the sake of speed if it means fulfilling some business need, AND there is a plan of action to rectify the technical debt. This becomes an issue when there isn't good project leadership on the product side or the development side. Trusting leadership is huge when it comes to this sort of approach.

Thoughts?

Collapse
 
aodev profile image
AoDev • Edited

I don't believe that quality must be sacrificed in order to gain speed. It's a lie to cover bad code that is produced by forever hacker type people. As senior developers, the experience, problems faced, tools, patterns and practice should have given all you need to code fast and with good quality as opposed to junior people. Lack of quality comes from lack of knowledge, more than lack of time. This can be applied to anything, not just code.

Collapse
 
jgranttuttle profile image
Grant Tuttle

"...the experience, problems faced, tools, patterns and practice should have given all you need to code fast..." is not true.