← Back to context Comment by direwolf20 1 month ago Are we measuring productivity by lines of code again? This was treated as unserious for decades. 6 comments direwolf20 Reply kaydub 1 month ago Why ignore where I mention engineering impact??? Come on, be real here ozozozd 1 month ago What git stats do you have that show “impact”?The OP was right to assume it was lines of code. Another assumption could be number of commits, which also doesn’t measure impact. HDThoreaun 1 month ago Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews. matkoniecz 1 month ago Probably because you mentioned "git stats".What you meant by that? kaydub 1 month ago High number of days with commits, merging and shipping code consistently (some people/project will ship multiple times a day/week, some projects move a little slower).That plus the completion of high impact projects makes good strong engineers.Those are the people I see using LLMs 1 reply →
kaydub 1 month ago Why ignore where I mention engineering impact??? Come on, be real here ozozozd 1 month ago What git stats do you have that show “impact”?The OP was right to assume it was lines of code. Another assumption could be number of commits, which also doesn’t measure impact. HDThoreaun 1 month ago Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews. matkoniecz 1 month ago Probably because you mentioned "git stats".What you meant by that? kaydub 1 month ago High number of days with commits, merging and shipping code consistently (some people/project will ship multiple times a day/week, some projects move a little slower).That plus the completion of high impact projects makes good strong engineers.Those are the people I see using LLMs 1 reply →
ozozozd 1 month ago What git stats do you have that show “impact”?The OP was right to assume it was lines of code. Another assumption could be number of commits, which also doesn’t measure impact. HDThoreaun 1 month ago Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews.
HDThoreaun 1 month ago Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews.
matkoniecz 1 month ago Probably because you mentioned "git stats".What you meant by that? kaydub 1 month ago High number of days with commits, merging and shipping code consistently (some people/project will ship multiple times a day/week, some projects move a little slower).That plus the completion of high impact projects makes good strong engineers.Those are the people I see using LLMs 1 reply →
kaydub 1 month ago High number of days with commits, merging and shipping code consistently (some people/project will ship multiple times a day/week, some projects move a little slower).That plus the completion of high impact projects makes good strong engineers.Those are the people I see using LLMs 1 reply →
Why ignore where I mention engineering impact??? Come on, be real here
What git stats do you have that show “impact”?
The OP was right to assume it was lines of code. Another assumption could be number of commits, which also doesn’t measure impact.
Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews.
Probably because you mentioned "git stats".
What you meant by that?
High number of days with commits, merging and shipping code consistently (some people/project will ship multiple times a day/week, some projects move a little slower).
That plus the completion of high impact projects makes good strong engineers.
Those are the people I see using LLMs
1 reply →