Henrik Berg Andersen
15 years of developer experience have given much code insight, but it is only half the story.
With more than 15 years ERP experience, I have been in divergent roles and scenarios, including everything from regular programming to maintaining a customer solution to mission-critical investigation of chaotic relationships in an ERP solution, with threads into the customer’s organization, business processes, social relations and communication conditions.
I am basically a developer with an education in computer science, but it is often evident that traditional role designation come up short when it comes ensuring the customer's best interest. A holistic insight into the overall context of things is necessary for understanding the potential impact of changes on departments or employees other than those a task is focused on. Being able to code is fine, but business sense is necessary in order to handle what our customers expect us to.
Honesty and equality are characteristic even when something is not done entirely as desired, because an error is essentially a matter of getting rules and policies clarified or expanded and reflected in an ERP solution. Open dialogue is therefore crucial in exploring the requirements for a new functionality.
On a team, I do best together with a consultant whose expertise is distributed a little differently than my own. We will have a common understanding of the professional aspects, and the old saying about two heads being better than one will achieve full expression.
