The highlight of all this is my brand new GitHub Action for cross-compiling Rust projects. The rest of the post is about why and how I wrote it. I was recently working on the CI setup for my ubi project with a couple goals. First, I wanted to stop using unmaintained actions from the actions-rs organization. Second, I wanted to add many more release targets for different platforms and architectures1.

This is probably obvious to anyone paying attention to my CPAN releases over the past few years, but in case it’s not, I wanted to state this clearly. All of my Perl modules are in maintenance mode. Why? I no longer do any professional work with Perl, and I haven’t done any since 2017 or so. All of my most enjoyable personal projects are in Rust these days. Also, I’m a bit burned out on the Perl community.

I just released version 0.4.0 of precious, my code quality meta-tool for configuring a collection of linters and tidiers for a project. The headline change for this release is that command invocation configuration has changed, with the old run_mode and chdir keys being deprecated. Don’t worry, you can safely upgrade to this release, as the old config keys still work and do not cause precious to emit any warning yet1.

My team at MongoDB is hiring a senior engineer. For this position you can be 100% remote or you can choose to work from one our offices. I’ve been at MongoDB since May of this year and so far it’s been great. If you have questions about the position, the team, or working at MongoDB, please reach out.

A while back I was looking at the output from my GitHub profile generator and it seemed off. In particular, the language stats seemed off. The generator sums up how many bytes of code I’ve written for each language. and then calculates what percentage of my total output that represents. Here’s what it showed, more or less: Past Two Years All Time Perl: 76%, 9.5 MB Perl: 77%, 11.3 MB Rust: 21%, 2.

Edit: In the discussion on /r/programming a comment from /u/nik9000 pointed me at what I think is the best solution. GitHub has a feature where the PR submitter can allow me to push directly to their fork. This means I can effectively edit their PR directly by checking it out and force pushing back to their fork of the repo! Apparently this has existed for a while but I didn’t notice it.

I went to The Perl and Raku Conference 2022 in Houston from June 22-24. Here’s my write-up. Again, I’d like to thank my employer, MongoDB, for paying for my flight and hotel during the conference. We’re hiring for a variety of engineering positions, with many remote options. Contact me if you have any questions about the company or positions, and I’ll see what I can do to find out more.

I’ve been at MongoDB for six weeks now and it’s been great. BTW, we’re hiring and we have a lot of remote engineering positions1. Please email me if you have questions about working at MongoDB or about specific positions2. But that’s not why I’m writing this post. No, I’m writing because apparently my job search wasn’t quite done. Today. Today! TODAY! I got an email from GitHub saying that the position I applied for had been filled:

I suspect that this title makes no sense to most people, so here’s the background. Like most normal people, I have four1 computers in my office. I used to have three, but that was shameful, so I was very relieved to get a new laptop for my new job at MongoDB. A while back, I bought a USB switching device with a remote. This eliminated the need to physically switch my USB hub’s cable from one computer to another.

I did a lot of coding and design challenges during my recent job search! A lot a lot. And I have some thoughts about them. Want to read all about my job search? Here’s a list of past posts: Week 1 Week 1.1 Week 2 Week 3 Week 4 Week 5 The Last One I mostly have thoughts about the coding challenges. The design challenges were pretty much what you’d expect.