4 ms·
A large percentage of the "very skilled" developers I know will much sooner brag about how much code they deleted or didn't write than how much code they wrote.
by klodolph 10y ago
A large percentage of the "very skilled" developers I know will much sooner brag about how much code they deleted or didn't write than how much code they wrote.
- agumonkey 10y agoThat is already well known quality[1]. I find Parent work even deeper, he pivoted the whole thing to make his main skill a second class citizen because that's what it was to be in this context. [1] I regularly nerdgasm at LibreOffice releases reading how many thousands LoC they removed from the code base. ps: beside code golf, I think there should be a patch golf thing. Try the smallest changeset that fixes or add a feature.
- Roboprog 10y agoI like the idea of "patch golf". If only people would at least do a diff before they commit to spot gratuitous reformatting or accidental changes :-(
- agumonkey 10y agoThat's the exact reason I thought of it [1]. With "large" code base, every character impacts the project, patch size becomes a skill. That said, it's so tempting to fix multiple almost related things in one go. [1] also, git surgically precise patch mindset helped too.
- Mc_Big_G 10y agoA very proud moment for me recently was when someone ran git stats and it showed I'd deleted more code than I'd written. It was glorious.
- nkassis 10y agoLazyness is a virtue for software engineers in my opinion.
- marktangotango 10y agoGenerally when I hear people talk about having imposter syndrome in software development, I feel like they're missing this key insight. The fastest code, and the easiest to maintain is the code that's never written. I've been trying to formulate how to express this idea to people who don't have it ie paraphrasing YAGNI: "Strive to optimize for less code, and the minimum level of abstraction."
- yclge 10y ago"Strive to optimize for less code, and the minimum level of abstraction." That should be the appropriate level of abstraction. The appropriate level of abstraction being that which requires the least code to implement and least effort to reason about.
- marktangotango 10y agoI think "appropriate" is highly subjective. The problem is developers seeking to impress their peers with over abstraction of trivial things. I personally think "minimal" is more "enforcable" ie easier to convey in a code review comment for example. Again, imo.