Business logic
-
I am writing some software for a client and find some of their business processes and way of doing things a bit illogical and confusing. A number of times I have thought "Why do they do it that way, wouldn't it be simpler to do it this way instead. Plus it would make my life easier too". On the occasions I have brought this up, I am usually met with the reply "that's the way we do it". Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.
-
I am writing some software for a client and find some of their business processes and way of doing things a bit illogical and confusing. A number of times I have thought "Why do they do it that way, wouldn't it be simpler to do it this way instead. Plus it would make my life easier too". On the occasions I have brought this up, I am usually met with the reply "that's the way we do it". Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.
Member 9475889 wrote:
Anyone else get this much?
</sarcasm> You're kidding, surely! Usually when talking to the client they embrace any changes in processes with open arms, glad to have an outsider tell them that their processes are inefficient. </sarcasm> With the right approach, infinite patience, and a 'seeing things from their point of view' attitude, it can be done - but you need to be really certain you have all the information before persuading them to change processes! Write software to cater for existing processes - you get paid and all is well. Change their processes and write software to support the change and you still have a fight to get the users to adopt it - and they will be negative. And if you miss something (usually because they just haven't told you about it) it will be entirely your fault.
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
I am writing some software for a client and find some of their business processes and way of doing things a bit illogical and confusing. A number of times I have thought "Why do they do it that way, wouldn't it be simpler to do it this way instead. Plus it would make my life easier too". On the occasions I have brought this up, I am usually met with the reply "that's the way we do it". Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.
Member 9475889 wrote:
Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.
Of course... it happens all the time. Here's one way to consider things: You are professionally obliged to inform the client that you believe that their process could be improved by X, Y and Z. BUT... at the end of the day, it's the client's call, and if they don't want to, then develop what you have been asked to develop. So long as you have informed the client, you have met your professional obligations.
Quad skating his way through the world since the early 80's... Booger Mobile - My bright green 1964 Ford Falcon - check out the blog here!! | If you feel generous - make a donation to Camp Quality!!
-
I am writing some software for a client and find some of their business processes and way of doing things a bit illogical and confusing. A number of times I have thought "Why do they do it that way, wouldn't it be simpler to do it this way instead. Plus it would make my life easier too". On the occasions I have brought this up, I am usually met with the reply "that's the way we do it". Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.
As has been pointed out, as a professional you should be enlightening your client as to potential process improvements, I say potential because you do NOT know their business practices as well as they do. And the LIE even if only by omission. 3 months after your system goes to production some pillock will come back to you with "oh I forgot to tell you this requirement". It may justify their entire approach (probably not). At the end of the day you build to your clients requirements even if it seems idiotic in your opinion.
Never underestimate the power of human stupidity RAH
-
I am writing some software for a client and find some of their business processes and way of doing things a bit illogical and confusing. A number of times I have thought "Why do they do it that way, wouldn't it be simpler to do it this way instead. Plus it would make my life easier too". On the occasions I have brought this up, I am usually met with the reply "that's the way we do it". Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.
The 2 Rules of Business Logic: 1. It's always been done that way. 2. It's never been done that way. Changing existing processes is never easy and often unwise. Keep reminding yourself that you gave them the best application they asked for and were willing to accept.
-
I am writing some software for a client and find some of their business processes and way of doing things a bit illogical and confusing. A number of times I have thought "Why do they do it that way, wouldn't it be simpler to do it this way instead. Plus it would make my life easier too". On the occasions I have brought this up, I am usually met with the reply "that's the way we do it". Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.
Business logic is to business what Military intelligence is to Military.. There you have it! :P
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
-
I am writing some software for a client and find some of their business processes and way of doing things a bit illogical and confusing. A number of times I have thought "Why do they do it that way, wouldn't it be simpler to do it this way instead. Plus it would make my life easier too". On the occasions I have brought this up, I am usually met with the reply "that's the way we do it". Anyone else get this much? Do you persist and argue your point or just give them exactly what they ask for? It's not my place to change their business processes, so I'm inclined to give them what they want and take the money. However, I'm left with the feeling that the application was not as good as it could have been.
You are not alone, I am starting to think that all business processes are illogical and confusing. Perhaps its just the way life is, cant change that.