Over the years that I have been in the software development profession, I have watched solutions evolve dramatically. \u00a0The progress has gone from code to libraries to frameworks and now configurable systems. \u00a0However, there are trade-offs to consider when you look at a configurable system instead of one that allows for customization with code.\u00a0 This is becoming a more common dilemma for businesses.\u00a0 Thus, it is good to look at the pros and cons of each approach. \u00a0Here are some points to consider when measuring configuration vs. coding.<\/p>\n
Let’s start with the positives a configurable system brings to the table.\u00a0 Configurable customization is where software of all sorts is heading. \u00a0Part of it is likely due to changing interfaces and keyboards becoming relics of the past.\u00a0 However, there is far more value included. \u00a0I have found that the most significant value companies place in these systems is the lower cost of maintenance. \u00a0A configurable system constrains how changes are made.\u00a0 Thus, it is easier to test those options thoroughly. \u00a0You also are less likely to have typo related issues.\u00a0 The inputs can be highly constrained and validated. \u00a0For example, a drop-down selection item is not susceptible to a typo.<\/p>\n
There is also a lower technical threshold for configurable systems. \u00a0Administrators can often learn all they need to know with a few days of training.\u00a0 As opposed to years required to build stable and scalable code. \u00a0This\u00a0approach has the side effect of reducing the number of points of failure in many cases. \u00a0Less information has to be communicated across departments. \u00a0Thus, for example, a marketing employee can make changes to the system.\u00a0 The alternative is to relate them to a developer to code. \u00a0Business users can focus on their business rather than how to communicate to the technical staff.<\/p>\n
With all that configurable systems have to offer, there is still a level of control given up. \u00a0The limits that make these systems so powerful also keep them from doing precisely what is needed. \u00a0A customer is also at the mercy of the vendor for these systems. \u00a0A required feature may be a long time coming, and critical functions may disappear. \u00a0These may be worst-case scenarios, but that is enough for many to choose a custom coded solution.<\/p>\n
Every business is different, and coding allows for software to be built to precise specifications. \u00a0Your priorities can be crafted into the software.\u00a0 Then, it can change as your business needs change. \u00a0There is also ownership of the product to consider. \u00a0A custom solution is owned by the creator and not a vendor. \u00a0You can change it as needed and do not need to worry about the future stability of the vendor. \u00a0Better yet, any problems that occur are your own. \u00a0There is one place to look for solutions.\u00a0 \u00a0Thus, no time wasted on support calls to get a response to meet your schedule.<\/p>\n
I could list dozens more pros and cons for each side.\u00a0 However, the decision is pretty simple. \u00a0A configurable system is the better solution in most cases. \u00a0One has to recognize that the 80-20 rule holds for these systems.\u00a0 Therefore,\u00a0configuration is an excellent choice. \u00a0The configurable piece of the solutions often allows a company to get 90-95+ percent of its needs met adequately while avoiding the costs and headaches of custom software. \u00a0It also allows you to buy the experience of the teams that created the software. \u00a0They used their expertise to solve common problems. \u00a0This may not get you to one hundred percent coverage, but it will provide tested solutions for eighty-plus.<\/p>\n
Finally, do not underestimate the value of fixed cost solutions. \u00a0Your vendor is providing you a solution that is complete.\u00a0 There are no concerns of improper estimates, scope creep, or schedule overruns.\u00a0 Therefore, the focus is on using the solution, not creating one.<\/p>\n","protected":false},"excerpt":{"rendered":"
Over the years that I have been in the software development profession, I have watched solutions evolve dramatically. \u00a0The progress has gone from code to libraries to frameworks and now configurable systems. \u00a0However, there are trade-offs to consider when you look at a configurable system instead of one that allows for customization with code.\u00a0 This […]<\/p>\n","protected":false},"author":1,"featured_media":366,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[13],"tags":[32,21,31],"class_list":["post-364","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-consulting-strategies","tag-comparisons","tag-consulting","tag-developer"],"yoast_head":"\n