Thank you for the write up. It’s very helpful.
I’d pick another CPU (even Intel) but I understand that you’re bound to the motherboard. I’m looking for a SFF build, what’s your PC-case?
That is sort of a surprise. Sort of, because I am not yet sure, if I can make it work. It will be part of a later post, but first I need to make sure the internal parts work. The linked articles and videos, suggest buying Intel 13th/14th generation is like playing lottery and the faulty vender bios configurations do not make things easier.
why not get the z690 and a 12th gen? I don’t think Intel’s improved their single thread performance that much with 13th and 14th, which is what matters with most games
There are two reasons why I chose a newer CPU. The first is, that I wanted to future-proof it, that was before I knew of the 13th/14th-gen issues. The second is, that I intend to use this machine for emulation. More specifically PS3-emulation. Because this requires a powerful CPU, I thought newer is better. But I will look, if a 12th generation CPU is enough to get the job done. Which CPU from the 12th gen would you choose?
idk, I have the 12400 and it works perfectly fine for me but i’d guess the prices would’ve come down on the 12th gen ones and you’re spending so much on the motherboard anyway so maybe look into the 12600k or 12700?
btw, for this generation the 12600 is very different from the 12600k because the 12600k has a few more core iirc
The most very Mary Sue characters will fail as part of winning. “Oh gosh, I flipped the evil villain’s wall switch that forced all the robots into hard mode - I guess instead of an underwhelming fight scene I now have to go full badass.” Basically their flaws are usually just vehicles for even more exaggerated strengths.
Tell it to my neighbors, my tree has slowly become treeless, I planted one in the middle of my front yard so that the house can stay cool in the mornings
I think applying design patterns blindly without understanding what problems they’re supposed to solve is often more harmful than not using them. It can lead to difficult to manage code bases because the program is over engineered for problems that don’t exist.
My general rule of thumb is to write code that can be easily adapted to unexpected changes in requirements. Avoid writing code that paints yourself into a corner. Simple solutions are often easier to work with than complex solutions. If what you’re doing adds a lot of complexity, take a step back and seek other options. Maybe you’re overlooking an obviously simple solution to the problem?
I think inheritance almost always has this “painting yourself into the corner” tendency. Once the design is set, it’s often difficult to break free from it. Composition along with interfaces is generally the better choice. Often not even interfaces are needed.
This comes with experience. You learn what works, and what doesn’t. Often you do it the hard way.
Databases are tricky. I have no good advice for that.
I mean, the guy has some good points (and a good microphone and a radio voice) but I don’t think the first video you linked is very well done, especially the intro. Starting with “this is the most important video because it’s going to tell you something that nobody tells you” is a great way to sound …kind of like a narcissistic crackpot.
E.g. the one with 3800 lines is pretty good. (BTW I realized already subbed to his channel earlier…)
Haven’t properly watched the videos, but I don’t think OOP is that bad. I even think encapsulation is one of the core strengths of OOP.
I’ve worked with systems where no thought was put into encapsulation, and those are often incredibly difficult to work with because everything is heavily interconnected. Can’t make a change in a small thing without risking breaking something else at the other side of the program.
I like to see encapsulation as a workspace. It defines the tools we have direct access to. Changing one thing in a workspace shouldn’t affect anything on the other side of the program. Makes it much easier to collaborate in large teams. Minimizes the risk of interfering each other’s work.
Your build looks good (setting the ongoing intel issues that somebody else already mentioned aside), but personally I’d consider a different drive than the Samsung - it’s a great drive, but usually overpriced imo. If you can get it for a good price then absolutely go for it, but most times I find sn850x drives significantly cheaper and insignificantly slower. Otherwise, the only other note I’d make is that grub is abysmally slow at higher resolutions on chips with no igpu, at least when using a nvidia gpu. I’m not certain if this would apply to an AMD gpu, and either way you can just use something better (cough cough refind) to avoid the problem, but for anyone who just wants the default out-of-the-box bootloader on most distros to just work properly it might be worth spending the extra ~$40 for the K series instead of the KF to get the igpu. It’s not something I’d recommend doing personally, but it’s at least worthwhile to know about when you’re making the K/KF choice imo. Anyway, good luck with your build and have fun with setting everything up!
Thank you for this interesting information. I use systemd-boot with secure-boot. I do not know if it has the same issue, but I hope not. If it does, I might consider switching my boot loader or when nmbl is ready ditch it entirely. Like thingsiplay mentioned though, it still might be a good idea to use an iGPU for debugging purposes.
Turley has written a lot about the NY trial and his analysis looked ok to me. IANAL of course. But, those convictions didn’t seem to change Trump’s polling noticeably. We will see what happens with Harris.
kbin.life
Hot