Date: August 24th 2025
This is my very first entry on this website! Pretty much what you'll find here is rambles I may have about tech, self-hosting, the importance of online privacy, security, etc. Hopefully it's not too boring for you to read lol. I won't be making daily posts or anything, just whenever I feel like it.
I'm starting my senior year of college tomorrow. I'm filled with a lot of excitement but also a lot of worry for my future (pretty much the standard feelings). I'm also trying to get a promotion at work to be able to provide for myself and my fiancée better. I'm faithful that I'll get it but I'll create backup plans lol.
Date: August 30th 2025
Completed my first week of college for senior year. My classes don't seem that bad. One of my teachers is really strict which is kind of annoying but not a big deal.
I want to ramble about why this website doesn't use any sort of JavaScript and why it will NEVER use any sort of JavaScript, TypeScript, or whatever. Firstly, this website only ever needs to be a static website. I won't be implementing dynamic features onto here. I just want you to be able to look around and read things about me. Secondly, I think JavaScript is a terrible language. It's not hard to learn but it adds unnecessary complexity that doesn't need to exist and the language is designed poorly. There are like two million JavaScript frameworks that pretty much all do the same thing. I can do everything I need to do with HTML + CSS. Thirdly, I personally believe websites should go back to being simple HTML + CSS pages. JavaScript allows for too much bloat, spyware, complexity, etc., that it completely ruins websites. This website loads insanely fast and efficiently BECAUSE I don't have two million JavaScript plugins micromanaging the button, the image, etc. I could potentially get behind WebAssembly + JavaScript but, in my humble opinion, it all sucks and we need to return to HTML + CSS.
Date: October 1st, 2025
I've completed my first month of classes into my senior year. My classes are pretty straight forward. I thought they were going to be a lot more difficult
I wanted to take some time and write about something that I thought to be really interesting about networking. In the current TCP/IP model, whenever you need to connect to a computer you connect to there IP address and port as we all know. But something really valuable that I learned while developing my own network stack is that IP addresses and ports are purely logical concepts that have to be implemented on the computer rather than the network card. I've known for a while that IP addresses are logical because they "sit above" MAC addresses on the stack. But understanding ports was kind of a challange for me because I didn't know how they were implemented. Were they on the NIC? Were they on the motherboard? I had no idea. I was thinking of ports as a physical concept rather than a logical one. Whenever I started to really deep dive into the OSI model, TCP/IP model, and my custom network stack is when it started to make a lot of sense for me. Essentially anything above layer 2 of the OSI model is purely logical concepts. A computer will send packets to another computer and that computer needs to be able to handle IP and port logical internally and this logic can be implemented in different ways that are either fast or slow. This learning experience really humbled me because I felt like I knew a lot about networking but in reality I still need to keep learning and to keep growing
What’s this site running?
OpenBSD + HAProxy (TLS passthrough) → Debian + Caddy serving static HTML/CSS. No JavaScript.