Before we write production code, we write test code to establish the expected behavior. As the system grows, we run these tests to help ensure that our software continues to behave as expected and bugs are not introduced.
We are proud of our culture of continuous learning. We gather every Friday afternoon for talks, workshops, and cross-team pairing to learn from each other.
We build software in short, one-week release cycles called iterations. Working this way allows us to provide continuous value and adapt to changing requirements.
Multiple pairs of developers often work on the same projects. To maintain the integrity of our codebase, we use sophisticated version control to continously merge and test the code our teams produce.
At each workstation, you find four hands, two keyboards, and one computer. We have found that writing code in pairs produces higher quality, encourages diversity of thought, and creates higher overall productivity.