I have some earth-shattering news to share… Software Engineering is hard. Expectations for Software Engineers (as opposed to programmers) are high. We’re expected to have an ever-broadening spectrum of knowledge, and to be able to…
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…
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…
Last time, we saw how to make each test target it’s audience effectively. This was important because different audiences have different needs. So we should address those needs individually, in separate stages of our continuous delivery…
Last time, we talked about how to write tests that don’t impede our continuous delivery pipeline. Today, we’ll start the discussion on how to make our pipeline effective for all stakeholders. Different types of tests…
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.