Almost always a small fraction of the code that I read in the process of finding out how exactly to add an enhancement to existing code. Read, think how the pro

Almost always a small fraction of the code that I read in the process of finding out how exactly to add an enhancement to existing code. Read, think how the problem fits in, read more, maybe code some little experiments to see how part of the problem will be interfaced, read more, etc. More skimming than perusing, if it's part of the codebase that you're familiar with. Number of issues closed: Depends on what I'm doing. Short little maintenance things can take less time, and you can clear a bunch in a day. Some individual features will take weeks or months to code, depending on how deeply new changes need to infiltrate into old code, the size of the change, how much work you depend on other teams to do to provide ancillary features to support your work, etc. My team's more of a "fulfill the requirements; do it right" than a "move fast and break things", because our products are backup applications. I suspect that this changes the tempo of the work, compared to how other teams might function.