An Alternative To Code Reviews
2 July, 2018
I'm not generally a huge fan of code reviews or giving people a dedicated chunk of time to review code, as it doesn't usually work as effectively as you may hope. People waste time focussing on manual reconfigurations and, therefore, don't have as much time to build using the code they have developed.
Different teams will deliver different levels of quality, so your code review should be integrated into your process of delivery. It can be useful to give people DevOps tools in order to support your team. This could include Slack integrations to keep people involved and up-to-date or giving everyone a thumbnail snapshot of what code was there previously and what has been checked in to keep everyone accountable and prevents people from delivering low-quality code. Automate as much of your code review as possible and let your team know about the benefits of increased automation. Namely, automation prevents people from having to rely upon manual testers or QA testers.
You should be able to trust your staff members to deliver code to a high level of quality and to automate to a certain level. When you write automation out of your own functional code, this also helps to make you a stronger owner, as you can start building with the code you are writing as opposed to being constantly stuck making manual configurations to that one piece of code.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Internal Hackathons invite team spirit and collaboration which are critical whether an engineering org is co-located or operating remotely spread across 20 times zones. Hackathons give employees the opportunity to connect and network while they solve fun & relevant challenges.
Senior Director of Engineering at SupportLogic
This was not a high point in my career. It's a story of single metric bias, how I let one measure become a 'source of truth', failed to manage up and ended up yelling at one of the most respected engineers in my team.
Chief Technology and Product Officer at Hive Learning
Supporting principles on why being data led (not driven) helps with the story telling.
Head of Engineering at Xero
Your Org Team may as well be a Sports team. Let's explore how this cohesive, multi-skilled team can be optimized for Great Group Playoff.
Google Cloud Practice lead at Contino
When you grow fast, its normal to focus on Value delivery aka "Feature Releases". Too many releases too soon will inevitably lead to piling tech debts and before you know, inefficiencies creep in, performances goes down, and ultimately any new release takes too long. Sounds familiar? Then read on..
VP - Engineering at ITILITE Technologies