The company I work at right now seems quite good at maintaining solid code quality. I'm pretty sure the reasons why are: * A belief that code quality lets us d

The company I work at right now seems quite good at maintaining solid code quality. I'm pretty sure the reasons why are: * A belief that code quality lets us deliver faster in the medium-term * We start projects by asking "why does this need to be done?" and pushing for a fleshed-out explanation of that. This lets us write less code and do sometimes do projects without writing code. It also reenforces that we are building sonething that we will then need to mainain. EDIT: * We also follow that up with writing out a 1-2 page document explicitly outlinibg the scope of the project, the approaches we considered but are not taking, and the approach we are taking. This helps us keep a 1 week project from taking 3 weeks. * Our hiring process includes a take-home coding test and a pair-programming exercise. We explicitly grade these on code quality and testing, so we filter for hires that value these things. Feel free to email me at amfarrell@gocardless.com if have questions.