We’ve been going through a major upgrade of the site recently. There’s been a few reasons for this:
- Time on my part to deal with coding
- Time on our developers part to work with us complex code
- Funds for purchasing modules / development work
At the same time, we’ve got to balance both the cost of an upgrade to the site with its potential benefits. Most changes fall into one of three major categories:
- Front-End Design Changes
- Back-End Administrative Changes
- Bug Fixes
Front-End Design Changes generally focus on making the website more user friendly and interactive. So the addition of the Social Share buttons to the site, the new Checkout are all front-end design changes.
Back-End Administrative changes help us work more efficiently. Example would be integrations with Canada Post, a stock updater and edits to our PDF invoices.
Bug Fixes are more complex. When we can, especially if it’s a bad bug; we fix the problem as quickly as possible. However, to fix a bug we need to replicate it. Unfortunately, with some of our more persistent bugs in the system; they are extremely difficult to replicate. Without going through a tens-of-thousand dollar bug-hunt; they’re just not feasible.
What to Fix & When?
The obvious constraint is funds. All these changes require funds – whether its purchasing pre-made modules that should work out-of-the-box or having our developers write the code for us specifically.
The Benefit of the change is another major factor – if it’s fixing a major bug or adding a new, must-have feature to the site; we’ll attempt to get on it immediately. However, some projects are multi-week projects and those then require both the funds and the free time to complete.
Lastly, there’s the Complexity of the project. It’s why you see a lot of small, simple projects done before the major changes. Since I can hack my way around basic code; I tackle all the small projects when I have time; leaving the complex code problems to the real developers.