In the modern Western world, we turn to software as the solution to most business problems — and rightly so. Software can be a fantastic tool to bring efficiency, consistency, and predictability to business processes. However, I often see business leaders misunderstanding what technology can and can’t do for them. They look at the tough […]
Good software is never done. This is even true for software that could be considered “feature complete.” There may come a time when there are no more opportunities worth chasing by adding to a product. However, there will always be a need to ensure it continues running smoothly. While the bits in your software don’t […]
Many first-time Atomic clients are also first-time custom software buyers. To those first-time buyers, I can imagine that Atomic’s sales process is pretty disorienting. We sell our services in a non-standard, custom way. If you are experienced in software buying, you might also be interested in a high-level understanding of our sales process. We are […]
Atomic’s product teams start software projects with Human-Centered Design (HCD) practices and Design Thinking activities that help us focus on the customers who will use the software. But that’s not the only use for this type of user-centered thinking. I’ve also found HCD incredibly helpful for teams who are deciding whether to continue supporting a […]
Imagine you’re building an internal business tool for your global company. This new tool will improve and streamline the work of hundreds of your coworkers. It’ll also give the business better visibility into how your bottom line is being built. You’re close to having a minimal usable product to ship, so what’s next? Because We […]
I’ve always had a hard time talking to “blue-sky” thinkers and entrepreneurs with the “next big idea.” It’s not because I don’t enjoy talking to them. It’s the opposite — they hate when I question them. I’ve been guilty of this, too. You’re passionate about your good ideas — you love them. And when people […]
Earlier this year, I rotated onto a long-running project. This was the first project I’d joined that already had an established code base and team. This particular project is complex, with a large team, big goals, and a long history.
When starting a new software project, there are a series of questions that need to be explored before diving headfirst into the development cycle. At Atomic, we often spend time in what we call the “Research, Design, and Planning” phase of the project to do just that.
Software applications (like homes, cars, and nearly everything else) need maintenance. Even when the software itself doesn’t change, the systems/devices it runs on and the larger software environment are always moving forward. This is called Software Rot. Most software maintenance falls into one of these categories: Updating Dependencies – Upating the frameworks, libraries, etc. that […]
Software rots if not maintained. The longer it sits on the shelf, the harder it becomes to work on it. It may even stop working on its own one day. This surprises my clients frequently, so I wanted to talk a bit about why this happens and how to plan for it.