Syndication Icon

Software Engineering

True software engineering is carefully designed, implemented, tested, and analyzed. Such software evolves over the course of development through review and feedback from customers. We might make mistakes along the way or be surprised by new and inventive ways customers use our software. This is expected, welcome, and how we grow.

Quality

Our drive for quality is woven through everything we do, and is the primary reason this collective was formed. We are dedicated to championing software engineering practices both in terms of the health of our collective and sound engineering principles.

Communication

Second to technical aptitude is the ability to communicate clearly and succinctly. Mastering the written word allows for you and fellow collegues to express ideas, think deeply about complex problems, and document architecture so others can ramp up quickly. Good communication means less interrupts, notifications, meetings, etc.

Ethics

We craft software that first causes no harm. Our code and business practices strive to make the right ethical choice for our staff, society, and the environment.

Inbox Zero

We avoid letting inboxes/inputs distract from our work by staying focused on Getting Things Done. We deal with inputs by responding quickly, delegating as necessary, and/or scheduling larger projects in order to not distract from tasks at hand.

Zero Bug Policy

It would be unreasonable to assume we never have any bugs. No idea is hatched perfectly at inception, try as we might, but we have a low tolerance for bugs if/when they crop up and work to resolve them as quickly as possible. Bugs are an early warning system that, when left unattended, inevitably leads to complex and even catastrophic failures.

Security

Security is often an after thought but, for us, is a primary focus and concern in everything we do.

Maintenance

Quality software development is impossible without well maintained source code. For us, working toward zero technical debt is an ingrained practice. We achieve low technical debt by being proactive rather than reactive in order to not fall behind open source updates, major version releases, security patches, etc. Only with this level of diligence can we provide a code base that is enjoyable to work in and yields an outstanding user experience.