Have you ever wondered what a code review is and/or what it’s like to participate in one? Are you a tester, product or business person who regularly interacts with the output of the code but wonders if they could catch bugs earlier by “shifting left”?
Turns out you don’t have to know how to code in order to learn about the changes, question the assumptions, clarify ambiguities, and generally participate in the knowledge-sharing around Code Reviews. Here’s a presentation on how to get started and what to look for.
Simply register to gain access, and the video will start right away.
I much prefer the saying move fast and make things better over move fast and break things. The latter might be more popular but the former is more realistic.
Moving fast (software agility) used to be a business advantage but now, at least for any service business, it’s mostly a requirement. Fast implies some things might “break” and while that’s part of the process it should never be our aim. (We should have flexible systems in place to help us quickly identify and fix those “breaks”. Moreover a DevOps culture can help us improve stability so “breaks” are less severe.)
A more realistic mission should be to solve our customers problems and do so in a way that continually improves. Where failure doesn’t mean we stop but rather we iterate until it’s right. This way we solve the customers problems while being able a benefit to our business.