Streaming myself coding was strange, terrifying, and fun all at the same time.

Why did I choose a nascent, apocryphal language to do the thing?

Rusty options for CI/CD pipelines and why Xtask is best for complex pipelines.

A survey of simple Rust GUIs for desktop applications. Spoiler: egui's my favorite.

GitHub Actions has little the way of best practices, but here are some strategies that don't work.

Organized lists of stuff that I think is cool.

Version bumping’s the gateway to a smooth CI/CD process and branch naming conventions make it happen behind the scenes.

Use a Github Action workflow to build "universal" Rust binaries that work for both MacOS chip architectures.

I'll be the first to admit that my GUIs don't look great and the second to admit it's okay. There's an undue expectation that the simplest application has to have a snazzy frontend (probably written in ReactJS) or it's not legitimate software. My resume's littered with pandering to this sentiment-- so much development time lost to visualizing stakeholder value so my manager had a dashboard to know what we were up to 🤢.

So, this gopher came to my ~, s*** on my lawn, and built a fence around it, as if it was theirs. There's gotta be a better way to bring home a (Go)pher.

GitHub Actions came onto the scene four years ago with the promise of free Continuous Integration (CI) for public repos. I was eager to use it, but quickly found that the product was too young. Buggy UI elements and the dearth of community workflows made it more of a time sink than it was worth, so I left it with the expectation that the issues would be solved.

My first foray into Github Pages seemed like a warmup. Given how strongly Github touts its Jekyll integrations, I assumed that the process would painless. Ruby proved me wrong.