Granted this is a pretty simple task and a low stakes scenario, but I don't think we should limit ourselves to assuming AI will always only be dev tooling.

I use ZFS on Arch Linux and overall have had no problems with it so far. There's more customization and methods to optimize performance. My one suggestion is to do a lot of research and testing with ZFS. There is a bit of a learning curve, but it's been worth the switch for me.

I did a couple years writing C/C++ professionally, and I hope to not go back to that. Too many hours debugging other people's code, suffering vague integration issues, and just trying to get the build system spaghetti to run.

Back then I barely understood binary, and pointers completely confused me. I remember most of the book feeling like a collection of magic tricks. Sometimes I pull it out to rekindle that sense of wonder.

https://codelabs.developers.google.com/your-first-webgpu-app

If you're working a lot with text, Vim macros are great. I'll regularly go into Vim as kind of a text workbench.

If you want to try an auto-updating Vim suite, check out LazyVim [0]. The defaults are great, and there's a lot of features with absolutely zero configuration.

[0] https://www.lazyvim.org/

The Runescape wikis left Fandom a few years ago. The improvement to quality and features has been massive. I'm not sure how much traffic the Minecraft wiki gets, but the Runescape wikis got over a billion page views in 2021 [1]. These are not insignificant losses for Fandom.

[1] https://weirdgloop.org/2021-year-in-review/

I spent too much time trying to guess at the author's reasons. Why are Python and JavaScript not extensible but R is?

The trick for me was to only be able to see one day at a time until the end of the month. I would record a day and think "I'll do better tomorrow." Only to realize that today is always yesterday's tomorrow.

All that to say I'm not surprised to see they hired back many of those people. Ford is a large company and Argo felt just like any other team within the company at times.

> I feel like if I used it, it would atrophy my skills in other more traditional languages.

was not the case for me at all. If you go into a text editor and remove all the parentheses, I find that's how Lisp programmers tend to see Lisp, (function argument) isn't that far from function(argument).

Learning Lisp has only improved my skills as a programmer, after getting ideas like code as data, macros, let over lambda, CLOS and the metaobject protocol. It's a simple model that to me shows how other languages have picked an abstraction and stuck with it, but Lisp has all the tools to implement those abstractions and more.

More mainstream languages are great at focusing the developer, and that makes them very practical. It is amusing though to watch many of the "new features" in languages come out even though Lisp had them years ago.

If you have a good idea for a feature, product, or a new system to improve your team, it's unlikely there will be time in the schedule for it. In my experience you spend your extra time playing around, show it off, and wait for a decision maker to take interest.

Like the original comment said, I've personally never seen someone be assigned time to innovate from scratch. Once a POC already exists folks jump on the bandwagon though.

All during that I try to keep track of questions I have or claims the authors are making. Once I've gone through a lot of the paper, I go back and look for answers to my questions. Interrogate the paper until you are convinced.

I remember being younger and getting stressed about reading papers. So I want to add that not all paper are well written. Don't worry if you're struggling. It's not easy in the beginning and the papers themselves aren't perfect. Keep working at it because it does get easier!

I'm not sure if the Linux Foundation is just a relevant example here or an actual contender to be the steward.

I kind of hope it's the latter. TTRPG rules are close enough to code right? Structured instructions executed by humans with some flavor text at least.

Any unit tests got rewritten along with the test's relevant code. Now that we are sticking with this Go based solution, adding more unit and regression feels more reasonable now.

Recently I chose to rewrite several thousands of lines of Python in Go, because we needed more speed and improved concurrency. Already having a working program and tests in Python was great. After figuring out a few Go-isms, it was a quick couple of days to port it all for big improvements.

It's just one paper of course, but the energy results weren't too surprising. C was the baseline. C++, Rust, and Java close behind. Languages like C# and Go near the middle, and then Python, Ruby, and Perl at the bottom for most energy used.

[0] https://greenlab.di.uminho.pt/wp-content/uploads/2017/10/sle...