Recent Posts3076
General Software Discussion / Re: Implement features that are known to be loved in other programs, on your own
« Last post by skwire on August 16, 2011, 12:12 PM »I concur with f0dder's comments. What it boils down to for me is ROI (Return On Investment):
This includes trying to forecast how many other users would use such a feature. That first question leads to the second question I ask myself:
This is something that non-programmer folks NEVER consider. They see it done in one application and think it can be slapped into any other application in under ten seconds. There have been instances where I would very much like to add a given feature but cannot due to such limitations.
What I've found over the years is that most non-programmer folks have zero idea how easy or hard an idea is to implement. In fact, there have been lots of times where I have had requests from non-programmer types that they think is super easy (in their head) and, in reality, would be nigh impossible to do programmatically.
- Is the requested feature worth the time it takes for me to implement it?
This includes trying to forecast how many other users would use such a feature. That first question leads to the second question I ask myself:
- How easily can I implement such a request within the limitations of the GUI toolkit/controls I am working with?
This is something that non-programmer folks NEVER consider. They see it done in one application and think it can be slapped into any other application in under ten seconds. There have been instances where I would very much like to add a given feature but cannot due to such limitations.
What I've found over the years is that most non-programmer folks have zero idea how easy or hard an idea is to implement. In fact, there have been lots of times where I have had requests from non-programmer types that they think is super easy (in their head) and, in reality, would be nigh impossible to do programmatically.
