Hi! My name is Sage (he/him), and this is my some-sort-of-blog. I’m a full-time software engineer, and most of my posts here are about programming in one way or another (aside from the odd “look at this cat” post).
This site is something of an experiment in minimalism, trying for easy readability on a variety of devices, while being as small and efficient as possible!
A journey through several heavens and hells.
At my company, the fast majority of our applications run a React frontend (pure JavaScript) driven by a Java REST API. And this is… fine. In some ways it’s very lowest-common-denominator development, but there’s a lot of usefulness in that. All those popular tools tend to be relatively well-supported and documented. In fact, it’s in the places where we’ve tried to go a little fresher, a little more hip, that things haven’t always held up so well.
Or, Re-wording the Lessons of ‘Choose Boring Technology’
Here’s a question: What do you do when that “cool new” REST framework your company uses is dying on the vine? Someone hung every application off of it like a damn Christmas tree, and uh-oh, now it’s February.
In a previous post, I talked a bit about my endeavour to build myself a lil’ Lisp: PebbLisp. It’s a project I work off and on depending on my motivation. Recently, I was pretty bored with it, and found myself looking for a new project. Having read a bit about Forth, I thought it wouldn’t be too hard to try implementing it. Plus, this would be a great opportunity do some practice with Rust.