Anthony Martinez @ajmartinez@librem.one

Rust really shines, for me, in cases where I have targets with multiple processor architectures, and varying degrees of maintenance support (read: still in service but beyond EOL). I write my tooling once, and when my build scripts are done I have the binaries I need for each platform. In my last use case, these were actually smaller than the venvs I needed to ship with Python on the minority of nodes where it was even possible to deploy a modern Python venv.

Living on the wild side: firmware upgrades 7min before my stand up.

Here’s to hoping I actually get to do some climbing in the next two years. I moved to Europe prepared to climb every weekend of the season but then 2020 happened and the only climbing I’ve done is up the stairs into bed.

Wireshark and ripgrep ended up really being all I added to Tails. Oh, and a persistent .bashrc with the critical ‘set -o vi’ addition.

And let me just say how cool it is that a Tails stick I created a month ago booted up and immediately said “upgrade!!!!”

Worked like a charm too.

Sometimes I still expect nothing to work after an upgrade like the old days when a new kernel most likely meant you’d spend a week trying to figure out why your audio didn’t work anymore.

Since I’m not a huge fan of the “need” to carry multiple machines around with me everywhere I go, I’m setting up a Tails drive with the tools I need to act remotely in emergencies from any machine I can USB boot. My hope is that in the near future I can use a Librem 5 to handle my remote admin needs directly. Where apps do not exist for my specific needs, I intend to create them since that’s part of the beauty of open software and systems.

Made it the entire week without feeling compelled to launch VS Code. Developing in Vim, alongside my native terminal tooling and needs was actually very enjoyable. Time to `sudo dnf -y remove code`

It looks like Hurricane Laura for the most part spared my family reliving the damages sustained in Harvey and so many other storms in recent years. Having mucked houses and done recovery work many times now my heart goes out to those who took it head on in Louisiana.

All dev this week has been in vim, and it’s working out very well for me. My config is here: https://github.com/anthonyjmartinez/vim-config

In the 20yrs I’ve been a #linux user I’ve always used vi(m) as my editor of choice, but it wasn’t until this week that I bothered to add a single plugin or add more than some filetype/extension-based indentation preferences to my .vimrc. Today, I managed to get quite a lot of development done without launching VS Code once. Not mad about that one bit.

Nobody seems to enjoy documenting their tools, but it seems that people also really hate when production lines are stopped due to a change in an undocumented system breaking their end of line test.

If only there was a way to avoid such work stoppages...

Yarn progress. May only have a week or two left before I finish spinning this single. Plying should not take very long afterwards.

Finished my self-defined let’s go ahead and write yet another implementation of “tail” in #Rust project today. It’s about 100 lines of code, and I built it as a library with a “reasonably sane” default implementation in an accompanying binary. Need to write some tests and documentation and then perhaps I will actually release the thing on crates.io

Haven’t made it as far in my Rust adventures as I would have liked today, but I didn’t get totally stumped. For every #rust project I start I probably complete four #python projects, but this is most likely because I’ve been messing with Python for decades and only recently started to dabble in Rust.

Last day on quarantine. Suppose I'll work on some #rust programming with the hopes of gaining better proficiency. I'd like to get my Rust to where my Python is so I can rapidly develop solutions with either language based on my needs.

First time spinning dyed wool, and first time spinning in The Netherlands. What else am I to do on quarantine?