5 ms·
Was the 3M LOC refactoring for yelp.com? The article doesn't say. How could possibly a review site have 3M LOC?
by spapas82 10y ago
Was the 3M LOC refactoring for yelp.com? The article doesn't say. How could possibly a review site have 3M LOC?
- raverbashing 10y agoThe front-facing system is the smallest part The admin and back-office system is deeper. Beyond the reviews you also have: events, mailing list management, profile management, messages, i18n, search, etc Example: http://engineeringblog.yelp.com/2015/10/how-we-use-deep-learning-to-classify-business-photos-at-yelp.html http://engineeringblog.yelp.com/2015/10/how-we-use-deep-lear... Edit: still, 3Mi lines is massive. However, I think there's something that contributes significantly: HTML and CSS
- spapas82 10y agoHmm, well even with all those, the amount of code just blows my mind!
- qznc 10y agoOnce I was talking to someone from SAP. He told me about their Netweaver framework is 1 billion LOC and 40k SQL tables. That does not include any application, yet. The biggest reason for the bloat: People are not allowed to change code. You only add code. Now try to add a button to some GUI without changing a single line of the existing code. At this moment I understood, why enterprises produce those overengineered AdapterFactorySingletonDecoratorBridge stuff.
- throwaway_exer 10y agoi18n generally just adds property files and maybe localized CSS, not code.
- kasparsklavins 10y agoReminds me of Ubisoft claims that its Assassin's Creed crouching mechanic had 6M LOC
- unabst 10y agoIf you pay coders to code, they will give you code, and if you track performance based on their output, the code remains to justify their cost. And it's just hard to delete good work. So everything grows in businesses that hire tons of (good) coders. Pay them to refactor it and they'll do that too :)