- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
When the coder's knowledge surpasses the business analyst on a project
Posted on 6/5/14 at 7:08 am
Posted on 6/5/14 at 7:08 am
Do you find this happening often? For example, say an analyst passes specs to a programmer to code an interface tied to a relatively complex business process.
At first the BA has more knowledge, but once the programmer really gets going, he has to think through the whole process in purely logical form.
Over time that leads the programmer down the path of more knowledge and having to explain the intrinsic logic of the process (and it's flaws) to the BA. And at that point...the BA is effectively obsolete.
Think Chicken vs. Circus Child
Am I the only one who sees this all the time? Disclaimer: I've been on both sides of this coin.
At first the BA has more knowledge, but once the programmer really gets going, he has to think through the whole process in purely logical form.
Over time that leads the programmer down the path of more knowledge and having to explain the intrinsic logic of the process (and it's flaws) to the BA. And at that point...the BA is effectively obsolete.
Think Chicken vs. Circus Child
Am I the only one who sees this all the time? Disclaimer: I've been on both sides of this coin.
This post was edited on 6/5/14 at 7:09 am
4
Posted on 6/5/14 at 7:43 am to theunknownknight
I think it's an inevitable evolution.
They need to give you all of their knowledge, and in you breaking it down and building it back up makes you see the inherent weakness in the models they are using.
This is why programmers are being used to breakdown systems to look for weaknesses in not so related fields such as agriculture and epidemiology. Trying to understand what is attacking what and then piecing out what parts, if targeted, would mitigate the effects or yield a drastic change in the end.
They need to give you all of their knowledge, and in you breaking it down and building it back up makes you see the inherent weakness in the models they are using.
This is why programmers are being used to breakdown systems to look for weaknesses in not so related fields such as agriculture and epidemiology. Trying to understand what is attacking what and then piecing out what parts, if targeted, would mitigate the effects or yield a drastic change in the end.
Posted on 6/5/14 at 8:05 am to theunknownknight
Pretty common. I think it is the analysts job to do all the leg work and the developers job to shoot holes in it, which then helps them learn more due to working through the issues.
Posted on 6/5/14 at 9:28 am to HeadyMurphey
Plus, the analyst usually has the people skills to deal with the end user/customer. Most programmers I know want nothing to do with that process. This of course is not the case with everyone, but a general observation.
Posted on 6/5/14 at 9:58 am to theunknownknight
If the BA had as much knowledge as the dev, they would be a dev.
Posted on 6/5/14 at 10:04 am to theunknownknight
It's pretty common. Let's look at LSU for example. You have both an ISDS and CS program. The ISDS students are more than likely going to become your BA's as they have taken the business courses to become more well rounded. Whereas your CS students know way more detail about coding and can give you a better product. Paired together you can get a good product, but one without the other and its a gamble.
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News