Post-migration, I knew some jobs were left untouched. Not because of the amount of work involved — again, I don’t think the workload has meaningfully increased. For the first project afterward, I wanted to focus on a part of the website I hadn’t touched in a while: analytics.
Tagged Migrating with AI
To Self-Host or Not To Self-Host, Migrating with AI Pt. 4
No doubt the idea of complete control of a blog at $10 a year would be appealing for many. And no doubt many would share the same concerns as I do. During the planning phase, some of the definitive downgrades I was able to come to terms with, some of the regained controls I was able to make use of, and the saved cost I was ready to file under an existing list of subscriptions. I believe there are three major concerns most bloggers may have: uptime, support, and technical debt to AI.
The Part Where I Pay, Migrating with AI Pt. 3
The plan finished baking. Reviewed, revised, the whole nine yards. I wasn’t going to execute the plan myself; I wanted to automate it as well. The only decision left was how.
Between Cost of Hosting and Effort of Self-Hosting, Migrating with AI Pt. 2
Starting a blog doesn’t cost money. At least that’s how I started back in the 2000s, and free platforms are still around. Intermediary platforms came along in the 2010s, giving some control back to bloggers or sharing the ad revenue. The way out of it all, ever since the term weblog was coined, was to run it yourself — either on a machine from a paid hosting service or on your own home server. The question was price and effort.
The Day Hosting Failed Me, Migrating with AI Pt. 1
Mad Tea Party was down for 24+ hrs. A datacenter problem. I’m not arguing a professional hosting service should have zero downtime. Failure itself is expected. Reliability is what happens after it. A full day of downtime is one full business day lost, and a good hosting service should be judged not only on physical performance, but on clear communication during a sudden failure and reasonable effort to reduce it.