Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
cursee2020970dQuality is subjective.
Usable. Bug free. Functional.
☝️ These words are more practical.
rytzpekt27369dIf the product lifecycle is very short then bad code, because I am not burdening myself or others with stuff that will become obsolete quickly.
Otherwise good quality, because of maintainance burden to me and others and the need for constant evolvability.
devTea2627169dCode Quality, I’ll even volunteer for overtime if I really like the project
Froot912169dCode quality is all fun and good but it accounts for nothing unless you get the product out the door. So it's a balancing act really
MacDev211869dI can see from all these comments that the question should be presented in a much more detailed sense, and all of you have your opinions about it. Currently I am doing this project on overtime since the project is really awesome because I would like to set a standard for whoever would be joining next in this project later.
rytzpekt27369d@MacDev with your effort you can set the standard for others. You can leave a lasting legacy. Continuation of your work with quality set by you is easier than doing something else.
Bad quality leads to more bad quality most of the time. Good quality leads to more good quality. Working against the trend is more effort, so we continue in the vein of our predecessors.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job