3 ms·
> The best code is the code you don't write. I envision your comment will be taken out of context to literally justify adding mountains of code written by othe
by austincheney 6y ago
> The best code is the code you don't write.
I envision your comment will be taken out of context to literally justify adding mountains of code written by other people. Invented Here Syndrome
- ChrisMarshallNY 6y ago:) Never even thought of that. Not necessarily a bad thing, if you are good at selecting dependencies. But it can be a very, very bad thing, if you are not so good at selecting dependencies.
- lucideer 6y agoI've seen both cases (people over-avoiding dependencies to detrimental levels, and people who are VERY bad, and very zealous, at selecting dependencies). While I think it varies per language community; overall, the latter seems more common. That said, the worst codebases I've worked with were examples of the former. So it's definitely a tricky balance.
- ChrisMarshallNY 6y agoMy codebases can be difficult to maintain (I know, because I'm the one that has to maintain most of them). It's not because the code is bad. Quite the opposite, really. It's well-structured, and incredibly well-documented. It's because I tend to do some fairly ambitious things, and write in a modular, layered fashion that can distribute functionality throughout the stack. I also tend to write in a fairly asynchronous fashion (would you call it "reactive"? I dunno. I've been writing code like that since long before "reactive" was an official buzzword). Can be hard to grok.