<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scott Berrevoets - Engineering Culture</title><link>https://scottberrevoets.com/</link><description/><atom:link href="https://scottberrevoets.com/feeds/engineering-culture.rss.xml" rel="self"/><lastBuildDate>Mon, 05 Oct 2026 00:00:00 -0700</lastBuildDate><item><title>Why big companies are bad platform citizens</title><link>https://scottberrevoets.com/2026/10/05/why-big-companies-are-bad-platform-citizens/</link><description>&lt;p&gt;In the fall, when Apple releases new iPhones and major iOS versions, small/indie
developers take a lot of pride in being ready for this new tech on day 1. They
spend all summer learning new APIs and development tools, and integrate them in
their apps so their users can …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 05 Oct 2026 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2026-10-05:/2026/10/05/why-big-companies-are-bad-platform-citizens/</guid><category>Engineering Culture</category><category>Technology Adoption</category><category>Engineering Culture</category><category>Technical Debt</category></item><item><title>Review your own AI-generated code</title><link>https://scottberrevoets.com/2026/03/20/review-your-own-ai-generated-code/</link><description>&lt;p&gt;Years ago, when we started to have 5+ contributors to our codebase at Lyft, we
had to establish a code review process with high enough value to justify the
friction it caused. However, "value" is very subjective, as not everyone cares
about the same qualities of a pull request:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Catching …&lt;/li&gt;&lt;/ul&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Fri, 20 Mar 2026 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2026-03-20:/2026/03/20/review-your-own-ai-generated-code/</guid><category>Engineering Culture</category><category>Developer Experience</category><category>Engineering Culture</category></item><item><title>All in on Interface Builder: 10 years later</title><link>https://scottberrevoets.com/2026/03/02/all-in-on-interface-builder-10-years-later/</link><description>&lt;p&gt;Back in 2017, I wrote about how we used &lt;a href="https://scottberrevoets.com/2017/03/06/using-interface-builder-at-lyft/"&gt;Interface Builder&lt;/a&gt; as our primary way
of building UI at Lyft. Interestingly, Speak chose to use Interface Builder to
build UI too before SwiftUI came along, though without the same tooling we had
at Lyft. With Interface Builder mostly forgotten, including …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 02 Mar 2026 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2026-03-02:/2026/03/02/all-in-on-interface-builder-10-years-later/</guid><category>Engineering Culture</category><category>Technology Adoption</category><category>Technical Debt</category></item><item><title>Incremental complexity in iOS development</title><link>https://scottberrevoets.com/2025/02/03/incremental-complexity-in-ios-development/</link><description>&lt;p&gt;I wrote my first app, a map to navigate my college campus, in the winter of
2011, on iOS 4.x and with Xcode 4.x. There were 25 frameworks, iOS 7 hadn't been
invented yet, there was only 1 phone size, and we wrote apps with Objective-C.&lt;/p&gt;
&lt;p&gt;But things …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 03 Feb 2025 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2025-02-03:/2025/02/03/incremental-complexity-in-ios-development/</guid><category>Engineering Culture</category><category>Platform Engineering</category><category>Developer Experience</category><category>Engineering Culture</category></item><item><title>Shifting the testing culture: Motivation</title><link>https://scottberrevoets.com/2024/11/18/shifting-the-testing-culture-motivation/</link><description>&lt;p&gt;Five years ago I began promoting automated testing heavily within Lyft even
though I didn't have any real experience in writing big test suites myself. Many
hands make light work, so I found a few people who shared this thinking and we
started on what turned out a multi-year testing …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 18 Nov 2024 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2024-11-18:/2024/11/18/shifting-the-testing-culture-motivation/</guid><category>Engineering Culture</category><category>Testing</category><category>Engineering Culture</category></item><item><title>Human factors in choosing technologies</title><link>https://scottberrevoets.com/2022/09/28/human-factors-in-choosing-technologies/</link><description>&lt;p&gt;I recently saw a thread where someone wanted to introduce a more capable
architecture pattern than what most apps start out with in a small team, but
received some pushback from teammates and was looking for help in countering
their arguments.&lt;/p&gt;
&lt;p&gt;The thread for the most part focused on the …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Wed, 28 Sep 2022 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2022-09-28:/2022/09/28/human-factors-in-choosing-technologies/</guid><category>Engineering Culture</category><category>Technology Adoption</category><category>Engineering Culture</category></item></channel></rss>