
To clarify: one can configure a new database, which is clearly essential and highly beneficial, but this means using existing tools and functions in the system which, for the most part, can be managed by just the software's "front-end" interface (i.e. drag-and-drop, using the standard GUI and the like). Indeed, some CRM systems can do this and still provide very sophisticated functionality and capabilities.
But as soon as you start writing code, "customising", bespoking a system, then that is what I would recommend you try to stay clear of, at least when you are first implementing a new database.
Why? Because customising takes longer, is more complex, needs more work, raises the risk factor, it will cost more, requires more specialist expertise, will be harder to change later, will be harder to maintain later, you may change things you will later learn you didn't need to change and so on.

And if such discussions mean that coding/customising is shown to be a beneficial thing then great, let's do it. If not, keep it simple, configure the database, use a process and move on. Your project manager will thank me. And so will your FD.
No comments:
Post a Comment