I have some apps written in Go, which I deliver as binaries for each platform using GitHub releases. Until now, I was doing it with a very simple shell script.
Watchub is a service that notifies you of people who followed/unfollowed you and starred/unstarred your repositories.
As a DevOps/SRE, I spent a reasonable amount of time dealing with metrics and alerts.
I have seen a lot of posts like this subject, but almost all of them were about stuff you should do and almost none of them reflected how I truly feel, how I want a product to be so I can “love” it.
Every now and then an active java-based project enters in a “dependency hell” state. That usually happens because people keep adding dependencies without checking what comes in transitively nor if that dependency is declared somewhere else already.
I’ve lost a considerable amount of time trying to bind those things together, so I decided to write this quick post about it, so others could also benefit from it.
This is the story on how I speed up my terminal load time.
booleans, right? What a wonderful piece of technology! They help us solve so many problems…
I’ve been wanting to write this for a long time, just to clarify my thoughts on the subject. Now, on vacations, I took a couple of days and finally did it. This is a personal opinion based on my personal experience and tons of books I have read, and I am not, by any means, the supreme holder of the true, so you will probably disagree with me at some point.
This is just a quick overview of how I did it in antibody’s homepage. The site has a very simple index.html plus a service that can discover and download the latest antibody version from GitHub releases. Not sure how relevant this is, but the service is written in Go. Currently, every commit pushed to the master branch of the site repo will be automatically pushed to production. There is no option to skip that.