3 ms·

Have you ever worked on projects (particularly java suffers from this) where there is generational bloat because most people have very narrow understanding of t

Have you ever worked on projects (particularly java suffers from this) where there is generational bloat because most people have very narrow understanding of the codebase so they can only add things and not remove/refactor without breaking it? That’s how

deleted 3y ago
[deleted]
CapsAdmin 3y ago
Usually if you peek at the first few commits it all seemed nice and clean. The turning point is usually as soon as the original author/'s leave and new people come in.
Cthulhu_ 3y ago
That's not likely to be the issue here tbh, or, that's focusing on low-hanging fruit. You get large codebases from having many features. No amount of coding and refactoring will bring a codebase's size down in a significant and measurable way unless features are ruthlessly removed.
- dilyevsky 3y ago
  I mean sure, I could understand Figma's frontend or something having millions of lines but what does linkedin frontend do that would reasonably require this?
  - crooked-v 3y ago
    My guess is that it's because there are 800 different versions of everything because none of the company's 13,000 UI/UX designers are willing to use the same component libraries.
    - superhuzza 3y ago
      Blaming 2,000,000 lines of code on UX designers, and not the developers, is certainly a new one.
- bluetomcat 3y ago
  These high-profile apps are elaborate spying devices. Besides the UI code, they probably have thousands of classes, some of which abandoned as dead code, with names like ProfileViewActivityLocationTracker...
realusername 3y ago
Orgs never value engineers that improve the overall codebase so I can't blame them. You're only getting promoted and compensated by delivering the next big feature which is part of the owners vision and being visible.
The_Colonel 3y ago
> particularly java suffers from this Correlation, not causation. Java is often used on large projects, it doesn't itself make things brittle. It's like the bomber survivorship fallacy - the fact you see such messed up projects mostly in Java is that they would not survive in languages like Python, where even a simple method rename can easily lead to big regressions.

deleted 3y ago

[deleted]

CapsAdmin 3y ago

Usually if you peek at the first few commits it all seemed nice and clean. The turning point is usually as soon as the original author/'s leave and new people come in.

Cthulhu_ 3y ago

That's not likely to be the issue here tbh, or, that's focusing on low-hanging fruit. You get large codebases from having many features. No amount of coding and refactoring will bring a codebase's size down in a significant and measurable way unless features are ruthlessly removed.

dilyevsky 3y ago
I mean sure, I could understand Figma's frontend or something having millions of lines but what does linkedin frontend do that would reasonably require this?
- crooked-v 3y ago
  My guess is that it's because there are 800 different versions of everything because none of the company's 13,000 UI/UX designers are willing to use the same component libraries.
  - superhuzza 3y ago
    Blaming 2,000,000 lines of code on UX designers, and not the developers, is certainly a new one.
bluetomcat 3y ago
These high-profile apps are elaborate spying devices. Besides the UI code, they probably have thousands of classes, some of which abandoned as dead code, with names like ProfileViewActivityLocationTracker...

realusername 3y ago

Orgs never value engineers that improve the overall codebase so I can't blame them. You're only getting promoted and compensated by delivering the next big feature which is part of the owners vision and being visible.

The_Colonel 3y ago

> particularly java suffers from this Correlation, not causation. Java is often used on large projects, it doesn't itself make things brittle. It's like the bomber survivorship fallacy - the fact you see such messed up projects mostly in Java is that they would not survive in languages like Python, where even a simple method rename can easily lead to big regressions.