https://owenps.github.io/Recent content in Home on Owen SmithHugoen-usTue, 12 Aug 2025 20:44:44 -0400https://owenps.github.io/read-list/Tue, 12 Aug 2025 20:44:44 -0400https://owenps.github.io/read-list/I spend a lot more time reading than writing. There are a lot of incredible people and resources that inspired me everyday. Here are some of my personal favourites. Read List 2026 [Video] Mario Zechner - Building pi in a World of Slop 2025 [Article] Logging Sucks [Guide] Tiger Style [Article] Conventional Comments [Article] Martin Fowler - Microservices [Article] Ludwig Abap - On becoming competitive when joining a new companyhttps://owenps.github.io/contact/Mon, 11 Aug 2025 22:07:21 -0400https://owenps.github.io/contact/Always happy to chat and discuss projects. My accounts on other sites ledge.io/owen letterboxd.com/owenps linkedin.com/in/owenpsmith github.com/owenps x.com/owenps_https://owenps.github.io/blog/the-150-150-rule/Sat, 28 Jun 2025 12:31:43 -0400https://owenps.github.io/blog/the-150-150-rule/The “Rule” The 150-150 CR (a.k.a ‘A Code Review A Day’) Rule is a development philosophy at Amazon that helps teams ship code faster and at a higher quality. The rule is that each code review (CR) is at most 150 lines of changes to source code and 150 lines of changes to test code. The guidline recommends: Limiting total changes per CR to 150-150 lines or fewer. Submitting at least one 150-150 CR a day.