3 ms·
Poor documentation is a strategy, and if it's poor enough you can run your own university/camp. A large complicated codebase is another strategy. Edit: Strang
by 0xdeadbeefbabe 8y ago
Poor documentation is a strategy, and if it's poor enough you can run your own university/camp. A large complicated codebase is another strategy.
Edit: Strangely enough, I don't know anyone who did this on purpose.
- eruci 8y agoI don't do that on purpose, but I'm guilty on both counts.
- ChrisCinelli 8y agoIt seems that today is it is hardly a good strategy. Unless you are giving something so valuable and scarce, poor documentation is pushing away adopters. The average engineer will think about building the service on their own.