Comment by direwolf20 16 days ago Are we measuring productivity by lines of code again? This was treated as unserious for decades. 6 comments direwolf20 Reply kaydub 16 days ago Why ignore where I mention engineering impact??? Come on, be real here ozozozd 16 days 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 14 days ago Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews. matkoniecz 16 days ago Probably because you mentioned "git stats".What you meant by that? kaydub 16 days 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 16 days ago Why ignore where I mention engineering impact??? Come on, be real here ozozozd 16 days 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 14 days ago Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews. matkoniecz 16 days ago Probably because you mentioned "git stats".What you meant by that? kaydub 16 days 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 16 days 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 14 days ago Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews.
HDThoreaun 14 days ago Track engineering impact and git stats were two separate suggestions in that comment. Every org tracks impact through performance reviews.
matkoniecz 16 days ago Probably because you mentioned "git stats".What you meant by that? kaydub 16 days 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 16 days 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 →