I had a project idea a month or so ago when I was part of a group planning some holidays. We were booking flights and accomodations, but the confirmation emails only went to the account of the person that actually made the booking. So I thought, wouldn’t it be nice if we could all get those emails? Well, some services do allow submitting multiple contact email addresses or adding “guests” to a booking, but not all of them do.
I’ve fallen behind on my daily blog post initiative, but oh well. It turns out that I don’t really have time to write a good blog post every day. But at least this time I have a good excuse, because I was busy swimming in the ocean (and it was awesome). “Serverless” computing is a new-ish paradigm with many use cases. I tend to use it for anything that I can lately, since I never have to worry about uptime and I also don’t have to pay for it (my projects stay small enough to live within the free tier—especially with the growing number of providers these days).
I’m a day late again, but this post took quite a while and ended up more detailed than I intended my daily posts to be, so this counts for two. At least, it does until I get inspired and write two posts in one day (this weekend is a long weekend, so don’t be surprised). The website that you’re reading is pretty new. It’s also the first website I’ve ever hosted (excluding via GitHub Pages), and I learned a lot about how the Internet works while getting everything online.
CircleCI is a continuous integration platform similar to Travis CI. You can run your tests on it, save artifacts, deploy software, etc. I’ve found that it offers a number of advantages over Travis: Faster builds Custom Docker image support Local build support Less magic Faster Builds CircleCI builds boot nearly instantly, which I don’t usually get from Travis. The actual speed of the build is roughly the same from what I can tell, but the quick startup is really valuable to me.
I’m kind of obsessed with trying out new programming languages, but it doesn’t feel very productive. Eventually, I’d like to find something that fits just right for the type of programs that I like to write, and get really good at it. That hypothetical perfect language should be/have most of these things, in rough order of priority: Good tooling/development workflow Coherent type system Easy to deploy Simple package management Expressions over statements Multiple dispatch Macro system Tooling/Development Workflow