But what if I want to type other fuck-based phrases?
Hmm, my motherboard (Asus) just has a reset button that flashes the contents of the secondary ROM to the primary ROM. If there's any problem getting the primary to POST, you just push the button and it reflashes the primary from the secondary, so you're back in the original state. It's not a one-shot, because the contents of the secondary don't change. You can use it as many times as you need to.
Once you get a good POST from the primary, it updates the secondary. I've never had an issue with this system.
Phone mainboards are very different, which is a big part of why maintaining third-party phone OSes is such difficult work, and why GrapheneOS constrains itself to specific devices.
The best answer is actually to pay more attention to your local elections than national ones, and vote based on issues that impact you directly.
Just type in your full real name on our free website! We definitely aren't associating it with your IP address, location information, browser fingerprint, and anything else we can scrape from your cookies, and then selling all of it to data brokers! Honest!
Ever since I bought a desktop motherboard with a secondary BIOS/UEFI ROM, I'll never buy one without it again. The peace of mind alone is worth any extra cost. And it has saved me from failed flashes twice.
In vino, veritas
Computer networking is basically a completely different field from operating systems and programming, though obviously some of the concepts are relevant. Turns out plugging these things into each other so that they can share information in a useful way is kind of difficult. A lot of very smart people have been working on it for almost 70 years, and frankly it's still a fucking mess, so don't feel bad if you feel a little lost.
Starting with the basics is the right instinct, in my opinion. Start with the OSI model:

https://jakarta.telkomuniversity.ac.id/7-osi-layer-the-building-blocks-of-networking/
https://www.geeksforgeeks.org/computer-networks/osi-model-analogy-osi-7-layers-explained/
This helps to break down the actual functioning of the network into logical steps. It's very helpful when you're trying to visualize the operation of some of the more abstract bits of the technology stack (like TCP/UDP), and when you're trying to think through what piece of it might be causing your problem in the moment (the router is on and the cables are plugged in, why is there no connection?). It's a map that can help you when you're lost. It's also a guide to how a lot of people who work on networking technology think, so it can help you understand how things are supposed to work.
Beyond that, Professor Messer is a great resource: https://www.professormesser.com/
If you feel reasonably confident with computer hardware components and various types of cable connectors, you can probably skip the A+ part and go straight into Network+. Because you're doing this as a home hobbyist (not for the actual certification), I recommend just listening to the courses like you would a podcast. Don't try to memorize or fully understand everything, just use it to get a grasp of the terminology and purpose of the various pieces.
I also recommend taking on a project to gain experience. Implenting PiHole https://pi-hole.net/ for your home network will cover routing, DHCP and DNS, plus you can do it with a Docker container.
Look they're RGB for end-user personalization, OK? Most people just leave them on the default blue, but they can be pink or yellow or whatever you want. RTFM
Er, and if your friend asked you directly how that specific thing was going for you, how would you handle that?




Windows as a home user desktop is definitely coasting on momentum, though it is also the OS deployed on most new PCs which keeps it going.
I think the only thing really keeping Microsoft relevant is Active Directory (and Azure by extension) because a lot of organizations are dependent on AD internally, and there still aren't really any good alternatives that check all the same boxes. You could probably cobble together a working solution for ~90% of it with open source software, but it would be clunky, fragmented and feature-poor compared to an on-prem AD system. It would require a lot more administrative overhead to configure and maintain it, and user management would be a mess.