Building custom software is costly, complicated, and sometimes emotional. A well-executed project must hew to a fine line to navigate many constraints successfully, threading the needle between cost, timing, purpose, user needs, technical constraints, maintainability, extensibility, and operational considerations.
An idea for a product is just the beginning. To find success, you need a broad view of what’s important, the willingness to proactively go above and beyond, and careful planning. We call this collection of attributes “owning it”—personally investing ourselves in the success of our projects and seeing them through to success. Read more on “Owning It” Every Step of the Way…
We recently took a look at some of our benefits to see if there were improvements we could make in support of our efforts to grow Atomic in diversity and numbers. Having a diverse team makes Atomic better and stronger, and we want to grow the number of women we employ while continuing to make Atomic a welcoming and supportive place for all Atoms to thrive.
We decided to work through writing a simple language and provided participants with an introduction to the challenge, a set of unit tests to guide them through the implementation, and coaches to jump in with suggestions as needed. Oh, and plenty of food and drinks to keep everyone happy and energized through the day. Read more on GVSU WIC Workshop – Write Your Own Language!…
Fair pay matters a lot. It’s important to our business that we attract and retain top talent, and it’s important to me personally. I care about the Atoms at Atomic; they’re my friends. For them, and for my own personal integrity, I want a fair and consistent value exchange for everyone at Atomic.
I’ve been part of Atomic for 10+ years, and it’s easy to forget some of the dreadful feelings and experiences I’ve had in other companies where transparency in financial performance was not part of the culture like it is here.
I hate the idea that we might miss hiring an awesome teammate at Atomic Object — especially if we lose the opportunity for a stupid reason like an unintentional bias in our interview process. Several of us recently read Thomas Ptacek’s post about fixing broken developer interviews, which has spurred our efforts to improve our ability to gather consistent, concrete, unbiased information about candidates throughout Atomic’s hiring process.