This area of the site is all about notes, technology exploration, and opinions. It is my very own digital garden. You’re welcome to explore, collect the fruits of my labor, and apply them in your own projects. Content here is 100% organic and locally-grown.
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!
Not too long ago, I was reading Charlie Kindel’s “You’re Thinking of Your Career Trajectory Wrong” and it reminded me of yet another trope that somehow is very commonplace, at least in the tech industry - your career is not a sprint, it’s a marathon.
Why it’s a bad thing that we don’t get to use perpetual licenses and instead rely on software subscriptions.
How to manage your game captures in bulk.
Understanding the components to the Spotify Wrapped generated story.
The other day, Clint Rutkas (yes, that Clint Rutkas) tweeted about a potential scenario that GitHub does not have built-in, but that could be useful for folks that want to have a deeper look at the performance of their repositories - identifying “center of gravity” issues.
Making it easier to work with APIs where APIs are least likely to be easy to use.