Are you a perfectionist? Or do you compromise on quality to get it out the door?
You’re #CuriousAboutData, so read on!
Many discussions center around the idea of “good enough” and about not being a perfectionist.
It’s all good, but often misses the point. In fact, it’s what is technically referred to as a “false dichotomy”. Good enough doesn’t have to compromise on quality. It is supposed to be a limitation on the scope of a project. That’s an important distinction.
If you compromise on quality, it’s really not good enough at all. It’s a jury rigged solution waiting to become a problem. On the other hand, if you design everything correctly, you can still be on time and built for the future so that there is no “throw away” work. Creating a good software infrastructure can be fast and flexible. At BitWise, there is no need to compromise on quality.
For example, we were tasked to create a data transfer application that linked a warehouse management system (WMS) with a digital store-front. The scope of the transfer was not clear from the start, but we had to give the developer something to look at so that they could finish their design and make the necessary choices.
Data had to be transferred asap. Does that mean that we had to compromise on the design? Not at all. We created an abridged version that could run locally, but was easy enough to convert to an Amazon Web Services (AWS) Lambda when the design was closer to a completion. We also made it modular to isolate the field selection module but leave the rest of piping intact through the entire development process.
The result? After about a dozen iterations the digital storefront looks gorgeous, bi-directional sync runs on AWS Lambda in a separate account — and the best of all? Every change took minutes, not hours or days, because at BitWise, the software is built to last from the start, with an intrinsic ability to handle changes. Because, let’s face it, all software goes through change.
We like people, so feel free to call or write. Humans only.
