Having a good process to update your tools is very important, specially for those that affect directly your code. I’ve talked about how I update swiftformat and this post will discuss my update process for SwiftLint.
Talking about how one updates a tool may seem a bit nonsensical, after all, what dificutlies can you have when updating a tool? Well, you would be surprised! But no, this post is not about issues when updating swiftformat. Quite the opposite!
At the iOS team at Lifeworks we’ve been using Danger since its inception. We care about the etiquette of our PRs and the more that can be automated the better.
Make is one of those tools that I’ve always been curious about but never had a good change to try it until a couple of years ago. It is a really powerful and convenient tool and in all honesty I just use it as a task runner, I define some names for a set of commands and run them that way.
This post is just a dump of the things that came to mind while watching Jonathan Blow’s libraries discussion. I’m not an expert on any of this but I find it so fascinating that my mind can stop thinking and taking notes when watching Jon streams.
I’ve always been fascinated by the culture behind dotfiles, those files that people have automated to be installed on a new computer to have everything set up just the way they want. Configuration for development programs, terminal settings, aliases, colors… But the truth is that I’ve only seen all of this from afar. I was very interested, but all these kinds of things come from necessity, and I’ve never had this necessity—until now.