moonarchia
The Scientific Shitlord
- 29,346
- 56,999
IT/Software career thread: Invert binary trees for dollars.
- Thread starter Traak
- Start date
Noodleface
A Mod Real Quick
- 39,401
- 17,864
Have my EOY convo coming Monday. Expecting all good things from my boss but it made me question something in my head.
You guys that don't write much code anymore, how do you measure your productivity? I feel like quantifying what I do is impossible And it makes me wonder what others think of my output at work. Was going to raise the question to my boss in the EOY convo.
You guys that don't write much code anymore, how do you measure your productivity? I feel like quantifying what I do is impossible And it makes me wonder what others think of my output at work. Was going to raise the question to my boss in the EOY convo.
- 2
TJT
Mr. Poopybutthole
- 46,461
- 126,909
I write a fair amount of code still but a lot less than I did 5 years ago. Despite that, I still have tickets in my name which remain evidence of my productivity. I still own the features deployed and various projects. So yeah, its more subjective but if you don't even have tickets anymore like managers do its going to be more about selling what your team accomplished. Which remains evidenced in tickets and documentation.
- 2
- 3,080
- 5,019
I'd argue we still haven't figured that out, and probably never will. IBM had this metric with thousands of lines of (debugged) code:
It's obviously bullshit. Also, SCRUM story points are bullshit, too. There was also an idiot that measured productivity with ... VCS checkins. Of course every programmer in the building started to game the system, by checking in code with typos, and then fixing typos one by one in individual commits.
Tickets are also an iffy thing, because from "fix this typo" to "re-architect the entire application and database so we can extend it for this feature that a single user wanted" everything can be inbetween.
- 1
Noodleface
A Mod Real Quick
- 39,401
- 17,864
I have tons of tickets in my name but my management does not give a shit about that. I mean, my manager has told me how great I'm doing so I'm not worried... Just kind of a rhetorical question.
Most of the code I write now is fixing things with long debug sessions resulting in a single line change. Most of my time is spent designing, architecting, and leading a smaller team but I am still an IC.
Doesn't matter too much, I just care what my boss thinks.
On the lines of code thing Raytheon was the same. Their measurement was SLOC, source lines of code, or something. I always felt that was prioritizing the wrong things but that's a dinosaur defense company so par for the course.
Most of the code I write now is fixing things with long debug sessions resulting in a single line change. Most of my time is spent designing, architecting, and leading a smaller team but I am still an IC.
Doesn't matter too much, I just care what my boss thinks.
On the lines of code thing Raytheon was the same. Their measurement was SLOC, source lines of code, or something. I always felt that was prioritizing the wrong things but that's a dinosaur defense company so par for the course.
moonarchia
The Scientific Shitlord
- 29,346
- 56,999
As long as you have your accolades in writing you are good to go. Remember, you are the one keeping your thing going, right? And it is important to the business? And you are the only one who actually knows that thing?
- 17,630
- 8,650
Where/when do you guys decide it's time to cut and run on a feature? As in, it's not done right, but it works and you definitely don't have time to do it right.
I hacked together some ugly after_script so that our pipelines would be less gay. This was unprompted, no planning, and well received, including my boss. Then he sees how I did it, and now it's "gross" and I should have spent the extra tens of hours refactoring to do it right.
I'm not going to disagree that inserting [[ATTACHMENT]] links into xml with sed is...gross. But I feel like the context of serious refactoring and how far behind we are is being ignored. Was this my mistake for not getting the work properly planned? I'm at the point where almost nothing I do gets properly planned. Loose concepts get assigned even looser story points and I usually just git er dun. I would like better planning, but we're a small enough company where the many hats thing really interferes.
I hacked together some ugly after_script so that our pipelines would be less gay. This was unprompted, no planning, and well received, including my boss. Then he sees how I did it, and now it's "gross" and I should have spent the extra tens of hours refactoring to do it right.
I'm not going to disagree that inserting [[ATTACHMENT]] links into xml with sed is...gross. But I feel like the context of serious refactoring and how far behind we are is being ignored. Was this my mistake for not getting the work properly planned? I'm at the point where almost nothing I do gets properly planned. Loose concepts get assigned even looser story points and I usually just git er dun. I would like better planning, but we're a small enough company where the many hats thing really interferes.