Many years ago, Travis CI was the only game in town for FOSS project CI, because it was the only service that offered unlimited free builds for FOSS projects. Many projects took Travis up on the offer, and I set up testing for all of my Perl projects there. Switching to CI was a huge improvement for many projects across many languages, and I hugely appreciate the impact Travis has had on my FOSS work.
After 17 years (or so) of operation, I’m shutting down VegGuide.org. You can read more about why by following that link. When I created the site, I was 28 (which means I’m now 45). Creating the site was a lot of work, and I did it in my “free” time outside of paying work. I think at the time I was doing consulting work and probably not working full time. I do miss the ability to simply put a huge amount of time and focus into a personal project, and I won’t rule out going back to consulting in the future.
We’re still hiring for a bunch of positions. But fear not, the position working directly for me has been filled, so you’re safe to apply now. Here’s what’s available: Windows Build Engineer - You need to really understand the Windows OS and how to compile things there for this one. Have you ever built Perl, Python, or OpenSSL on Windows? Have you ever written cross-platform C code that compiled on Windows?
Updated August 18 per discussion on /r/golang. Thanks to user Bake_Jailey for noting that running go mod tidy can do more than just remove unneeded module requirements. Now that Go modules are a thing, I’m starting to use them for my Go projects. So far it’s been a nice improvement from dep and before that, godep. With Go modules you end up with two files in your repo, go.mod and go.
Hey, ActiveState is hiring many people, and all of our engineering positions are remote-friendly! If you like what I say here, maybe you’d like to apply for one of those positions? Two years ago I wrote a post based on a talk I gave at The Perl Conference 2017 titled How to Make Your Technical Hiring Process Suck at Least 20% Less. The video recording for that talk never worked out.
We’re embarking on a large expansion of our engineering team at ActiveState and hiring for many positions! Note that all of our engineering positions are totally remote-friendly. You can work from anywhere in North America! The positions on my team are the Data Engineer and Senior Backend Engineer positions. Consider yourself warned. Please note that the various Build Engineer positions are not software development roles! Those roles are primarily focused on getting software to build on various platforms (including Linux, macOS, and Windows).
I just wanted to remind my many, many, many readers (all 3 of you) that I will be offering two tutorials at this year’s Perl Conference in Pittsburgh, PA. Also, last time I posted about this I got the dates of the courses swapped because I am very smart. You can sign up for these courses at the conference’s Eventbrite ticketing page. On Thursday, June 20 I’m offering my Introduction to Go course.
The CLDR project released a point update to the CLDR dataset, 35.1.0, a week ago. I regenerated the DateTime::Locale distribution using that source data and none of the data that DateTime::Locale cares about has changed. So if you’re wondering why I haven’t released a new DateTime::Locale now you know why.
Once again I’m doing two tutorials at The Perl Conference this year! On Thursday, June 20 I’ll be offering my Introduction to Moose course. This is likely to be the last time I offer this course so sign up now. If you want learn more about using Moose this is a great opportunity. I’d also note that most of what I cover applies to Moo, so what you’ll learn is useful in many situations.
This is a story of how Go’s package management system and GitHub fought a war, and how the war was lost (by me). Go references packages by a repository name, so if you want to important a package you write something like import "github.com/volatiletech/sqlboiler/queries/qm". It’s simple, right? Yes, it is. When you want to submit a proposed patch to a repo on GitHub, you fork, make a new branch (because you’re not a monster who makes a PR from master), and then you submit a PR.