The "small, but powerful, gaming machine" has seen a few new parts over the years but one of these parts (a new nvidia RTX 3080 ti founders edition) eventually pushed it beyond its cooling capabilities. My slim case was not well designed for handling the new flow through airflow design adopted by the newer RTX cards and any heavy usage caused the entire thing to fill with heat until eventually the PSU would call it quits. Ripping the top off of the case and adding a few extra USB fans helped to cool things off a bit but it was not a pretty sight, and the temperatures were still uncomfortably high...

In episode 54 of the All-In podcast, Chamath brought up the idea of initiating a spread trade within big tech stocks as a way of protecting against a market downturn. It has been three months since the episode aired and we've already had a pretty good market correction with the possibility of some more to go. So, how did the spread trade do? If you had entered the trade when the episode aired would you have made money? Let's take a look.

Lazy portfolios are a simple and safe way I've been using for some time to successfully invest in the market. The general idea is to allocate your investments into a few broad funds (usually index funds) proportionally to your desired risk profile and let them sit and grow over time. Once you've purchased your funds at your desired allocations the only action required is to occasionally rebalance them and bring them back to your desired allocations as they change over time. These rebalances can happen at set time intervals (6 months to a year) or at specific triggers based on some other strategy. If your only criteria is that your risk profile adjusts as you get closer to retirement age then you can invest entirely in a target date fund, but if you want more control over when/why/how you rebalance then a lazy portfolio might be for you.

Performance is a common topic in computing, but it is especially common in the frontend world as the latest Javascript technologies battle for the frontend throne. Some may say React has already won (and the usage numbers seem to agree) so in this blog post I wanted to talk about a piece of problematic code I'm seeing more frequently in the frontend world as Javascript syntax is evolving and components are taking over.

We've all experienced frustration with the internet going down. Now imagine how frustrated you'd be if you found out that your ISP intentionally blocked your internet access for the purpose of advertising their software; and better yet, your ISP claimed that state legislators required them to do it! Well that's exactly what is happening to CenturyLink customers in Utah right now.

There are many tools you can find for unminifying javascript code. However, most of these tools just add proper formatting and call it a day. Considering many minifiers mangle local identifiers to one or two characters and reuse those identifiers frequently, this can result in some code that is still quite painful to read. I think we can do better.

Have you ever wanted a computer that is fast and powerful but also small, sleek, and sexy? Surely such a combination cannot exist! Well, prepare to feast your eyes upon this beautiful build I recently completed.

One of the most important features that a website can have is a method to effectively search its content. There's no denying that there's such an overload of information on websites these days that helping people find what they need can be a monumental task. That's where a well designed site searching functionality can swoop in to save the day and today I'm going to show you how to deploy this superhero feature on your very own static website, no backend required.

One of my goals with this new year has been to start writing more frequently, be it technical articles or just my thoughts and ramblings. I've considered Medium in the past (and still might duplicate some of my writing there), but felt the platform just isn't quite there yet for the purpose of writing technical articles. I have read many well-written technical articles there that I felt were held back by the limitations of the platform. I'm of the strong opinion that learning is doing, and limiting educational writing to text and graphics isn't the best medium for doing.