5 ms·

That would still be 20-30k additional LOC per person year. Which is difficult to achieve especially in a corporate setting with a mature code base, without code

That would still be 20-30k additional LOC per person year. Which is difficult to achieve especially in a corporate setting with a mature code base, without code generation, lots of blank lines, or including static data. Even in startup environments it's hard to get 20k-30k a year for several years from the average unless many of the engineers don't overlap.

mrwh 4y ago
I don't know about that. 100 lines a day, 280-or-so days a year, is pretty doable for the average L4. You could do that in migrations alone, and people do.
- dchftcs 4y ago
  L5 or above there's normally a lot more communication and planning, which pulls down the mean significantly. In migrations you typically need to subtract some old code in the end, and it's not uncommon to result in net negative LOC (if the migration is ever complete). For L4 maybe there are more days where one can do several hundred LOC in an afternoon than L5, but there are also many days that result in 100 or less over an entire week, because there's testing, debugging, profiling and figuring out what to code. But, maybe I'd be wrong about Google. Afterall, it might be easier to dump lots of code into the codebase if there are 10 independent chat apps in development at any one time.
- xen0 4y ago
  Migrations tends to involve deleting lines too. A 200 line change typically doesn't grow the code base by 200 lines. I believe in my 2.5 years at Google, I've actually deleted more lines of code than I've added.
- deleted 4y ago
  [deleted]
- ahtihn 4y ago
  > 280-or-so days a year So working some week-ends and no vacations at all? There are about 260 week days in a year. Add bank holidays and vacations and you should ve closer to 230 working days in a year.
sudosysgen 4y ago
Probably half of that is config or autogen, perhaps even more, so it seems fairly reasonable?
- dchftcs 4y ago
  Yes but the point of contention was whether this can be done without code generation and static data. And probably both you and I agree it's quite difficult for a large organization to get 20k-30k net LOC additions per engineer without "conifg or autogen".

mrwh 4y ago

I don't know about that. 100 lines a day, 280-or-so days a year, is pretty doable for the average L4. You could do that in migrations alone, and people do.

dchftcs 4y ago
L5 or above there's normally a lot more communication and planning, which pulls down the mean significantly. In migrations you typically need to subtract some old code in the end, and it's not uncommon to result in net negative LOC (if the migration is ever complete). For L4 maybe there are more days where one can do several hundred LOC in an afternoon than L5, but there are also many days that result in 100 or less over an entire week, because there's testing, debugging, profiling and figuring out what to code. But, maybe I'd be wrong about Google. Afterall, it might be easier to dump lots of code into the codebase if there are 10 independent chat apps in development at any one time.
xen0 4y ago
Migrations tends to involve deleting lines too. A 200 line change typically doesn't grow the code base by 200 lines. I believe in my 2.5 years at Google, I've actually deleted more lines of code than I've added.
deleted 4y ago
[deleted]
ahtihn 4y ago
> 280-or-so days a year So working some week-ends and no vacations at all? There are about 260 week days in a year. Add bank holidays and vacations and you should ve closer to 230 working days in a year.

sudosysgen 4y ago

Probably half of that is config or autogen, perhaps even more, so it seems fairly reasonable?

dchftcs 4y ago
Yes but the point of contention was whether this can be done without code generation and static data. And probably both you and I agree it's quite difficult for a large organization to get 20k-30k net LOC additions per engineer without "conifg or autogen".