How do you balance business process changes against the challenges of changing software?
Posted
by Achilles
on Stack Overflow
See other posts from Stack Overflow
or by Achilles
Published on 2009-10-29T19:03:10Z
Indexed on
2010/05/31
1:52 UTC
Read the original article
Hit count: 351
efficiency
|business-process
In my admittedly young career I've found myself writing code to support quirky business rules and processes. Inevitably these changes were always in some massively difficult code base and caused many issues. My question has a couple of parts:
While software is a tool for businesses to make their lives easier, at what point do we as developers suggest a change in business process rather than in the software as the "magic bullet" to solve a particular problem.
How do we as developers evangelize a certain level of reverence for the software as well as the difficulty involved in making changes simply to support the quirks of the business?
I understand that these changes in business processes promote our industry, but in an analogy my father would understand: Which is easier, to melt down a hammer to forge a screwdriver to drive screws or to simply use nails since your hammer is already awesome...?
© Stack Overflow or respective owner
