@JackDunaway wrote:
@JÞB wrote:
I usually work with "One-off" systems.
Very true; when volume is low (as low as one), ROI of any one arbitrary "software engineering best practice" could be negative. Our (infernal) task as engineers and business persons is to have a good grasp on the tipping points for each task.
I like using "happiness" as a heuristic; when either side gets sufficiently unhappy, it's time to change.
@Craig_ wrote:
There's a nifty trick...
Slick!
I prefer "Soultion Delivered" but accept the point of view from Wirebird. That was nice! and justisfies my ideas for
context in MAX.
Key takeaway?:
Check your user's "Storey" ?Do they understand the GUI? "Story-time" is a key element in making my users happy....
"Should be" isn't "Is" -Jay
