Embracing Simplicity for Developers

In software development, you have the option of taking a simplistic track or a complex one. By taking the complex track, you could potentially be adding more bugs and requiring more testing and more eyes on what’s being done. In this Tech in 2, Principal Consultant Sean Wainner shares why simplicity in development can help you develop exactly what the end user wants: a simple, easy to use product.

In a software system, you have two approaches in development. There’s what I would consider the simplistic track and then the complex track. When you’re taking a more complex track, there’s always the potential to add bugs, because the code is more complex, physically. It takes more testing, more involvement, and more eyes on what’s being done. In contrast, if you’re trimming that back and you’re keeping things very focused and narrow, simplistic, then you’re not having to worry as much. Am I adding more code that has to be tested? Maybe they’re introducing more bugs? In a simplistic system, you don’t have to worry about that as much. 

Simplicity Requires Best Practices

One thing the developers need to carve out a little bit of time for, whether it’s quarterly or yearly, is making sure that you’re understanding what changes in your technology are. Make sure you understand what the best practices are, because those things are going to change over time. 

It seems common sense for most developers, but when you’re working on a product and you’re up against certain deadlines; it can be easier to slip back into old habits. You just want to get something done. What you should be doing is making sure best practices are being followed. There should be a checks and balances process. 

The Ultimate Goal of Simplicity

For the end user, everyone really wants something that isn’t complicated to use. They want an interface, or pages, that are simple to use and easy to navigate. You want something that’s low stress, right? That’s essentially the goal of simplicity.”