Writing

Last year I was upgrading my computer’s power supply unit (PSU) in an effort to prepare for the GeForce RTX 3090. It so happened that I swapped PSU manufacturers as well while I was at it.

Incremental changes for better GPU performance.

If you’ve been following my blog, you know that I’ve been fiddling quite a bit with the Halo Infinite API. To the point where I started writing my own wrapper for it.

I like reading papers on arXiv, but I like discovering them more through Andrej Karpathy’s arxiv-sanity-lite.

Back in January I mentioned that I managed to continue the tradition of beating Halo on Legendary with the release of Infinite.

After four months of waiting, I finally got my hands on a Steam Deck! I am particularly excited to get to use this device a bit more because it’s basically the cleanest version of “Gaming on Linux” that you can imagine.

We need to talk about Windows priorities as a product. And I am saying this as someone who wants Windows to succeed - it’s a great OS that, despite it’s naysayers, is still one of the best when it comes to backwards compatibility and richness of functionality. I mean, I can literally run a game written for Windows 95 on Windows 11 without major issues.

I am diving much deeper into deep learning. And with deep learning, one of the things that can help you the most is a beefy Graphics Processing Unit (GPU).

Getting visibility into your match performance outside the game.

Making sure you have the right tokens to make Halo API web requests.

How I managed to learn the about the Halo Infinite web API endpoints.

What better way to spend the couple of remaining vacation days than by diving into the new Halo campaign.

Getting to know a hidden data and insights pipeline.

Fiddling with Fiddler to enable hidden features in the podcaster dashboard.

Twitter just announced that they are re-launching their verification program, and now you can check whether you are eligible directly from your Twitter account settings. Neat!