About

Justin Carver

Howdy there! Thanks for taking the time to click around on my blog. My name is Justin, but my wife and friends call me Justino! [xusˈtino / hoos-tēˈnō]

I've worked in IT for over 14 years now, doing everything from desktop support, to audio-visual, to help desk; all the way over to systems administration and software development.

I browse the internet a lot. Probably more than what is healthy, so I'm constantly absorbing information, trying to learn the in's-and-out's of various libraries or hardware systems, but most of all, I really love writing. It's one of my specialties! So I apologize if any of my posts come across as overbearing or just rambling on about meaningless stuff. I do promise it's not on purpose.

Every post here is made of Markdown descent, with just a small formatting twist here and there. Nothing crazy, but I do think that standard, plain ol' Markdown cannot contain the ideas or the wherewithal to convey whatever dumb ideas I may have at the moment.

About my writing

I spend a lot of my time at both my 9-to-5 and my 5-to-9 working through stuff like: pumping out support/product emails, writing technical docs, reviewing code repos, checking software forums, reading up on obscure Reddit posts, conferring with ancient product manuals, etc. Mainly writing, reading, and typing; almost 24/7.

My grammar may not be the best, but please know that while I do type what comes from the heart, I will mainly type what comes from my soft, squishy, perhaps smooth, human brain. What's the fun in trying to keep a personal blog and then using something like AI to fill-in paragraph-slop on a screen.

With that said, all the content on these pages were written by a human.

Colophon

Built with Astro and React, set in Geist, served by Bun, and deployed with Docker.

Take a look at either my Atom, RSS, or standard JSON feeds listed below in the footer. I try hard to make sure to accomodate whatever the popular/favorite reading mediums are out there. If you like what I write, and would rather read it in a different format — by all means, please let me know what protocol or spec to publish in and I'll make sure it happens!