3 ms·
My experience mirrors yours. I'd like to also stress that it's not just 30:1 ratios that are worthwhile. Most recently, I just rewrote a decently written ~8 kl
by brandonbloom 11y ago
My experience mirrors yours. I'd like to also stress that it's not just 30:1 ratios that are worthwhile.
Most recently, I just rewrote a decently written ~8 kloc C program in to a ~4 kloc Go program that does 5 times as much, 10 times faster. If I had more time, I could probably shrink the new Go program to about half its size. This new program includes the old, as well as a new simplified interface, both HTTP.
Moving clients to the new interface has had cascading C#/Scala code reduction of ~1 kloc each. This is the most important point! Simplicity breads more simplicity.
- grandalf 11y agoExactly. I have recently had a few cases where I've rewritten bloated overly-complex js into 10% to 20% of the LOC. The big benefit is the drastic complexity reduction. Suddenly the junior developers look like superstars because they can understand it and their productivity soars. I'm continually surprised at how otherwise smart engineers end up writing boated spaghetti that is 'correct' at the micro level but ridiculous at the macro level. A few poorly chosen abstractions can increase the cost of development by 10x easily.