This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
We use Extreme Programming as our model of how to develop software. They also love test-drivendevelopment, pairing, continuous integration, and evolutionary design. They tend to be passionate, senior developers. They tend to be passionate, senior developers. You see, Extreme Programming is too.
These principles tell us our tests should be: Fast. Independent” is an especially common pitfall – it is very tempting to have tests depend on program state, its environment or on other tests. In the long run, this will result in tests that are hard to maintain and understand. Independent. Repeatable.
It’s been a fascinating opportunity to rebuild an engineering organization from the inside, and I’m loving every minute. We’re introducing a lot of cutting-edge software development practices, such as self-organizing vertically-scaled teams and Extreme Programming. Culture doesn’t change easily. It tends to snap back.
PDF) Culture Changes The purpose of the new career ladder is to help change the engineeringculture at OpenSesame. Software Engineer Software Engineers contribute to the work of their team without explicit guidance. We rolled it out in July, so now’s a good time to share what we’ve learned so far.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content