4 ms·
The real WTF was letting a Business Analyst do anything that could directly affect the code without it going through a programmer first. Would you let some guy
by Xichekolas 19y ago
The real WTF was letting a Business Analyst do anything that could directly affect the code without it going through a programmer first.
Would you let some guy build you a car if he had changed his oil once, years ago?
A+ story. Can't believe how much this stuff happens.
- raganwald 19y agoI recall reading something (sorry no link at the moment) which exhorted people to remember that anything which affected the software's ability to meet requirements is code and is to be treated as such. Which means... some kind of revision control and the full scrutiny of your QA process before deployment. So if a customer says, "and I want to be able to change the workflow rules without programming," you can say "Sure we can do that!" But you have to educate them to the fact that just because you give them a way to do that with a GUI or a DSL or whatever, the heavy part of the process--specification, testing, whatever--does not magically go away. I'm rambling a bit, but I guess I am saying that had this project succeeded exactly as they envisioned it, an incredible WTF would have hit them when the customer started changing the rules and breaking everything.