AWS Lambda and Actix: easy conversion of small web apps into serverless

Tom Parker-Shemilt wrote “I’ve been idly considering the uses of serverless computing, and I’m still not convinced it’s worth it. I’ve used it before, mostly as a means to make things happen in response to AWS events, but the pattern everyone talks about is using them to run web apps, and I’m not fully convinced about that. However,…”

Elastic Beanstalk: The Struggle

Alexandra Orth wrote “Recently, I found myself tasked with modifying a bunch of AWS Elastic Beanstalk environments despite having little prior DevOps/AWS experience. For the subsection of developers that, like me, now find themselves in the wide world of deploying their own code, I’ll describe a couple of the problems that I faced and how I solved them.…”

Serialising Rust tests

Tom Parker-Shemilt wrote “I’m once again prodding the potboiler tests and a couple of the tests I was doing wanted to mess around with the shared database. This had the problem that multiple tests would collide with each other, as the default for Rust testing is to run everything in parallel. This is unusual, but good in many…”

A year with Bitbucket Cloud

Dickon Reed wrote “For the whole of 2018 we used Bitbucket Cloud to host a few git repositories on a project with around 40 developers working full time, creating 20000 commits. The service worked pretty well, though: We did end up spending some time developing extra checks and automation. We have concerns around the lack of service availability…”

Experiments in converting code from C to Rust

Tom Parker-Shemilt wrote “I’m quite fond of Rust (as a few blog posts on the topic may indicate), but one item I hadn’t really explored was replacing/rewriting existing C code bases in Rust. There’s a general joke about the general notion of “rewriting everything in Rust is of course always the right thing to do!” (Google “rust evangelism…”

Not all watchers are created equal (or how to make yak shaving useful)

Tom Parker-Shemilt wrote “I’ve been hacking around with a Clojurescript project recently, and it resulted in a certain amount of yak shaving when I found the watcher system I was using was eating a lot of CPU. On the one hand, yak shaving is bad, because you’re doing other things that aren’t the core task you’d originally meant…”

PSA: Many ways to manage your Python dependencies

Tom Parker-Shemilt wrote “Having recently learnt about a few more tools, I felt it was worth writing this post. It’s pretty much a PSA, and some of you may well have found most of these, but there are a lot of Python developers out there who haven’t, and the improvements when using some them are considerable, so it’s…”

By Image has "Wilse" lettered on it (part of the largely illegible text at lower left). That would be Anders Beer Wilse. Seattle Municipal Archives (Flickr: Construction of Cedar River Pipeline, 1900) [CC BY 2.0 (https://creativecommons.org/licenses/by/2.0)], via Wikimedia Commons

Setting up drone.io CI

Patrick Tschorn wrote “Drone.io for go I was recently asked to set up a CI server for one of our go projects and decided to try out drone.io 0.8. From my point of view, the two most attractive features of drone.io are that: the build is defined through a single .drone.yml file in the root directory of the…”

Bazel: Fast, Correct, Usable – choose two

Tom Parker-Shemilt wrote “I’d recently gotten reminded about Bazel, Google’s ‘boil the ocean‘ build system, and decided to give it a proper go. TL;DR – it’s not ready yet, and might not ever be, unless you’re willing to throw away everything else. I’m generally on the lookout for good build systems. Some of my colleagues are perfectly happy…”

How software systems learn

Ceri Storey wrote “As part of a recent LShift tech meet­ing, we watched the first episode of Stewart Brand’s series How Build­ings Learn, as a way to prompt dis­cus­sion on what it means for soft­ware sys­tems to be ‘liv­able’.”

Sked: merged calendars as a service

Tom Parker-Shemilt wrote “I have a little bit of an obsession with calendars, mostly generated ones via a variety of tools. I don’t do well with pen-and-paper for this sort of things, and one of these days I will write the Grand Unified Todo Manager To Rule Them All (which will also eat emails, Calendars and probably a…”

Supposedly a property test library

Ceri Storey wrote “Over the past few weeks, I’ve been in­spired to create a new prop­erty testing lib­rary for rust, very much in­spired by the work in hy­po­thesis. Why use sup­pos­i­tions over say, quickcheck? For one, this takes in­spir­a­tion from hy­po­thesis and theft. While it’s still in it’s early days, the gen­er­ator system (in­spired by hy­po­thesis’ gen­er­ators means…”