A few months back I started a new challenge in Jumbo, accepting the role of Team Lead for the customer service teams. As a first action, I choose to dedicate most of the time to 1-on-1 meetings. There is one problem: I don't know how to have effective 1-on-1 meetings. Trying to improve, I kept asking myself: "What make a 1-on-1 meeting a great 1-on-1 meeting?".
During the refactoring work on the project I'm working for at Jumbo, went through many different changes and the first one was implementing a new networking layer. We decided to create an external library and make it open source: it was the perfect moment to try a new CI system. Long live Travis CI!
Today I decided to install the latest macOS Catalina because I wanted to start playing with the new SwiftUI framework. Everything seems working correctly, except third-party software.
At my current job, we needed to improve our code base and we started from the network layer. We wanted to create an open source library but a question was raised: how is the structure of an open source library?
Swift is a language that encourages the use of protocols: thanks to protocol extensions and protocol extension default implementation is possible to easily extend complex architectures, but how to test them?