5 ms·
Sounds like a cool concept. Personally, it's been my (cynical) conclusion that a lot of times the bad-communication around code (e.g. lack of documentation/com
by alexandercrohde 8y ago
Sounds like a cool concept.
Personally, it's been my (cynical) conclusion that a lot of times the bad-communication around code (e.g. lack of documentation/comments, resistance to PR feedback, closed architecture discussions), when it happens, can be attributed to motivations rather than lack of means.
But perhaps tooling provides more visibility around that and reduces the barrier for edge-cases.
- ppezaris 8y agoif we do nothing else, i hope we can improve lack of documentation/comments for some people, with one simple enhancement: allow you to ask a question. currently, all code comments are declarative, requiring you to pay into the system now, not knowing if anyone will ever benefit from your effort. with question-driven comments, you get answers to exactly those parts of the codebase that aren't clear, as it should be. well that's the hope anyway.
- ppezaris 8y agothere's one other aspect i've learned from having built and studied communications systems over the last two decades, which is that you shouldn't underestimate how many edge-cases there are when barriers are reduced. in 2004 nobody shared photos of their lunch with their friends, not because it wasn't possible, but because it wasn't easy. last week i witnessed a teenage girl in a restaurant spend the entirety of a 30-minute dinner taking and sharing selfies. perhaps 100 in total. it's my sincere hope that a reduction in friction gets us all talking about code more often.