We’ve talked about how Clean Code leads to better naming and focused functions. Both have a huge impact on how quickly the development team can respond to change. But there’s another piece, without which, the…
Continuing our Clean Code discussion, imagine you have a textbook from which you only need information from a single section. Now imagine that textbook has neither chapters, nor sections or paragraphs, and is even lacking…
As we continue our discussion of Clean Code, I’d like to begin by asking you a question…What book do you think best serves as a daily reference for improving the readability and understandability of our…
Clean Code is important for developers and managers. Last week in our post about the difference between programmers and engineers, we made the argument that software engineers – not programmers – are what we need…
Programmers: stop calling yourselves engineers. That was the title of an article I found myself reading a couple months ago. Of its many points about the difference between programmers and software engineers, I summarize them…
This week one of BTI360’s very own was part of a featured panel discussing Testing for Continuous Delivery hosted by Electric Cloud. In the discussion, Chris talks about: Evolving a test matrix as part of…
If you have been following along thus far in our Lean Laundry series, bless your heart. Hopefully you have gotten a few laughs, learned how large batch sizes can really mess things up, and reduced…
Close Form
Then stay up-to-date with our latest posts delivered right to your inbox.
Whether we’re honing our craft, hanging out with our team, or volunteering in the community, we invite you to keep tabs on us.