Gavination

I'm gonna need to know where you got this...purely for educational reasons of course...

1000% agree. It sounds like a lot, and that's because it is. I'd also like to add that when it comes to resumes, get as many eyes on it as possible before you toss it out in front of folks you want a job or internship from. I recommend obsessing over your resume and remembering that it's a living document; it's supposed to grow and change as you gain more experience. 

Hi! Software developer here, and I'm more than happy to echo some of the sentiment along with providing a very biased opinion on how tech careers should be looked at.
 
I'll be speaking purely from the perspective of a software engineering curriculum, but I'm sure you can get some generalities as well.

Firstly, before anything, remember to be passionate. You have to love what you do, and while some of it will be a slog, if you hate every moment, consider something else.

When recruiting from most universities, we tend to look more at how the candidate stands out than anything. Meaning, are you just someone who did more than undergo a CS or EE curriculum in college, or did you attend hackathons, join engineering groups, maybe found a way to marry your passion for other things alongside tech? Some general pointers I'd say would be good to look into are:
- Joining engineering groups: IEEE, your school's CS club, Women in Technology, etc...
- Participating in student hackathons. Checkout the Major League Hacking site. put em on your resume, especially if you win
- Hunting hard for internships. Make yourself as interesting as possible, start at the top of Fortune 500 companies list, and apply EVERYWHERE
- Go to conferences where you know recruiting is important. The Grace Hopper Celebration and Richard Tapia conference are targeted around promoting diversity in tech, so networking with folks there would be a great opportunity.
- Start a GitHub account, learn Git, and upload cool things you're building in order to learn. Recruiters LOVE to see Github accounts from students. It tells them you can walk the walk and talk the talk.
- Learn. Learn everything and always be hungry to learn more. Tech changes dramatically very quickly, so you have to be prepared to always be skilling up in something.
 
*leaves soapbox*
 

Laptops have become too "thin and light" at the expense of everything else

Folks, I'd like to thank you all as well as the power of the forum. A combination of updating the BIOS, clearing the CMOS, and swapping RAM in and out seems to have worked (though not individually lol). I was a bit nervous, but it looks like everything is on the up and up. You're all awesome.

Be sure to use the correct slots for RAM sticks, usually A2 and B2. Make sure with the user manual (who really read this).

Bad assumption there. The QVL is of very limited value as the manufacturers will never be able to test every version of every kit out there. More so with Zen 2, compatibility will vary with bios version also. I don't bother to look at it at all these days.

If you mean something like memtest, then no. I do run ram intensive workloads and any errors will get picked up quickly in those anyway. I mix and match ram kits and systems quite a bit since I dabble with competitive overclocking. Most of the time if the ram is unstable, you will know about it very quickly. I've only had one situation ever where ram was erroring at a rate of less than once a day. It would pass memtest as long as you like but errors only eventually showed up with 24/7 sustained loading, presumably as it also required some interaction with the IMC that memtest wasn't stressing enough.

OK, OK.  What I have observed in this forum since I discovered it is that there is ALOT of 1st and 2nd time builders.  There is ALOT of screen lockup, reboots, no boots that go on.  This is especially true of the extreme builds that people are doing.  I am just stating my opinion as a word of caution, not necessarily for people who are truly the enthusiast.  That's my 2 cents, and I'm sticking to it. ✌️

HAHA is right!  Good one.

To confirm, do you have the latest bios installed? Ram support has improved with more recent releases than older ones.
 
Generally speaking ram would default to a lower speed on first boot and it is unusual to not even make that. Problems usually only appear once higher speeds (XMP) are enabled. On Asus boards they have DOCP and DOCP Standard settings. One tries to reach rated ram speed, whereas the other sticks to preferred values. I don't know if Gigabyte has similar.

First post on this forum, forgive me. 
 
As of right now, I am running my G.Skill Trident Z memory at 3000MHz (although it supports 3200MHz, I was experiencing issues at this frequency myself). Although I have had no issues with that specific memory frequency, AM4 is known to be pretty finicky when it comes to ram. You say that you aren't "booting properly"; by this do you mean into windows or is nothing happening at all? If you can access the bios, try to set the memory to 2933 and see if it solves your problem.

Hello! So I've run into a bit of a pickle in upgrading my system. I'd been doing incremental upgrades over time, and this CPU/Motherboard (Ryzen 3900X/Aorus X570 Pro Wifi)  was supposed to be the final one. Unfortunately, after quite some time troubleshooting, I found that it wasn't booting properly because of the RAM I was using (32 GB Corsair Vengeance RGB @ 3000Mhz). After switching over to some older 16GB kit, it worked without a hitch. So, I went through the Motherboard's compatibility site and saw the weirdest thing: it supports 3200 MHz and 2933 MHz, but not 3000? I thought that was weird, but I was wondering if there was any way I could overclock or downclock to match the required speeds? Problem is, I can't boot with this RAM installed. Has anyone else experienced a weird issue like this and gotten around it? Would be a shame if I have to buy another set of memory. Thanks for any help!

JSON.NET is your best friend for C#. I don't know a .NET dev that doesn't use it.