Computer Scientists often use the phrase “premature optimization” to describe effort wasted on making code better or faster when it hasn’t been demonstrated to be a bottleneck in the software’s run time or the development team’s process. Implementing a super-fast-access data structure for a list of just ten things would qualify, as would spending eight […]

One of the more challenging aspects of my transition to working remotely here at Atomic since this March has been adhering to our Teach and Learn value. So much of that value was ingrained in a key part of our workplace culture: proximity to one another. As a mentee, this proximity to a pair (and […]

When most people start remote onboarding at a new workplace, they drown in new policies, people, and responsibilities. I did that in my first few weeks at Atomic this past June. But when I finished my four daily hours of drowning in code, I went outside and started my four hours of drowning in manure. […]

During my first few months at Atomic, I’ve asked a lot of questions, with topics ranging from Typescript syntax to why the shortcut for our Slack workspace’s Patrick Bacon emoji is “:dad_joke:.” Atomic’s “Teach and Learn” value is integrated into how we interact as teams every day. As I’ve started pair programming, I’ve often heard […]

As a member of a software implementation team, I consider building credibility with new clients extremely important. Fortunately, clients usually have many positive interactions with people at Atomic Object before meeting with us, which tees up the relationship. Nevertheless, there’s often a noticeable skepticism from clients before implementation begins. This is understandable, as these clients […]