Dev Owns Quality

1. Dev owns quality means better codes.
2. Dev owns quality means find bug easily.
3. Dev owns quality means find bug early, much earlier. We know the later you find a bug, the more expensive to fix.
4. Dev owns quality means reduce the hand off, more efficient and more fast.
5. Dev owns quality means test ability. When dev owns quality, dev has to think about how to test it when write code. They can’t be tested manually. Test automation is the only way to go, otherwise, he is not going to have time to write new codes any more but doing manual testing all the time :)

译：

1. 开发对质量负责，意味着质量更高的代码；
2. 开发对质量负责，意味着更容易定位BUG；
3. 开发对质量负责，意味着尽可能的发现BUG。越迟发现BUG，修复它所产生的成本就越高。
4. 开发对质量负责，意味着减少不必要的相互接口，具有更高的开发效率和更快的响应；
5. 开发对质量负责，意味着具有更好的可测性。当开发有更高的质量意识时，开发之前他就会考虑到如何对自己的代码进行充分的测试。开发是会进行手工测试的。自动化测试时唯一可行的方法，开发人员是不情愿为了测试增加新代码和进行手动测试的。

Here,you might think this is TDD. Dev owns quality means use TDD. 

Well, not exactly.  My experience with TDD is more in the ideally world. I don’t see any team yet use pure TDD. 

Most teams use what we called delay TDD. You still write code first, and then write test, then do the refactoring, in the end submit both code and test at the same time. 

译：

读到这里，也许你会认为这是测试驱动开发（TDD）。开发人员对质量负责的软件开发确实需要使用TDD。

然而，这种观点也不确切。我的TDD经验告诉我，TDD可能过于理想化。你可能找不到纯粹使用TDD的团队。

更多的团队使用着他们所认为的TDD：开发人员会先写代码，然后再写测试代码，再然后重构代码，最后提交代码和测试同步进行。

This is more nature way to develop software and achieve the same goal of TDD, meanwhile it’s much easy to adopt vs pure TDD which is completely opposite of what you came along. furthermore, dev owns quality can be extended to owning functional testing, i.e not only making sure  unit works by unit testing, but also make sure component works by functional testing.

译：

这是理所应当的软件开发过程，也可以获得和TDD同样的目的，同时也非常容易被抵触纯粹TDD开发的团队所接受。开发负责质量可以进位扩展到负责功能测试。比如，不仅仅为了单元测试而编写单元测试，同时可以考虑编写子模块内部的功能测试代码。