Unfortunately, I don’t have any video content to share as I don’t have the “studio” setup to do so. There are a lot of PC building videos anyway, so I don’t think I’ll stand out from the rest. So enjoy this written version of what I’ve gone through in terms of building and testing.

Here’s the setup:

PCPartPicker Part List

Generated by PCPartPicker, slightly edited

(Free 2x8GB DDR5 RAM with motherboard)

I may get criticized because of maybe a “better” deal on a prebuilt from Costco: https://www.costco.com/p/-//4000384603

iBUYPOWER Element Gaming PC Desktop - AMD Ryzen 7 9800X3D - NVIDIA GeForce RTX 5070 12GB - Windows 11 Home - 32GB RAM - 2TB SSD $1,499.99

Comparing the two, starting with the pros of the prebuilt, there’s more GB of RAM (albeit with less MHz), Windows, and peripherals (not that it matters anyway).

The pros for my build are that it comes with more storage and more watts on the PSU for upgrades in the future, probably with an 80-tier GPU.

I also don’t really like the trending designs of cases with a fishtank design and front I/O ports at the bottom, as shown on the iBUYPOWER. There are also random/questionable components and overheating problems, as said in the reviews.

Here’s the backstory. The client or my sister wanted a new PC but wasn’t in a rush (yet I press button on the motherboard/ram bundle). She is upgrading from an i7-2600K, GTX 1070, and 16GB DDR3 RAM. She plans to keep using her 120Hz 1080p monitor. Emphasis on that as the RTX 5070 should be enough. The reason why partly is because she wants to play Space Marine 2 and skate., but that system can’t launch them, according to her and the minimum specs. She also has a 3 TB HDD for games that’s almost filled up, so she could take advantage of the 4 TB SSD (personally, I would’ve gotten more RAM instead, but prices are outrageous right now) and use the HDD for other stuff. SSD prices are also steadily climbing up, so I just got the best price/GB kind of thing on PCPartPicker with DRAM cache as I believe it is needed for 16GB of RAM. Don’t quote me on that though.

She doesn’t care about the budget and aesthetics of the build, so I just went with the minimum RGB fans at the front with the free bundled RGB RAM that came with the motherboard. I could’ve gotten an RGB CPU cooler for $2 more, but…

Do note, this is the second time I’m building a PC, the first time alone. The first time was building with my brother. I don’t use anti-static wrist straps, and I didn’t do the “plug and touch PSU occasionally” thing. I just don’t wear socks. IIRC I didn’t wear them and have a wood floor hehe.

When I was building, I of course had some problems and hiccups. I’ll write this in steps:

• Get motherboard, check
• Put CPU, check
• Take out the motherboard SSD heatsink, take out the SSD, put it in the slot, screw… no screw

The motherboard SSD heatsink had a captive screw that I couldn’t remove, so I was thinking of putting it on the chipset-connected M.2 slot, resulting in “lower” performance, but I didn’t in the end. The motherboard didn’t come with extra screws. For filler, I took a dinner break.

So luckily, I just took a regular screw from my brother’s motherboard box that has them. And done. Then I put in RAM. And after that, here is some random image I took:

Yes, I have a LTT desk pad and an iFixit Mako Driver Kit.

Then:

• Put CPU cooler, check
• Temporarily remove rear motherboard fan, check
• Put motherboard I/O shield on case, check
• Put motherboard in case…

One of the I/O shield ground tabs got wrongly bent, as seen in this recent video I watched today, surprisingly, with the same board I guess. I was done building this on the 15th at night. I did fix it, with some hiccups. When I placed the motherboard for the first time, it got stuck. In the end, I just had to put some rightward pressure. The rest was easy, despite how messy the place looked with boxes open and plastic bags scattered everywhere.

Then another random image, which was before or after the I/O shield fix:

See the Nino plush. Anyway…

Then:

• Put back rear motherboard fan
• Put GPU, check
• Put PSU, check
• Wire everything neatly, check

Lastly, I just put the right metal panel back on (please don’t put the glass panel back yet) and hoped for a post:

It posted, but there are a few more issues at hand. Throughout the following days, I did some tests.

Here is a dump of them in no particular order:

• bluetooth, check
• wifi, check (latest 6101.19.134.0 driver has intermittent connection issues, at least on Minecraft, use 6001.19.119.0 for now)
• gpu, check (latest 591.44 driver slows down system to a slideshow and can maybe recover after ~5 minutes, repro: alt-tabbing on Minecraft and waiting for a bit, use 581.80 for now) (may need more testing on other games for some tradeoff bug fixes or stuff)
• front I/O, check
• hardware and cooling, check (did stress tests: memtest86 (ram), furmark (gpu), cinebench and prime95 (cpu))
• firmware update on ssd, check (had some old known bugs)
• bios update, check (just because and when I was debugging the above)
• bios settings (expo 1 [for AMD CPU and seemingly the only setting that does 6000 Mhz], forcefully disable iGPU [auto doesn’t work, unnecessarily reserves ram for unused iGPU])

I don’t really play games, so I just tested osu! and Minecraft. I use osu! to see if the performance and latency is similar to my current setup and Minecraft just because I was playing that at the time. Minecraft surprisingly shows two bugs that I’ve fixed via driver downgrades.

Well that’s it. See you next time. Or next year. Or next post, I guess.

Is “Hello world” perfect? Maybe, but it’s so simple and not really useful. Comparing a game like osu!(lazer), this is about 1,000,000:1 if talking about lines of code.

• Where do I put this class, method, or line?
• What do I name this?
• How do I structure this?
• Should it work like this?
• If I hack this now, would it be a problem in the future?

It’s these questions like these that halt productivity. If working on a project that’s not yours, most of these questions can be found by looking for patterns in the codebase and conforming to them. But there can be firsts and no precedent. Maybe you want to annoy the lead of the project or find a solution yourself. The latter can make you seem like a competent contributor or get a “request changes” review / criticism for the solution.

The last question is whether you want to spend the time now or later. Say, for example, osu!(stable) is built on a couple of hacks and has survived to this day. Until the devs want to rewrite such a game. They have to support legacy systems, probably break a few really hacky parts, and add more features to keep the game interesting.

This is probably the reason why I have at least 10+ branches with changes that are not upstream. Most required a little hack or a hack that required a comment. I opened some PRs with such hacks and seemingly got merged. But when is it gonna be properly supported in the framework? When someone implements it I guess.

Let’s talk about dates before February 14. On GitHub, it said that I joined on January 10. But I was lurking a bit before that when I was following osu!(lazer) builds. I remembered watching a video about the progress done at the end of 2017 when it came out. I, unfortunately, do not remember how or when I started following. Maybe it was that video, maybe not. I then joined the osu!dev Discord on February 12. Two days later I started contributing.

My first two contributions on this day five years ago were of course issues. They were on the game’s website: ppy/osu-web#2403 and ppy/osu-web#2404. I was the nitpicky type on day one, who knew. The fixes were PRed by the maintainers like 5 hours later and were merged a day after. I said to myself, make more issues. I made a whopping 10 issues the next day and the day after that. I then received a Discord DM from a then-issue opener like me to stop spamming issues, and I seemed to limit myself from then on. Looking at old issues, I shouldn’t have used a temporary image service puush. Now most of my past issues have a blank void :(

I made my very first PR on the website about a week later. It was just string modifications. To this day, I haven’t made a working development environment with web, and I went on contributing to other projects osu! had in store after I couldn’t find any more issues on web. First was the game, and second, was the wiki.

The wiki was where I was contributing for 2018-2019. I was mostly reviewing (with nitpicks) and helped made a consistent formatting article of the markdown (known as the ASC). I stopped contributing as I felt I couldn’t do anything else / was inefficient with the manual process. Since I left, there have been automated tools and CI made by the current contributors.

Around the time I was on the wiki, I also contributed to the game at a lower rate. My first PR was a mess. I wasn’t even using an IDE. After I knew my mistakes, I fired up the really bloated Visual Studio at the time, and I had a slow computer at the time. I then switched to VSCode. I was increasingly contributing here. In 2020, or three years ago, I got a community contributor badge. I believe I was done, but I just continued fixing the game as much as I can. I only recently switched to Rider in 2021. It was a huge jump to whatever I was using.

History aside, I gained a ton of experience. I didn’t code before this, but I had a yearning to fix things myself. I knew of osu! from a sibling and initially saw no interest. I was probably invested in some other game (Pokemon). I became interested when I played it more and noticed that it was open-source and needed some work. Working with the game you like really is something.

Thanks to everyone that helped me with this journey. Most notably, thank you peppy for making osu!, bdach for reviewing my pull requests, and MegaApplePi (if you’re still there) for making open-source initially less scary.