A lot happens before ideas become solutions.
At ElixWare we want to bring you more than just great, affordable software. We want to let you know how and why we do what we do.
Our Ruminations blog will bring you insights into how we got here and some of the things we consider when trying to help you run your business. We hope it gives you a better understanding of how we strive to better serve your needs.
I'm currently reviewing a software package we developed years ago. It's being migrated to a new server and will get some updates in Q1 23. This codebase actually started as a small task back in 2014. It was simply designed to meet a client's need to transfer a specific kind of data to a partner company. It eventually evolved into a large project that is now a foundation of their daily operations. I like to say we built the car while we were driving it, which is just how it happened.
It started off small and became something larger than any of us ever imagined.
You can watch the "The Story Of Bridge Over Troubled Water" on YouTube.
I know this all sounds like a small project that escaped its pen and careened out of scope. And in some sense, that's exactly what happened. But this was a situation full of unknown unknowns, and our initial code was just meant to patch a simple need. A bandaid, nothing more.
Once this "patch" was in place a lot of other simple needs started to become visible. And so, this journey began.
The original user interface is still in place, but after all this time it looks dated and limited. That's one of the changes that are coming next year. Newer systems we've produced for this client have a different look and feel, but this legacy system is still used more than everything else we've done for them combined. So, we're planning a facelift that we hope will provide more functionality without sacrificing any of the current features.
Unlike some legacy systems, the core of this one is still essential to the client. The time and effort to update software, without adding any major features, isn't always embraced. But we all agree that this is a necessary step to extend the life of this system until at least the end of the decade. Any updates will also improve the codebase to make it easier to maintain moving forward and to look less like the car pieced together by Johnny Cash in "One Piece at a Time".
Also, I'm sure we'll be adding more messages to Future James while we're at it.
prev post: R is for Ransomware