I am not evangelizing TDD for various reasons but I would like to share an relevant observation which I frequently made while working on consulting projects. If developers do not know how to write tests or need to take shortcuts (in form of not writing tests) they usually end up with a codebase that is hard-to-test. I was recently asked to add tests to such a codebase. The project had a few tiny testcases. I quickly discovered that I can not write tests for the project without making the codebase testable first. Now I have to take the risk of refactoring without the safety-net of powerful tests.

Today I had the chance to meet with Joel Spolsky at a Q&A event. Joel is the CEO of Stackoverflow and maintains an impressive track record as founder in the NY startup community. Given his unique background of being a successful founder with tons of software development experience, Joel has something to say on what works in software development and testing.

I have recently watched Larry Hastings talk about Removing Python's GIL: The Gilectomy that has been recorded at PyCon 2016. Larry very graphically outlines the problems from not having proper concurrency features. He also tells a nice story on how the Python community is struggling with this situation for the last 24 years.

DevOps is about operations, right? And about applying tools and processes from the Dev space to operations. But QA? Really? What I personally experience driving DevOps transitions is that continuous integration and operations need to work together. People need to realize that these are two sides of the same coin. One of the biggest challenges is that people often do not see it this way.