4 ms·
If you aren’t ready to say no and risk upsetting people, you’ll ruin both your software and mental health I think. A workaround to simply saying “no” might be
by alkonaut 4y ago
If you aren’t ready to say no and risk upsetting people, you’ll ruin both your software and mental health I think.
A workaround to simply saying “no” might be to make extension points or plugin functionality and then lots of requests can be closed with “this is a good idea for an extension but not suitable for the core application, at least not at the current time”.
- perlgeek 4y agoThis is indeed a good strategy, but beware: designing, implementing and documenting a good plugin or extension mechanism is quite some work itself. If it makes sense for your project to have such a thing, sure, go for it. If it's just a way for you to avoid having to say no... learn to say no instead. :-)