Sometimes in command line tools we want to perform some cleanup final task before the process is killed. To detect this scenario we can hook to unix signals like an interrupt and perform the needed work before existing from the process.
I’ve already mentioned how I moved tasks from Todoist to Bear but one of the missing pieces of the migration was some lists that I had on Reminders.
After having clear the requirements for a notes system and comparing different options I decided to give an honest try to Bear. Now, one of the first things I need to do is move the tasks from my current system, Todoist, into it.
After a long day of hard work I endup having many apps open. Xcode, Visual Studio Code, Simulators, the terminal… when it’s six o’clock I want to close everything work related instantaneously whiteout effort.
In the past few days the Swift community has been awoken again with the promise of a better way of using Swift for scripting, all thanks to swift-sh.
One small inconvenience of a static blog generator running without a CMS is that to create a new post in markdown you need to add manually the front matter in the top of the file. That’s why the first thing you should do after setting up your static site generator is to create a small script that automates the new post creation.
I’ve been always a big fan of productivity, time is gold. But funny enough, as many other people, we fall into the traps of being productive by just spending more time on looking for tools and solutions to be more productive. This is not a bad thing per se, but it can end up being. You may end up having a false sense of productivity because you improve your workflows and tools. But, in reality, the only thing that matters is the output of your work and, specially, your happiness.
One of the things I think is really important in any team is to keep track of the performance. Not to use it as ammo to blame individuals but to learn and have data to keep improving.
The other day, while I was writing a Swift script, I added an option to make it run continuosly so it could be on a server doing its job without stoping. for eva.
This is the second part of my posts about the sate of scripting with Swift. In the previous post I wrote about what I expect from a language toolset when writing scripts and where Swift still needs some improvements. In this post I want to do a quick overview of the libraries that I used to write the script.
In the past few days I’ve spend some time writing a little script in Swift and I thought it was a good time to revisit the state of the Swift ecosystem as a scripting language.
Last week I had to made some changes on the colors of the WorkAngel app. The colors of that app are retrieved through an object called ThemeColor (we have another for the fonts). That object is the concrete implementation of a Theme protocol that defines the names of all the different colors that the app needs.
When I wrote my srly script I thought on doing it in Swift, but at the end I decided to go with a well known scripting language, Ruby.
This weekend I wrote a little script that helped me to connect two of the main things that I do everyday: save things into the Safari Reading List and watch Youtube videos offline.
For those who don’t know me I have to say that I’m a big fan of Minecraft (1 and 2). And I’ve always wanted to connect the things that happen in that virtual world with the things in our real world (and other people have done great things; House light sync, controlling a Christmas tree. Now that I have one of the pieces of the puzzle I am available to do it, so this morning I started writing some code and in a couple of hours I accomplished my objective.