As a new dev, I needed a process for reviewing pull requests that allowed me to feel confident. Here are four questions I ask for every PR I review.
One of my favorite tips for making pull request reviews more useful, efficient, and enjoyable is Github's "Saved replies."
Following a process like the Scientific Method can help maintain your sanity during those seemingly hopeless searches for software bugs and broken code.
While pair programming, having an engaged navigator can prevent the driver from wasting time on pesky syntax errors or little logic errors.
Developer applicants generally have to complete a coding challenge. But who does the reviews for the code submissions, and how do they do it?
Software developers can apply empathy in many ways. But I’m going to focus on utilizing empathy when reading others' code.
A new perspective on old code can help spur refactoring that will not only make the app more usable, but will also make it a better environment for makers.