Tags:
DevOps
,
Homelab
,
Kubernetes
Published Oct. 20, 2025, 7:03 p.m. by wielandtech
After this morning’s AWS outage, which took down roughly 30% of the global Internet, I wanted to share how I’m keeping my website resilient and independent from the big cloud providers.
What started as a simple need to add a Redis cache to my Django website has turned into a bare-metal, three-node Kubernetes homelab. It now hosts my applications and services securely, efficiently, and completely under my control. The goal is simple: reduce dependence on centralized cloud platforms and take one small step toward democratizing the Internet.
From an Idea to a Self-Hosted Platform
Over the past six months, I’ve been steadily learning and building. The process has involved everything from hardware setup to cluster automation. This past weekend marked a big milestone: I deployed an NGINX reverse proxy on my VPS to forward public …
Tags:
Django
,
Photography
,
Python
,
DevOps
Published April 22, 2025, 12:36 a.m. by wielandtech
After hosting an open text box on the internet for the past couple of weeks, I've decided to lock /blog like, share, and comment functionality befind authorization. To access any of these features, please create an account or sign-in using an existing Facebook or Google account.
Once you do so, check out the new /images Photography Gallery. Right now it's mostly just pictures of my dog, but feel free to upload a photo of your own.
Behind the scenes of this latest update, I've migrated this site from the cPanel shared hosting I'd been using for the past several years to an unmanaged VPS. I apologize for any 502s you might've encountered over the weekend. What started as a quest to run my own instance of Redis turned into me running my own instances of everything.
Tags:
Dynamic Programming
,
Interviews
Published April 10, 2025, 4:32 p.m. by wielandtech
A rainforest recruiter recently reached out to me, and I began the mad scramble to learn Dynamic Programming. I find recursion and memorization quite natural to how I think, but dynamic programming quite the opposite. Where we somehow already have the answer, but now have to work backwards to where we started?
The OA was exactly what I had expected to encounter: Two dynamic programming questions; one medium; one hard. Never-the-less, I couldn't plop out two answers in the 90 minute time-frame. I'm curious how much time I should dedicate to this very specific interview skill?
I guess rainforest is saying memory is cheap, wrap it in a cache. Try again in 6 months? GL to Project Kuiper.
