I wrote a prototype of a tool to “declare bankruptcy” on your Sqitch migrations and start over. If you have a project with 50, 100, or more migrations, this might be useful for you. The details are in the blog post I wrote on the ActiveState blog.
I’ve recently been puttering about attempting to write a Postgres SQL & PL/pgSQL tidier in Rust called pg-pretty. If you’ve always wanted such a thing, don’t get too excited. It isn’t even close to usable yet. But this post is about Perltidy and Black. These are both source code tidiers (aka formatter aka pretty printers). Black is for Python. These two tidiers reflect their respective languages. Perltidy is all about TIMTOWTDI1 and Black is very much a TOOWTDI2 project.
I’ve now moved all of my sites from my Linode box to Render. This includes: This blog - Uses Hugo. Repo houseabsolute.com - Contains my resume and links to conference slides. Also uses Hugo. Repo presentations.houseabsolute.com - A new hostname for my slides. See below for more details. Repo masonbook.houseabsolute.com - Just a static site. Repo vegguide.org - Just another static site. Repo I really like Render! It’s incredibly easy to use.
Many, many years ago, in the flower of my youth (June, 1999), I registered the urth.org domain. I can’t remember when I started hosting my own email, but it was around that time. For many years after, I had a server in my home that hosted my email, various websites, and some web applications. Eventually VPS’s became cheap and powerful enough that I ditched the home server and moved everything to the cloud (Linode, specifically).
Like so many conferences this year, RustConf 2020 was a purely virtual event. I’d already helped organize and attended The Perl Conference in the Cloud 2020 as a virtual conference earlier this year, so I knew it could work. RustConf was very different from The Perl Conference. It was just one day and one track, lasting about five and a half hours with a break in the middle. The conference schedule was incredibly detailed.
Edit: I’m now up to a 0.11 trial release. Please test that one instead. I just did a trial release of this distro. It doesn’t contain any radical changes, but I did enough tweaking to the internals that I think it’s best to make a trial release. If I don’t get any bug reports in the next few weeks I will do a non-trial release some time in August.
I will be offering my Introduction to Go class at this year Perl & Raku Conference in the Cloud. The cost is just $50, with all proceeds going to The Perl Foundation. You can register for this class using Eventbrite. This year I have the class capped at just 10 people, because this is my first time doing this online. I’ve found an online classroom solution that allows all attendees to share their screens simultaneously, so I’ll be able to virtually look over your shoulder while you’re working on the exercises .
What’s a code quality meta tool? It’s a tool that lets you orchestrate many linting and formatting tools to operate on an entire project which may contain many languages. Examples include tidyall (which I maintain), pre-commit, lefthook, husky, overcommit, and precious (my new project in this space). It’s worth noting that only tidyall and precious describe themselves as being focused on tool orchestration. The others all describe themselves as systems for managing Git hooks.
One of my favorite bloggers, Scott Alexander of Slate Star Codex, regularly publishes predictions for the year. Here are his predictions for 2020. I thought it’d be fun to make some predictions of my own, following the same rules and a similar format. In 2021 I’ll rate my predictive success and maybe make some more predictions. Rules (copied from SSC): all predictions are about what will be true on January 1, 2021.
Sorry, couldn’t resist the pun. First, a bit of background. Tidyall (aka Code::TidyAll) was first released in June of 2012 by Jon Swartz. It’s a code quality meta-tool that orchestrates other code quality tools. With a single configuration file you can enable many different tools for a single project. By “code quality tools” I mean both pretty printers and linting tools. Each tool is supported via a plugin, implemented as a Perl class, that knows how to talk to that tool.