DEV Community

Discussion on: Stop rewarding quantity!

Collapse
 
flodev profile image
Florian Klenk • Edited

Hi, thanks for making a point.
The same principle should be applied for delivering source code. The less code the better. Dev.to should actually be aware of it... but apparently that's not the case 😕
But to be fair quantity is much easier detectable than quality 😆

Collapse
 
ingosteinke profile image
Ingo Steinke • Edited

good point Florian! I heard that developers used to get paid by lines of code in early days of software development. Looking for a source, I found this (not finished reading though)

The oldest metric for software projects is that of “lines of code” (LOC). This metric was first introduced circa 1960 and was used for economic, productivity, and quality studies

ifpug.org/content/documents/Jones-...

Collapse
 
ingosteinke profile image
Ingo Steinke

and getting paid by hours spent in an office or in front of the monitor by default these days is only slightly better, at least it's no longer about output quantitaty

Thread Thread
 
flodev profile image
Florian Klenk

This is what I really hated in most companies. Being there just for being there 9 to 5. Everyone especially the management distrusts each other to just screw around when they have no tasks.
In my opinion tasks should be planned for a sprint and when the tasks are done it's done. Every employee can use the time that's left to learn but does not have to.
There has to be some slack so that employees can be creative.