4 ms·
The problem with most great projects written by small group of brilliant people in any language: - it introduces its own vocabulary, it looks like gibberish u
by DmitryOlshansky 7y ago
The problem with most great projects written by small group of brilliant people in any language:
- it introduces its own vocabulary, it looks like gibberish until you build up the context
- since the group is small and gifted they have no problem creating and using the power tools of their own
- there is no documentation so your only way is through experimentation and direct communication
- the folks who have built it had to move on to solve another (bigger) problem, leaving no traces of what the vocabulary is, where the design was headed, what should be changed with the new requirements and again next to zero documentation
- hinkley 7y agoCircular reasoning is hard to manage out of a project. Circular reasoning that has never been articulated is much worse. Some of the best ergonomic improvements to my own code have come from trying to explain why my code is so stupid and figuring out that there is a fix that’s easier than this apology. When it’s three people there are no apologies even offered, and almost no feedback.
- amboo7 7y ago3. You can actually try and understand most of what's been written through reading, given that you're allowed the time for that. It's an investment, prevents technical debt and promotes progress. No one is born with the mediocre skills of big teams, one can (almost) always improve.
- erik_seaberg 7y agoI don't see how learning a vocabulary could ever be harder than continually trying to get the same concepts across without having vocabulary.