The developer then produces software features, documentation, deployments, and/or bug fixes on a recurring basis.
Hours and salary are visible, easily quantifiable inputs. A full-time developer works 40 hours per week for an average salary of $107,510 per year in the United States. In software development, as in any other field, many people think of productivity in terms of inputs and outputs. It’s also a source of anxiety for developers at all experience levels: how do you know if you’re doing enough, both on and off the clock? When everything you do is intangible, how should you measure it? Can it be measured at all? In this article I’ll discuss the biggest pitfalls of productivity measurement and a few ways to do it well. It’s the basis of enormous investment, the value proposition of numerous startups, and one of the most difficult parts of an engineering manager or CTO’s job description.
Defining and measuring programmer productivity is something of a great white whale in the software industry.
