4 ms·
I agree that information shouldn't be duplicated, but in one of my projects I've taken the opposite approach and made the FAQ the only place that certain inform
by tlocke 5y ago
I agree that information shouldn't be duplicated, but in one of my projects I've taken the opposite approach and made the FAQ the only place that certain information is presented. It's for the library https://github.com/tlocke/pg8000 https://github.com/tlocke/pg8000 and I've called them 'Examples' rather than a FAQ, but each time I get a question that isn't covered by the examples I add in a new example. I'd be interested to hear what people think of this approach.
- c0balt 5y agoIt's a good approach for giving people a point to start/ be inspired by though it will take an increasing amount of time to maintain when your interface changes etc. Reminds me of the aweso.e examples for actix-web that include a lot of common use cases and patterns.