I’m looking for a free, lightweight project management tool--something to track tasks, bugs, and priorities as I develop an app.

My first go at developing requirements for a mobile application.

Apply a tailored “ready for review” checklist to ensure a PR is in a state where detailed code review will be productive.

Tests should be included in the same pull request as the code changes they test; this provides verification, eliminates risk, and guarantees no-fuss rollbacks.

Here are the slides and transcript for a talk I gave at a Meetup event on April 22 2025.

When a PR can’t be small, it’s on the author to keep it reviewable—because reviewable PRs lead to better code.

For an effective and efficient code review, focus on understanding the problem, gathering context, and ensuring basic functionality.

When approaching a code review, determine whether the pull request is reviewable before diving into the actual code.

As much as I'd like a portfolio app, I won't release something if a solid app that does the same thing already exists.

For years, I've wanted to create my own iOS app and get it on the App Store. After 12 years as an iOS developer, I'm finally doing it!

Early code reviews, when used thoughtfully and aided with clear communication, save time and improve team morale.

After I submit a PR for review, it remains my top priority until it's fully integrated into the codebase.

In this post, I share five key techniques that help make my PRs a pleasure to review.

Software development teams can save time and avoid frustration by establishing a shared definition of "ready for review."

Every software developer should establish their own definition of 'ready for review.' Doing so will help them produce high-quality output.