Agile
The reason I got into programming as a teenager was because of video games. I mean, I always liked computers generally–I was fortunate to grow up in the Cupertino area, and my dad was a software developer who would build random computers for my brother and I out of
Agile
Last year our team decided to start documenting a list of our pain points as developers. We created a spreadsheet with columns for the original reporter, a quick description, and a pain rating on scale of 1-10 of how bad it hurts. We started to review the the document weekly
Design
It’s that time again… monolith vs microservices architecture debate on twitter! What better time to throw my hat into the ring and scream my raw, non-peer-reviewed thoughts into the void? Like all patterns, implementing a microservices architecture pattern is a transaction that exchanges one set of problems for a
Swift
JSON in Swift 4 and Open Source Thoughts Swift 4 brings a cornucopia of welcome (and a few unwelcome) updates. One of the ones I am excited about is the introduction of Codable. As the owner of a popular open source JSON mapping framework, I really look forward to Codable
Swift
A Love Story Last time we talked about some pretty cool stuff we can do to build a more reactive iOS application using the Reactor architecture. Today we’ll investigate how we can keep in sync with data from the network and make our app faster with the power of
Swift
Making your Swift app more React Nativey Confessions I’m going to let you in on a dirty little secret. Sometimes I think longingly about React Native. I know, I know. Feels so wrong. But some of it feels so right. Reactive, declarative UI code? Hot reloading? Updates that can
Refactoring
Enums in Swift are great—love me some sweet, sweet enums. However, as with all great things, one can go too far. Let’s look at the following contrived example: I’ve seen a lot of enums like this. Well, not animals maybe. But you know what I mean. Let’
Swift
Previously we explored how to use Swift’s amazing type system to simplify our JSON code. We came up with a solution that was concise, without building a complicated tree of JSON enums, using crazy operators, or getting deep into reflection. And we did it all in 100-some-odd lines of
MacOS
Long has the holy war between emacs and vi been waged. I’ve used both, and I don’t really care either way. However, OS X text fields everywhere come with secret support for limited (and sometimes modified) Emacs keybindings. So, regardless of your position in the great text editor
Swift
Last time we talked about how we could simplify our JSON parsing with Swift 2 error handling and get rid of all the magic. Today we’re going to use the power of type inference to take our old JSONObject struct from having 12 methods (or more, if you want
Swift
Swift 2.0 is causing a lot of well deserved excitement. Chris and the folks over at apple have been doing an amazing job. I have been loving Swift the past year and am really excited about all the new features—and, of course, the open source announcement. When the
Swift
The forward pipe operator is an infix operator taken from languages like F# and Elixir. I've been working on a Swift implementation that will help clean up data processing pipelines. In order to understand the motivation for the forward pipe operator, let's first look at some