4 ms·
All of those things are what a developer worth anything to a company should be doing. Similarly, BAs without business domain knowledge are even more worthless
by lugg 7y ago
All of those things are what a developer worth anything to a company should be doing.
Similarly, BAs without business domain knowledge are even more worthless because of this.
I.e. consultant BAs are, as most of us know, a waste of money.
BAs are struggling to find a language to describe their business requirements in a way the programmer or computer can understand.
It's code. It's what programmers have been writing all along. That is the god damn language they need.
Given when then? If then else.
Surprise!
- kthejoker2 7y agoRicardo strikes again. Relative comparative advantage says even if a developer is a better coder and BA, they're better off spending time coding and letting non coders be BAs to maximize overall throughput.
- lugg 7y agoThis assumes a BA is cheaper and more available than a programmer. If they are cheaper, I guarantee you're going to have problems. You're literally installing a weak link in the most crucial part of the chain.
- kthejoker2 7y agoBAs are by definition more available than developers, as all developers are BAs but not vice versa. And given basic supply and demand they are cheaper. Anyway read your Ricardo, you're right but wrong about the implications. Your development is an even weaker link in the chain because good developers are even rarer than good BAs.
- dragonwriter 7y ago> BAs are by definition more available than developers, as all developers are BAs but not vice versa. Plenty of developers are not BAs. BAs are systems analysts with expertise in requirements elicitation (basically, goal-directed interviewing) and technically writing. Plenty of developers are neither systems analysts nor skilled at interviewing or technical writing.