When a team decides it needs a coding convention, the usual move is to borrow one from a big company, such as Microsoft’s C# conventions, the Airbnb JavaScript guide or one of Google’s style guides. That’s a sensible starting point. But each of those documents was written for one company’s team size, codebase and tools. …
Programming Processes
Programming Principles: DRY, KISS, SOLID, YAGNI and More
I’ve written before about the principle I use most when designing software, doing the simplest thing that could possibly work. This post collects the other programming principles and laws I keep returning to, from DRY and SOLID to Conway’s law and Brooks’s law. None of them can be applied mechanically, and several pull against each …
Code Review Best Practices: A Complete Guide for Teams
Code review is one of the cheapest ways to improve software, and one of the easiest to get wrong. When it works, bugs get caught before they ship, knowledge spreads across the team, and the codebase stays consistent. When it doesn’t, pull requests sit for days, reviewers argue about formatting, and authors learn to dread …
Application Secret Management: How to Implement a Good Secret Management Strategy
Sometimes bad things just happen, or perhaps they happen because of our neglect. Bad things like committing an application secret into our repository. The problem with doing that is that if that happens, deleting the secret and committing will not suffice. We need to purge that commit completely from our repository and its history. But …
Code Review Best Practices: A Short Guide
Code review is an essential part of development workflow. It can have a big impact on the quality of our code and the delivered result. So, it’s important to make sure it is done correctly. Code review is one of those tools that have a high return on investment. So many companies invest in building …
