Swift Memoization This post comes from this tweet shared by David Rodrigues (if you don't follow him on Twitter you should): If you have a closure that needs some internal state to be used and
ReactiveSwift RAS S2E1 In this post we will see why a SignalProducer is more suitable for a particular task than a Signal.
ReactiveSwift Parents and children problems 😅 If you follow me on twitter, you have been spammed these last days with a particular problem I have been tackling. It all started with this: I have a feeling that the way
Management On being an Engineering Manager In this post I will share what I learned throughout the last year (2017) as a engineering manager of 10 people and how it has impacted me, as a professional. A manager should
MVC MVC. A lot has been said in the last years about MVC and its problems and how to tackle them.[1] Lately two posts (or series) in particular caught my attention: Much ado about
ReactiveCocoa RAS S1E4 Flatmap is one of those ubiquitous operators that, independently of your expertise level, will be present in your day-to-day work with ReactiveSwift. In this post I will talk about how we can leverage
ReactiveCocoa RAS S1E3 As a ReactiveSwift user myself, a lot of times, it's difficult to decide which operator to use. In this post I will share some of the mental process I go through when picking
Functional Programming map versus flatMap Note: The goal of this post is to give the reader an intuition about the usage of a map versus a flatMap, instead of playing around with return types of each operation, until
iOS demo project checklist ✅ Note 1: This post is not to hack your way through the interview process, but to avoid situations where you might put 10h of work, to just be rejected by a small mistake.
iOS RAS S1E2 A tale of composition 🌳 In my mind there are two ways of thinking about composition, when we have FRP or FP in the mix. The first one is often mentioned when compared to
ReactiveCocoa RAS S1E1 Note: this will be a series of posts about ReactiveSwift. When explaining ReactiveSwift, I tend to go away from FRP entirely and linger into familiar concepts, like the Optional type. The problem, is
year-review 2016 in review Working at the MailOnline was a great experience and it was the longest I ever been in a company based in the UK. The time there gave me the opportunity to enhance my
Swift Cakes and ViewModels A talk that I think went fairly unnoticed, by Jon Sterling, entitled "Modularity à la Taliban" stated the following: A ViewModel should only be created by another ViewModel. [1] With this
Bias After releasing the post ReactiveCocoa vs RxSwift, some people (which I deeply respect) were/are quite unhappy with me. More specially with the tone I used to talk about RxSwift and my bias
ReactiveCocoa Younger self What I wish I could tell my younger self about FRP (from a RAC perspective): Before diving into FRP, start using functional aspects that Swift gives you for free. Like: map, flatMap, filter,
iOS Cells and ViewModels With MVVM, each cell will have its own ViewModel from where it will get the necessary data it needs. That's pretty sweet, until you have to dequeue a cell: So, what's the identifier?
iOS Why FRP? So today I wrote this on Twitter: People still think that Reactive libs/frameworks are just an enhanced KVO. #2016— Rui Peres (@peres) January 7, 2016 Part 1 And I got some
ReactiveCocoa Schedulers When you think about ReactiveCocoa, one immediately thinks about Signals, streams of events and transformations. Although that's all there, RAC is more than meets the eye. Lately I had to do the following:
On benchmarks A lot of people pointed out that they didn't really understand what was the point of this. Or what does it actually mean. The main job of a lib of this nature is:
#3 Diary of a Secret App: JSON Parsing Intro If you follow me on twitter you must have seen my most recent rant: Argo vs JSON Parsing "by hand" with +1M objects. Argo -> 3.05s | "by
iOS #2 Diary of a Secret App: AutoLayout I had a rough battle with AutoLayout these days[1]. The following notes are in the context of a UITableView with dynamic sizing cells. : If you want to change an UITableViewCell's layoutMargins, don't
iOS Generic UIViewControllers Update 1/09/2015: Code tested on Xcode 7.0 beta 5 (7A176x) Note: Kudos to Robert for lending me his brain in some of this decisions. Context Imagine you want to display
Swift Bye Storyboards Storyboards are awesome and if I was doing Objective-c, I would probably still be using them. But the thing with Swift and Storyboards, is that it shows that there is still some friction
Rant Juggling Junior Engineer: Creates complex solutions to simple problems Engineer: Creates simple solutions to simple problems. Senior Engineer - Creates simple solutions to complex problems. Rockstar Engineer - Makes complex problems disappear. (taken from
Swift Monads Note: This is an exploratory post, where I will write about some ideas that are still fresh in my mind and need consolidation. Any mistake, lack of objectivity/rigor, that you find, please