“Who Tested That?” Probably Someone Like You

I’m sure many of you have come across errors like the one above when you are surfing the internet or using an app. Your first reaction might be, “Who tested that?” You know your site and app would never have an error like this in production!

Or would it? Here are a few reasons why this bug might have made into it production. Read more on “Who Tested That?” Probably Someone Like You…

The Value of a Fresh Pair of Eyes

When you’re working on a piece of software for a long time, it can be easy to overlook poor architecture or an awkward UX. You may spend your day avoiding the dark corners of your app and choosing to forget that they even exist. Unfortunately, when this happens, the health of our codebase and application can suffer.

Recently, my project team gained a new member—a fresh set of eyes unfamiliar with our application’s design. This newness allowed them to notice inconsistencies and ask valuable questions about why we chose to architect our app as we had. Read more on The Value of a Fresh Pair of Eyes…

What I Learned from Working 32 Hours a Week

In early November, I helped run the Weekend For Good event as part of the Code For Good West Michigan admin team. The event brought together 120+ volunteers and 14 local nonprofits to help build, rebrand, or update websites. It was scheduled for three straight days, and I was there for all of it.

It’s safe to say I needed a break after working my normal weekly schedule along with the extra hours I put in over the weekend. This made November 5 an important day—and not because it was Guy Fawkes Day, but because it was the first time I had used any of my allotted vacation time. Read more on What I Learned from Working 32 Hours a Week…

Redux Thunk Best Practices for Loading Initial Data

Every application needs to handle a couple of tasks: loading initial data for users and determining what page or screen they land on. Despite being order-dependent, this logic is often scattered into various parts of the application. This can lead to subtle bugs and makes it hard to answer simple questions like, “What will the user see when they log in?”

Redux and Redux Thunk are great for structuring front-end logic, but without a strategy for handling loading, the logic can still get out of control. Read more on Redux Thunk Best Practices for Loading Initial Data…

Bluetooth Mobile App Testing Checklist

Bluetooth is one of those technologies that seems like a very simple thing from the perspective of a user—you set it up once and forget about it. But in reality, there’s a lot of complexity hidden behind the scenes. As we all know, wherever there’s complexity, there’s more that can potentially go wrong. Read more on Bluetooth Mobile App Testing Checklist…

Three React Native Libraries I Can’t Live Without

As I wrap up my current project, a React Native app, my team has been thinking a lot about what went right and what went wrong when using the framework. Since it’s a pretty lightweight framework, we brought in a lot of external libraries to help us build our app. Besides some always-useful libraries, such as Lodash, Redux, and date-fns, there were a few that really helped the app come together. Read more on Three React Native Libraries I Can’t Live Without…

Your Backlog Isn’t a To-Do List – It’s Self-fulfilling Prophecy of Success or Failure

Your backlog is an imperfect, always changing, self-fulfilling prophecy for how your software will be built. Not only that, but at a software consultancy like Atomic, it’s also a prophecy for how the engagement will end and deliver on your brand promise.

All this to say: Tending to the backlog is one of the most important activities development leaders can engage in to ensure a project goes well overall. Read more on Your Backlog Isn’t a To-Do List – It’s Self-fulfilling Prophecy of Success or Failure…

Four Steps for Inheriting a Codebase

In the last two years, I’ve worked on a few projects passed on to me by other teams. Inheriting an existing codebase can be a challenge, given you weren’t there when architectural decisions were made, you are less familiar with the project domain and client needs, and you are just new to the codebase.

Read more on Four Steps for Inheriting a Codebase…

Using “Last Thursdays” to Discuss Exceptions with Users

Most people call them “exceptions.” We call them “Last Thursdays.” I’ve mentioned this term in a couple of my previous blog posts, and I think it’s important to touch on it one more time, to better explain what it means, and to discuss how changing the name has helped us communicate more effectively with our clients. Read more on Using “Last Thursdays” to Discuss Exceptions with Users…

loading…