<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scott Berrevoets - blog</title><link>https://scottberrevoets.com/</link><description/><atom:link href="https://scottberrevoets.com/feeds/blog.rss.xml" rel="self"/><lastBuildDate>Fri, 20 Mar 2026 00:00:00 -0700</lastBuildDate><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>blog</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>blog</category></item><item><title>Scaling my git/tmux workflows for AI agents</title><link>https://scottberrevoets.com/2026/02/17/scaling-my-gittmux-workflows-for-ai-agents/</link><description>&lt;p&gt;After I started to ramp up on agentic coding, I found my workflow lagging behind
how I ended up working. Previously I would clone my project's repo twice and
switch back and forth between the clones. I used stack-based git workflow
&lt;a href="https://github.com/keith/git-pile"&gt;git-pile&lt;/a&gt;, which eliminated the overhead of switching branches and …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Tue, 17 Feb 2026 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2026-02-17:/2026/02/17/scaling-my-gittmux-workflows-for-ai-agents/</guid><category>blog</category></item><item><title>Localization troubles with Swift PM</title><link>https://scottberrevoets.com/2025/09/19/localization-troubles-with-swift-pm/</link><description>&lt;p&gt;A few weeks ago we got bit by a piece of Apple magic in its localization
workflow when combined with Swift PM. The problem we ran into was that as soon
as we moved all our &lt;code&gt;Localizable.strings&lt;/code&gt; files to an SPM package, none of the
localizations would be picked …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Fri, 19 Sep 2025 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2025-09-19:/2025/09/19/localization-troubles-with-swift-pm/</guid><category>blog</category></item><item><title>Managing code deprecations on iOS</title><link>https://scottberrevoets.com/2025/08/20/managing-code-deprecations-on-ios/</link><description>&lt;p&gt;A great manager I once worked with had been at Google for a while and poked fun
at an aspect of its engineering culture: any given service was either deprecated
or not yet ready for adoption. I spend a lot of my time working on mobile
platform development and over …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Wed, 20 Aug 2025 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2025-08-20:/2025/08/20/managing-code-deprecations-on-ios/</guid><category>blog</category></item><item><title>Flywheel of tech debt</title><link>https://scottberrevoets.com/2025/07/02/flywheel-of-tech-debt/</link><description>&lt;p&gt;Tech debt is often compared to financial debt, in that you're borrowing
development time now to pay it off with more development time later. When
"later" comes around, the development time needed to fix the issues introduced
earlier is too high so the new thing is also not built "correctly …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Wed, 02 Jul 2025 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2025-07-02:/2025/07/02/flywheel-of-tech-debt/</guid><category>blog</category></item><item><title>Art of the state</title><link>https://scottberrevoets.com/2025/06/02/art-of-the-state/</link><description>&lt;p&gt;&lt;code&gt;@State&lt;/code&gt; plays a prominent role in any SwiftUI app, and for good reason: app
state is what ultimately drives the UI and how the user interacts with your app.
This has always been true, but SwiftUI embraces this reality with specific APIs
and a unidirectional data flow. UIKit-based apps or …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 02 Jun 2025 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2025-06-02:/2025/06/02/art-of-the-state/</guid><category>blog</category></item><item><title>Composing a resume in markdown</title><link>https://scottberrevoets.com/2025/03/15/composing-a-resume-in-markdown/</link><description>&lt;p&gt;I recently updated my resume, and after a few iterations of tweaking the same
Pages file I started more than a decade ago, I decided that I really wanted
source control to make it easier to keep track of changes and to have different
versions of the same resume. Additionally …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Sat, 15 Mar 2025 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2025-03-15:/2025/03/15/composing-a-resume-in-markdown/</guid><category>blog</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>blog</category></item><item><title>Looking up words in a dictionary with Neovim</title><link>https://scottberrevoets.com/2024/12/08/looking-up-words-in-a-dictionary-with-neovim/</link><description>&lt;p&gt;When writing code in neovim, I frequently use &lt;code&gt;K&lt;/code&gt; to look up documentation,
function signatures, variable definitions, etc. In markdown files that doesn't
make too much sense, but I wanted to use it to look up words in the dictionary
instead. This didn't appear to be possible out of the …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Sun, 08 Dec 2024 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2024-12-08:/2024/12/08/looking-up-words-in-a-dictionary-with-neovim/</guid><category>blog</category></item><item><title>Shifting the testing culture: Code coverage</title><link>https://scottberrevoets.com/2024/11/20/shifting-the-testing-culture-code-coverage/</link><description>&lt;div class="admonition note"&gt;
&lt;p class="admonition-title"&gt;Note&lt;/p&gt;
&lt;p&gt;This is the third post in a series on shifting our testing culture.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href="https://scottberrevoets.com/2024/11/18/shifting-the-testing-culture-motivation/"&gt;Motivation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://scottberrevoets.com/2024/11/19/shifting-the-testing-culture-infrastructure/"&gt;Infrastructure&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Code coverage&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;
&lt;p&gt;Most people will say that code coverage is a measure of how well-tested your
code is. I prefer to say it's a measure of how &lt;em&gt;untested&lt;/em&gt; a codebase is. Take
this example …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Wed, 20 Nov 2024 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2024-11-20:/2024/11/20/shifting-the-testing-culture-code-coverage/</guid><category>blog</category></item><item><title>Shifting the testing culture: Infrastructure</title><link>https://scottberrevoets.com/2024/11/19/shifting-the-testing-culture-infrastructure/</link><description>&lt;div class="admonition note"&gt;
&lt;p class="admonition-title"&gt;Note&lt;/p&gt;
&lt;p&gt;This is the second post in a series on shifting our testing culture.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href="https://scottberrevoets.com/2024/11/18/shifting-the-testing-culture-motivation/"&gt;Motivation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Infrastructure&lt;/li&gt;
&lt;li&gt;&lt;a href="https://scottberrevoets.com/2024/11/20/shifting-the-testing-culture-code-coverage/"&gt;Code coverage&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;
&lt;p&gt;This second article goes a bit deeper into the testing infrastructure we built
over the years to optimize the ergonomics and developer experience as much as
possible.&lt;/p&gt;
&lt;p&gt;Our initial test suites only …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Tue, 19 Nov 2024 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2024-11-19:/2024/11/19/shifting-the-testing-culture-infrastructure/</guid><category>blog</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>blog</category></item><item><title>Migration strategies in large codebases</title><link>https://scottberrevoets.com/2022/11/15/migration-strategies-in-large-codebases/</link><description>&lt;p&gt;Code migrations are a fact of life for large codebases. New technologies pop up,
platforms see improvements, and programming languages get new features you might
want to adopt. Not performing these migrations and keeping up with the times is
simply not an option in most cases. While some migrations are …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Tue, 15 Nov 2022 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2022-11-15:/2022/11/15/migration-strategies-in-large-codebases/</guid><category>blog</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>blog</category></item><item><title>Third-party libraries are no party at all</title><link>https://scottberrevoets.com/2022/07/15/third-party-libraries-are-no-party-at-all/</link><description>&lt;p&gt;&lt;em&gt;What better way to end the week than with a hot take?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In my 8 years at Lyft, product managers or engineers have often wanted to add
third-party libraries to one of our apps. Sometimes it’s necessary to integrate
with a specific vendor (like PayPal), sometimes it’s to …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Fri, 15 Jul 2022 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2022-07-15:/2022/07/15/third-party-libraries-are-no-party-at-all/</guid><category>blog</category></item><item><title>iOS Architecture at Lyft</title><link>https://scottberrevoets.com/2021/10/14/ios-architecture-at-lyft/</link><description>&lt;p&gt;June 30, 2014 was my first day at Lyft as the first iOS hire on the ~3 person
team. The app was written in Objective-C, and the architecture was a 5000-line
nested switch statement.&lt;/p&gt;
&lt;p&gt;Since then, the team has grown to about 70 people and the codebase to 1.5M …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Thu, 14 Oct 2021 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2021-10-14:/2021/10/14/ios-architecture-at-lyft/</guid><category>blog</category></item><item><title>Re-binding self: the debugger's break(ing) point</title><link>https://scottberrevoets.com/2018/08/08/re-binding-self-the-debuggers-breaking-point/</link><description>&lt;p&gt;&lt;strong&gt;Update 07-29-2019: The bug described below is fixed in Xcode 11 so this blog
post has become irrelevant. I'm leaving it up for historical purposes.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;For the Objective-C veterans in the audience, the strong-self-weak-self dance is
a practice mastered early on and one that is used very frequently. There are …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Wed, 08 Aug 2018 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2018-08-08:/2018/08/08/re-binding-self-the-debuggers-breaking-point/</guid><category>blog</category></item><item><title>Using Interface Builder at Lyft</title><link>https://scottberrevoets.com/2017/03/06/using-interface-builder-at-lyft/</link><description>&lt;p&gt;Last week people realized that Xcode 8.3 by default uses storyboards in new
projects without a checkbox to turn this off. This of course sparked the
Interface Builder vs. programmatic UI discussion again, so I wanted to give some
insight in our experience using Interface Builder in building the …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 06 Mar 2017 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2017-03-06:/2017/03/06/using-interface-builder-at-lyft/</guid><category>blog</category></item><item><title>Keeping the Lyft iOS App Accessible</title><link>https://scottberrevoets.com/2017/01/18/keeping-the-lyft-ios-app-accessible/</link><description>&lt;div class="admonition note"&gt;
&lt;p class="admonition-title"&gt;Note&lt;/p&gt;
&lt;p&gt;This article was written by me but originally published on the &lt;a href="https://eng.lyft.com/keeping-lyft-accessible-53155f0098b9"&gt;Lyft
Engineering Blog&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;At Lyft we’re in a unique position: every day we work on an app that affects
people in the real, physical world — not just the digital one. This has an
especially large impact on …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Wed, 18 Jan 2017 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2017-01-18:/2017/01/18/keeping-the-lyft-ios-app-accessible/</guid><category>blog</category></item><item><title>Silencing NSLog</title><link>https://scottberrevoets.com/2016/08/01/silencing-nslog/</link><description>&lt;p&gt;When your app has a lot of third-party dependencies, what often happens is that
those libraries log a bunch of things to the Xcode console to help their own
debugging. Unfortunately, a lot of these logs are useful only to the developers
of the library, but not the developers of …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 01 Aug 2016 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2016-08-01:/2016/08/01/silencing-nslog/</guid><category>blog</category></item><item><title>Outlets: strong! or weak?</title><link>https://scottberrevoets.com/2016/03/21/outlets-strong-or-weak/</link><description>&lt;p&gt;There are a lot of styles out there when it comes to using Interface Builder
outlets in Swift. Even Apple's documentation and sample code isn't always
consistent. The most common one, the one Apple uses in its sample code, follows
this pattern:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;@IBOutlet private weak var someLabel: UILabel!&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;Let's break …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 21 Mar 2016 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2016-03-21:/2016/03/21/outlets-strong-or-weak/</guid><category>blog</category></item><item><title>@objc class prefixes fixed in Xcode 7 beta 4</title><link>https://scottberrevoets.com/2015/07/23/objc-class-prefixes-fixed-in-xcode-7-beta-4/</link><description>&lt;p&gt;Back in December I &lt;a href="/2014/12/15/at-objc-creates-a-wrong-class-name-in-objective-c/"&gt;wrote&lt;/a&gt; about what I thought was a bug in the Swift compiler that would expose the wrong class name for a Swift class in Objective-C. I then later &lt;a href="https://devforums.apple.com/message/1072175#1072175"&gt;found out&lt;/a&gt; everything worked as intended and I had just misunderstood what &lt;code&gt;@objc()&lt;/code&gt; exactly did. Apparently it was …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Thu, 23 Jul 2015 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2015-07-23:/2015/07/23/objc-class-prefixes-fixed-in-xcode-7-beta-4/</guid><category>blog</category></item><item><title>The power of UIStackView</title><link>https://scottberrevoets.com/2015/06/13/the-power-of-uistackview/</link><description>&lt;p&gt;I was in the audience for "Implementing UI Designs in Interface Builder" at WWDC, where Apple touted &lt;code&gt;UIStackView&lt;/code&gt; as a new, better way to lay out your views that in a lot of cases didn't require Auto Layout.&lt;/p&gt;
&lt;p&gt;While the presentation looked good, I wasn't quite sure this solved a …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Sat, 13 Jun 2015 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2015-06-13:/2015/06/13/the-power-of-uistackview/</guid><category>blog</category></item><item><title>@objc creates a wrong class name in Objective-C</title><link>https://scottberrevoets.com/2014/12/15/objc-creates-a-wrong-class-name-in-objective-c/</link><description>&lt;p&gt;A few months ago, I decided I'd get started porting &lt;a href="https://github.com/sberrevoets/SDCAlertView"&gt;SDCAlertView&lt;/a&gt; to Swift, but I was only a few minutes in until I ran into a problem I had no idea how to solve: I couldn't get my class names right in both Swift and Objective-C. Even though there are …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 15 Dec 2014 00:00:00 -0800</pubDate><guid>tag:scottberrevoets.com,2014-12-15:/2014/12/15/objc-creates-a-wrong-class-name-in-objective-c/</guid><category>blog</category></item><item><title>Dev-only iPhones</title><link>https://scottberrevoets.com/2014/10/20/dev-only-iphones/</link><description>&lt;p&gt;With today's release of iOS 8.1, most app developers are looking at 4
significantly different iOS versions they will be supporting: iOS 7.0, iOS 7.1,
iOS 8.0, and iOS 8.1. Factoring in the number of devices (iPhone 4S, iPhone 5,
iPhone 5s, iPhone 6, and …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 20 Oct 2014 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2014-10-20:/2014/10/20/dev-only-iphones/</guid><category>blog</category></item><item><title>UIMenuController and the responder chain</title><link>https://scottberrevoets.com/2014/09/15/uimenucontroller-and-the-responder-chain/</link><description>&lt;p&gt;The responder chain is a very important paradigm in the world of iOS development, and not terribly hard to understand. Dozens of articles have been written about it, and with some examples, the concept of finding a responder to a certain event by traversing a chain of potential responders is …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Mon, 15 Sep 2014 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2014-09-15:/2014/09/15/uimenucontroller-and-the-responder-chain/</guid><category>blog</category></item><item><title>Xcode &amp; Objective-C Oddities</title><link>https://scottberrevoets.com/2014/08/10/xcode-objective-c-oddities/</link><description>&lt;p&gt;Any developer that has worked with Xcode to write a little more than just "Hello, World" knows that Xcode and Objective-C have their quirks. Chances are you have heard of &lt;a href="https://twitter.com/TextFromXcode"&gt;@TextFromXcode&lt;/a&gt;, the Twitter handle that portrays Xcode as a high school bully in fake text conversations like this:&lt;/p&gt;
&lt;p&gt;&lt;img alt="Xcode Bully" src="https://cl.ly/image/0I2P191S0Q2k/20140227.PNG"&gt;&lt;/p&gt;
&lt;p&gt;But it's …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Sun, 10 Aug 2014 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2014-08-10:/2014/08/10/xcode-objective-c-oddities/</guid><category>blog</category></item><item><title>Objective-C prefixes: a thing of the past?</title><link>https://scottberrevoets.com/2014/07/25/objective-c-prefixes-a-thing-of-the-past/</link><description>&lt;p&gt;This past week, there was, again, a lot to do about Objective-C and prefixing. To most iOS developers, the story sounds familiar: one camp is strongly in favor, another camps is strongly against, and a third camp couldn't really care less.&lt;/p&gt;
&lt;p&gt;Unless I'm unaware of any other platforms where the …&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scott Berrevoets</dc:creator><pubDate>Fri, 25 Jul 2014 00:00:00 -0700</pubDate><guid>tag:scottberrevoets.com,2014-07-25:/2014/07/25/objective-c-prefixes-a-thing-of-the-past/</guid><category>blog</category></item></channel></rss>