Developing for developing

We’re going to start dedicating time for the team at Brinkbit to periodically analyze and improve our workflow. As creators of developer tools, self-reflection and examination are both natural and necessary. Our tools need to help other people do what we do every day. We’re already constantly striving to reduce and eliminate friction in every area, from communication methods to hotkeys and macros. I’m hoping that having dedicated ops improvement time will canonize this element of our company culture. Ideally the improvements we make for ourselves in these times will naturally manifest as improvements in our product.

It can be hard for an organization to justify spending time on development that doesn’t visibly impact revenue or product outcomes. Obviously revenue and quality product are central to an organization’s success. But I’m confident that the net gain of hours saved to hours invested over the years will end in our favor. Additionally, I’ve found that the time investment spent on improving operations really pays off during high-pressure crunches. The only way we’ll be able to consistently deliver timely results is if we’re constantly examining our process and improving areas of weakness.

We don’t want to reinvent the wheel, we just want to tweak it a little bit, smooth out some of the bumps so it can roll a little faster.