"You should let the AI decide your roadtrip," one friend suggested. I swirled the remnants of my tiki drink in my class and mulled this over. It was true that I only had a vague concept of how to reach Minneapolis, as well as a broad timeline. Four days? A week? I had done a quick search of the travel time between Vegas and Minneapolis – roughly 24 hours – and knew if I broke that into chunks, I can ship away at the miles until I had finally reached my destination. I had gone meet my friends in Vegas with only a estimate in my head.

So it wouldn't hurt to take a chance on AI. In the lulls of the conversations I started to pull out my phone and ask my favorite AI, DeepSeek, where I should be going on my way to the wedding next weekend.

The First Lession: AI Cannot Account For Or Predict Day-To-Day Fires

When I informed DeepSeek of my plan, it was very happy and willing to help. It asked my preferences in what I enjoyed--nature, Historical landmarks, or roadside attractions. I had told it to avoid the historical landmarks and focus on nature. It suggested my next stop should be One of the several national parks in Utah, presenting me with a list. I settled on Bryce Canyon since it wasn't too far out of the way and I hadn't bee there before.

After the concert and departing from my friends, I made a last minute reservation on Recreatioin.gov before heading off into the desert. (Pro tip: most National Parks have last minute spots available Mondays - Wednesdays if you can take a day off from school or work.) As I left Vegas and attached approached the park, I noticed the sky on the horizon became very foggy. Once I reached the fog it became clear to me as a California Native what this was--the ash of a wildfire. I notification appeared from the Reaction.gov site indicating that there was bad air quality.

As far as the AI could ascertain, this was still an excellent camping spot. I feel this is a momentary setback for AI as of now, it only knows what its modeled after and cannot manage literally fires in real time. This was not the type of weather I'd want to be outdoors for.

I had asked for other options. While it give me a list of other excellent camping spots in Utah, none of them were something that I could pivot to given my direction northeast for my roadtrip. This is somewhat of an issue I've seen with AI. Once you are on your way and reach a snag, AI tends to want to have to travel backwards and start over.

I stayed the night but the smoke rolled thickly into the canyon that I opted not to do one of hikes that I was hoping to do on my travels. As disappointing as this was, I knew I would get at least one good hike in later--there was still time.

I packed up early, eyes watering, and headed onto the next phase of my digital sojourn.

AI Will Get You 90% of The Way, But You Still Need To Do The Footwork

The night before I had made the discovery that I had forgotten to pack a book to read while at camp. I asked my AI friend to suggest a good book store between Bryce Canyon and Minneapolis, and it suggested The King's English in Salt Lake City.

I pulled into a rest stop after getting out from down wind of the fire and asked my AI Road Trip buddy for an itinerary to Salt Lake City. I was surprised that not only did it find some landmarks along the way, but also generated a google maps link to give me on my way.

The first stop, Big Rock Candy Mountain, sounded like a delight little place to stock up on sugar and mirth for the long road ahead of me. As I passed through some of the canyons and valleys that made up Utah, I found myself pulling into a side road and stepping out in a derelict rest stop. NO POTABLE WATER read the signs next to a restroom.

I checked my map again, and it would seem this is where my AI wanted me to go. There was a rocky mountain next to me, but no real indicator of anything that this was what I should have expected to see. My experience with AI told me that perhaps I was in the ballpark but not quite at the true Candy Mountain.

Being in a canyon I had not enough reception to do a search online. I opted for the old tried and true method of finding one's destination: I wandered around aimlessly until something "felt right".

One exit over and I discovered the Big Rock Candy Mountain Resort next to the true Big Rock Candy mountain. Not where the AI instructed me to go but pretty close. Elated, I stepped inside to purchase my reward. While a fun stop, it was not the largest selection of candy.

The same scenario played out again at the next stop, Needles. This was a ghost town that was washed out by a landslide and never rebuilt. Unfortunately I couldn't locate it at all given the AI's directions and to turn around would have been difficult given the location. I decided to continue onward.

When I reached the book store, I asked the AI for a book suggestion, and once again the same problem. It gave me a list of good roadtrip and camping books, but I could not find any where they should be located in the store. Eventually the Ai suggested I ask a store clerk, still not no avail.

Once again I began to abandon the AI and take matters into my own hand. I have been on a kick of philosophy and esotericism, and decided to look in that section for a book to read. To my surprise, it was in this section that I found Desert Solitare--the book that my road trip buddy DeepSeek and suggested.

Why didn't I find this book sooner? I had misunderstood the classification of the book as not a travel book but non-fiction. As the Ai had given me a cornucopia of suggestions I hadn't mention the book by name to the clerk either, only the board stroke of "where is the travel section?"

As an aside, I have noticed that certain AI will behave in different manners when trying to assist you. I enjoy DeepSeek as it will present me with options and not be deterministic on a solution. Claude, what I use when I am coding, is much more deterministic with his suggestions and often I find myself arguing with its execution. So this book debacle may be a result of my personal preference and human mannerisms clashing with the programmatic intentions of an AI.

After the book store, the next stop on my list was one that excited me from the oddity of it.

With AI You Are The Captain, Not The Navigator

After I made the exodus out of mormon country, I found myself heading to the next stop on the AI's master travel plan: Hell's Half-Acre, also know as that place where they filed Starship Troopers.

I had given up on using the map DeepSeek and provided me and started looking places up by their names. As I drove my trusty muscle car deeper into the barren corner of Wyoming, I peeked at the distance I was to go down a certain road; 100 miles.

I panicked. No where behind me or in front of me did I see any other cars, buildings, or signs of civilization. Water towers on the horizon had become my guiding bacon in the bald and barren landscape. Not I saw only cracks in the road and long flat hills until the horizon.

I took a leap of faith When I saw my first land mark of any sort I anxiously pulled over. There I came across a sign that explained that I was on a common path to the west – THE OREGON TRAIL!

As I stood on the banks of the Green River looking at a old ferry boat that crossed settlers over a century ago, I realized ultimately what the AI had accomplished. My trip was based on popular knowledge. This path I was on was the same taken by the riders of the pony express, emigrant settlers long ago, the same as the indigenous people before them. This was the path that folks like me learned about in elementary school playing Oregon Trail on flickering CRT screens with 256 VGA colors.

It was at this point that my anxiety subsided about being alone in the empty grasslands. I was in the guiding hands of collective nerds. I continued on my way to Hell's Half-Acre, which to its name felt like a microcosm to the Badlands National Park miles away.

The Hidden Truth of Getting What I Asked For

On the last stretch of the journey I traveled through South Dakota. I found myself going to two last tourist destinations, the famous Wall Drug and the Corn Palace. As popular as these were, I happened to come across something I had seen in photos but didn't realize it existed at a visitor center.

I found Dignity, a million dollar statue of a Lakota inspired woman on a bluff overlooking the city. I had seen photos of the status a few years ago and was curious to see it from the side of the road. I had instructed the AI to show me kitsch and natural landmarks, and the avoid historical monuments as they often frame things from the settler's perspective and do not adequately present the indigenous people's voices.

While, this statue seems to fall into the realm of fetishization of indigenous people similar to the Crazyhorse Memorial, I felt it was odd that the AI attempted to get me to go to that monument but not this particular statue.

This I feel is a hidden truth in plain sight when using AI. Its still very biased to the information that it is getting fed, and the gatekeepers of that information are still a specific gender and skin tone.

At Wall Drug, famous for its signs announcing its existence hundreds of miles away, still has antiqued posters explaining the importance of learning of Custard's last stand. There was a gift shop selling native inspired ceramics. Nearby was a giant dinosaur that roared very few minutes. I asked for kitsch and nature, and received explicitly that. Kitsch in some way lends itself to the theme of appropriation, which I had overlooked.

The Road Back Home And Beyond

On the way back home from Minneapolis, planned my own path and took an MVP route back to California. I drove on only three interstates, straight lines following cardinal directions, no scenic routes. I managed to get home a day early and under budget.

I did however stopped by a dive bar to grab lunch and a drink with a friend. She stands on her scruples, which I've grown to appreciate. I had briefly mentioned my use of AI for my road trip, and they pointed out their disdain for it from the amount of energy it devours. The AI is constantly learning, more than 4.4% of all the energy in the US now goes toward data centers, according to a recent article in MIT Review.

My only rebuke to this was a meager, "The problem is its not going anywhere, and in my line of work its being pushed hard. I need to be in front of it somehow." For what its worth, I used one of the less energy-draining AIs on the market at the moment, DeepSeek.

I have been enjoying my experiences using AI, but I think overall its still something that is growing and might be a while until its where it needs to be. I wonder if sometime down the line, I will be able to hop into an automated car like a Waymo, tell it to take me to Chicago, and stop at all the tourists traps along the way. Will that cost the energy of heating a small nation to get that next refrigerator magnet autonomously? I have to remain hopeful that with the Janus-faced aspect of life that is progress, we eventually find a balance to it all.

Sometimes life gives you lemons. Sometimes life decides to give you not only a box of lemons, but a whole moving truck full of noting but browning, rotting, stinky maggot-filled lemons. And then the delivery guy complains his boss is going to make him wash out the truck, so you offer to help clean out the truck with him. But then he seems pretty indignant about the whole thing, and you end up picking out festering lemon chunks from the floor boards for hours as he complains his back is busted from moving all those crates of those damn heavy stinky lemons.

I wanted to take a moment and talk about setbacks. Most of the stories I've shared have been topics relating to developing hobby projects for festivals and nerd collectives I attend. The most bulk of these projects gravitate around Neoptropolis, and five day sci-fi LARP/Music Festival/Immersive Experience. I'll write up another post shortly but I wanted to focus on the projects I attempted to manifest this year but didn't quite hit the mark.

I had left Neotropolis 2024 with a goal in mind. I had seen folks using spreadsheets on monitors, writing down notes on scratch paper, anything but a exciting immersive seamless fantasy building experience. I felt this was a problem that I had the knowhow to solve. I decided to develop a tool to allow folks to create their own interfaces for immersive games without having the need to code. Examples I had in mind were a queue system, a high score table, and a game item menu. This system would save to a database players, teams, and projects that would work with a plethora of inputs – usb devices, RFID readers, QR scanners. As y2k programmer, I had envisioned something similar to Macromedia's Flash but with hooks to actual devices.

A friend at the event had said to me of my terminal hobby project from 2024, "I want a box like yours for next year!" So I called this omnibus of a project Tingobox.

I started on it with the goal to use this new tool to rebuild my last year's hobby code slideshow as an example! In hindsight I see this now to have been a very lofty goal, and ultimately I had to pivot two create a proof-of-concept that at best could only take notes on the player, as well as a update of the 2024 digital toy.

There are a few reasons for this one one theme was paramount. Between the 2024 Neotropolis and and this 2025 Neotropolis, I had the unfortunate privilege to attend three separate funerals for family members. This put a damper on my enthusiasm to produce hobby code--the last funeral I had to throw in the towel and simply show up with a half working demo.

After the event, I immediately thought about all the ways I didn't succeed to reach the accomplishments I set before myself. But people enjoyed what I brought out regardless of my failures or successes. They were happy to interact with something unique.

I also ended up with an app I wasn't planning to build: the utility tool aptly named RFID-Pouch-IndexedDB.

The Mantras of the Pivot

On that note, I wanted to pontificate on my mantras that lead to the mutation of the project over the span of a year. These are sayings that I told myself to provide a bit of respite and continue to get something--anything--done for the year on the side from my normal day to day activites.

Keep It Social

As like with the previous years, I did my best to livestream the coding process of Twitch and later TikTok. This helped shape of the the basic elements of the project, as I ended up trying to different viewer suggestions such as Radix for some of the UI elements and SQLite for data storage.

Its Hobby Code, Keep it Fun

As my morale started to diminish over the summer from the first funeral, I decided to throw in some cartoony graphics to keep it amusing to me to look at. I like capybaras, so I drew some capybara images as placeholders for some of the sections of the app. This brought me joy and gave me an object to focus my thoughts, leaning towards "hey let's just make some templates for people to use as a alpha".

Go / No - Go Time

It was around the second funeral I started to realize I wasn't going to have the energy to complete this omnibus of a project. This was especially made clear to me when I tried to solicit a friend to collaborate with me on it. They couldn't quite grasp the nature or the scope of the project, a "builder to build any display for your immersive event" was a bit too new of a concept that they became shy to help.

From my short stint in making software for managing satellites and rockets, I started to treat my projects with the concept of Go / No-Go for launch on elements of the project itself. Since launches were done at very specific times and locations of the year, if certain criteria were not met by specific dates, we would have to scuttle the launch.

So I gave myself some specific dates to follow: January 1st was to be my ultimate go / no-go for the full version of the app. As the deadline approached, there was another death in the family. With a specific deadline to scuttle looming, I made the decision to spare myself the anxiety and scuttle the omnibus project.

Do What You Can

As 2025 started, I broke my project up into three parts. One would be an MVP – Minimal Viable Product – of what the most basic elements of the project could be. I decided that was a record keeper that could read RFID tags and write notes. I also wanted it to be useable by folks who weren't tech savvy– so I made it to be a webpage that saves local to the browser memory using a slightly new technology, indexedDb. ( RFID-Pouch-IndexedDB )

Since I no longer had a new app to rebuild my project in as an example, I went ahead and worked the previous year's app. After the third funeral in February I was nearly on empty on any motivation whatsoever. To combat this I went back to mantra 2 and decided to do what was all the rage with the kids these days--vibes code!

So I vibes coded in a 3d game last minute using babylon.js. It turned out ok.

Focus on the Journey, not the Desintation

When people asked me what I did for Neotropolis, I tell them I learned a hundred different ways to not do what I waned to do. But I did come out of the experience with knowledge of technology I hadn't encountered with before. I went from Electron to Tauri. CouchDb to SQLite. I poked around with the Web-USB, Web-HID, and even Web-Serial APIs in an attempt accomplish a robust communication to internet-of-things devices. I learned about IndexedDB, and noticed new internal tools were embedded into web browsers in the past few years. I grew more accomplished with web sockets and gained experience with javaScript libraries such as drizzle, nestJS, and babylon.js.

When it comes to my hobby code, I don't see if as a final project where I pass or fail. I see it as an opportunity to learn and grow. Failure is always the best educator. I value the experiences I had within the last year and I feel I can create even more creative experiences in the future. Also, I have to remember that people enjoyed what I did, even if in my eyes it came out undercooked.

More importantly, rest in peace grandma, grandpa, and cousin Sam.

«TEHCNOMANCERS, BLESS PLZ» I wrote on the tape covering the monitor from the wind. The sandstorm at Neotropolis this year rocked the wall of my booth with enough ferocity that it knocked the monitor out from the kiosk frame. Fortunately, it landed in the sand unbroken and I plugged it back into the cables it had escaped from.

Having participated in its sister festival, Wasteland Weekend, for over a decade, I had seen my fair share of bad desert weather. This time was easily the worst sandstorm I had encountered. By evening, those with now thrashed tents and those desiring a more insipid vacation packed up and headed down the long dirt boulevard back toward civilization.

As an event veteran, I knew with some patience the sandstorm would pass. This was a temporary delay like a sporting event postponed by foul weather. As evening approached the gusts became a chill breeze and the neon lights of Neotropolis began to electrify the air once more.

In its third year, Neotropolis continues to grow as an immersive entertainment entity. A stronger emphasis was present on storytelling both physically with new set pieces and volunteer storytellers, and digitally with several monitors displaying the Neotropolis New Network. N3 not only added an immersive backdrop to the event but served as a tool to elaborate on some of the fiction narrated during your stay on Kepler 609c.

Several other clubs and camps, known as factions, bright competing media to assault your eyes and ears in true cyberpunk fashion. Wayward Communication Corporation's radio station, Neotropolis Public Radio, returned this year with its 24-hour music and a live morning show. A rival to N3, news channel Network 42 was on display at least one seedy cyberpunk dive bar. A one-man pirate radio station, Radio Nox, was on the scene covering the event firsthand with his portable pirate radio.

Intranets were among the technology growing at the event this year. Seashell Cove displayed chat kiosks using the open-source software BeeBEEP in the Megablock. With NeoNav's tanChat in the WCC intranet Wayward Access, multiple chat networks functioned this year's event!

What is being developed is less of a curated zoo of tech, but a diverse technological forest where projects are blooming and thriving in their niche alongside their cousins. Multiple activities are supported by a web of intranets, gophers, artisans, technicians, and a decentralized power grid. If one tree falls, the ecosystem goes on.

«SANDSTORMS CAN'T STOP THE SIGNAL!» I wrote on tape as I screwed the monitor in place this time. Having blown away the sand from its ports like an old Nintendo for the 80's the kiosk came back to life and began to rotate through the carousel of graphs displaying NeoBand read data.

My one regret with this year is my lack of taking photos of all the interesting immersive interactions people created to share at the event. Currently, I am working on a small project to facilitate immersion for folks who aren't tech-savvy. It will be a welcome supplement for this wild neon jungle that has taken root in desert sands. I'm curious and excited to see what will continue to grow from the seeds planted these first few years of Neotropolis.

Before the year ends and my low attention span moves on to other things, I wanted to share a few items I created in 2023. This article exists solely so I don't have to dig through the buried images of my phone!

Exotica Expo at Wasteland Weekend

One of the festivals that I participated in for the past decade has been Wasteland Weekend. As I started to sunset the character that I played, I decided the mythos of his story would be that he would occasionally return with artwork of the strange exotic things he has seen among the wastes. My pal Dominic suggested I do some art related to the theme of 1950's exotica.

As exotica is more of a play on post-war travel, which has an unsavory colonist taste, my take on the theme was more about cryptids and bizarre occurrences that my character had encountered in his post-apocalyptic travels. A ragtag, mermaid, a many-faced creature, and even a rat fink-like mad max hot rod were depicted in my art. It was a very interesting confluence of several genres since the art was inspired by 50's cartoon retro designs, especially Derek Yaniger.

I had also designed a version of my character to look like an old Hana-Barbera character, so pulling that out I used it as a basis for the sign. As I was in a rush I decided to do it with poster pens with an acrylic background, which turned out pretty nice! As my art tends to be pretty sloppy I was surprised that people took everything home.

Art Sales

Art is a hobby for me at the moment, but to make a little passive income I made a font based off of my quirky handwriting. Two years ago I wrote a script that generated designs of every element in the periodic table and placed it in a fulfillment site, Redbubble. As a programmer, I make enough financially that I tend to timebox my art time to not eat up my programming time. So it was surprising to me when I saw that made enough for a fancy dinner this year from the sales of a singular element shirt: Thorium.

Sales for thorium peaked during the summer, so I think it was due to the movie premiere of Oppenheimer.

There was lots of interesting randomness when it came to art for me in 2023!

My friend Elli asked if I could help them with a character quiz for their custom Dungeons and Dragons class they had created, the Clock Tower Agent. This class is predominantly featured in a campaign she runs as GM on the curiously eclectic D&D podcast, Clock Tower. Now in its second season, the drama features a collection of Clock Tower agents who do the work of a magical tower that tosses them into strange and frightful worlds.

The Mysterious Masked Dungeon Master

First, let me tell you how I met Elli. They had shown up before a friend's campsite at the Wasteland Weekend festival I often attend. They had made a fake oversized backpack to appear much heavier than it was and were peddling masks they had made for the event. The whole time they wore a mask and not once took it off in complete disregard to the scorching Mojave sun.

It has been years now, and I can count the number of times I've seen them not wearing a mask on one hand. I've gone out to have a slice of pizza with them, and they will be wearing the same mask at the pizza parlor. One thing I admire about her is their commitment to the bit! More about that desert experience can be digested in this wonderful documentary by People Make Games.

The "Gardening" Method of Building an App

Typically, as I am twenty-plus years down the road of writing web code, I have become the seasoned code samurai--never to unsheath my blade of programming skills unless I have a finished design, API schematics, and an epic of to-do tasks. When I sit down to code, there is a roadmap to find myself to the finish line in the two-week "sprint" of work.

Elli approached me with a document that was a multiple-choice quiz that she administered to new players who wanted a new Clock Tower Agent character. The goal was the automate the process and place it on the podcast's website.

A multiple-choice quiz seemed easy, especially since there was no writing to a server. Hypothetically, this could be a single file that my friend could host on their site. With no design, a vague idea of how to set up a schema for a quiz from a lifetime of code challenges and tutorials, and a mental list of steps in my head, I thought to myself, "Let's just take a whack at this like I didn't know better and see what grows out of it!"

The basic quiz came together rather quickly, with some caveats. If you notice in the screenshot, you can select two answers at once. Secondly, each question added scores to multiple values (one answer could buff your strength score and also your subclass selection sorting tally). Oops. Normally, I'd ask a bunch of leading questions and avoid missing these bits of logic but it was fun to discover and refactor on the fly.

So each question can have multiple answers that modify multiple scores. The code is still pretty clean at this point. However, there was an interesting challenge that this organic approach didn't account for. Once the quiz of done, Elli would take the values and build out a description of the character as well. So not only did the quiz need to modify values, but it also needed to select certain character appearance attributes!

A part of the process is that the player can alter one of the assigned attributes. So I guess I'm making Mad Libs now too.

Do you know TDD? Test-driven development? This became DDD, dopamine-driven development. I allowed myself to make something silly and novel which was driving the process forward. By this point, the code was getting a bit unruly since I attempted to keep it a single file.

Ok, so once you're good with the Mad Libs, you get dumped onto a page where I got to play with my CSS skills and make a stylesheet for printers like the old days. As an aside, I once was asked to make a website that was mostly black on the screen, but mostly white when you printed it since the client imagined that was the most environmentally friendly solution.

So after showing my progress to Elli, somehow I had decided that I was now making it print out to a PDF character sheet! I forgot why if it was either the dopamine rush of playing with another tech library or if I didn't want to ruin the nifty half-sheet design I had come up with.

When the PDF writing feature was introduced, I ended up adding an extra library and a background image and my single file vision came to an end. Oh well.

But this was where my garden ended, and I reached the end of the Shire. It became apparent that the image I was using for the tables of the PDF wasn't consistently spaced and I had to find the X and Y positions for every field on the page. This killed my dopamine and I dropped the project at 99% of the way there. This was very un-code shinobi of me.

Fortunately for me, Elli has an artist's mind too, and we both forgot about the project. Now it is December. Time to put on my big boy pants and shovel that snowfall of X's and Y's to get this quiz out the driveway and on its way.

Thirty Second Retro

It was fun to allow myself to discover new aspects of the project along the way and let myself be curious about them. This was a nice change of pace of being in the primadonna headspace of needing a solid plan to follow to keep the course.

Would I follow this process again? Sure. Would I follow it on something that I would need collaborators on? Heck no. No one should need to weed my messy organic garden.

If you're curious about how messy the code got, you can find it on Git Hub here.

Try the Clock Tower Agent Test

Preparations have begun for my time at Neotropolis, an event returning for its third year in 2024. Like its sibling event Wasteland Weekend, Neotropolis is a hodge-podge of an immersive festival that attempts to collect many niche activities into one event.

I've enjoyed Wasteland Weekend for about a decade now, and I'm excited to explore the creative space Neotropolis offers. Although the communities for both events currently are almost identical, I'm hopeful that the immersive activities at Neotropolis will grow to be more tech-related as electronics are more prevalent from its sci-fi theme.

There are already some really awesome projects underway. One of my favorites from the previous year was done by Alleycat Asset Acquisitions, one of the many "factions" (clubs) present at the event. They created a wonderful bounty hunter game with custom 3D-printed wrist devices.

Not only did it add to the immersion of being a cool hacker, but with leaderboards, ID cards, and a video explaining the rules, the AAA bounty hunter game was easily one of the more immersive aspects of the event I enjoyed.

Then there is the project I helped co-establish with a fellow collaborator who enjoys being referred to with a William Gibson-like moniker, "The Swede". This project is of course NeoNav, a suite of tools to help facilitate play at the event. I was able to make a web interface client that could serve as a dashboard for some core features. For the last few years, it has run off a resort-style wifi network and on-site web server provided by The Swede's faction, Wayward Communication Corporation, which he calls Wayward Access.

Perhaps the very first and of my favorite games at the event was the Power Core Mission by Pilot‘s Perch. The objective is to recharge an interactive battery core for five minutes at one of several charging ports. With the ability for unsavory forces to “hack” and corrupt the charge attempt, the activity becomes more intricate than expected. The cores pulse colored light which was a level of detail that made it not only fun to play with but also watch as others gopher the devices around the event.

Lastly, one activity I missed last year was the cool VR game HackNeo by Andy Thorne. Written in Unreal Engine 5, this Neotropolis exclusive game was only available on a Quest 1 VR device that Andy presented to folks he encountered at the event. This is one of the more intimate and creative experiences I'd love to see more of.

As 2024 will be the third year of Neo, I am hopeful to see more of these kinds of activities come forward and establish themselves. Neotropolis is growing to become a confluence of technology with immersive experiences in storytelling.

Been to Neo and think I missed something good? Feel free to mention it in the comments.

I went ahead and revived my old blog site from the dead. Looking back at older versions of this site, I'm starting to have second thoughts.

The content you should expect are some coding tips, art shares, essays--maybe some info about my hobbies and creative processes.

If you want to follow along and receive emails when new content drops, feel free to subscribe.