You don't need to code but just understand how unix works,like at a sysadmin level. Then get some older hardware and play, play around with some distros, fix the issues that will inevitably crop up on your hardware so you can fix other issues on other hardware, learn why arch is different than debian and what drove those decisions.
Get something structured on unix (not linux) at first like Udemy or GC+ and then google everything (I know, but it's still the best for this kind of thing). Once you make the transition you'll get out of the cycle of new and shiny, focus on getting stuff done, you'll save a ton on hardware and no more Apple and google.
You don't need to code but just understand how unix works,like at a sysadmin level. Then get some older hardware and play, play around with some distros, fix the issues that will inevitably crop up on your hardware so you can fix other issues on other hardware, learn why arch is different than debian and what drove those decisions.
Get something structured on ***unix*** (not linux) at first like Udemy or GC+ and then google everything (I know, but it's still the best for this kind of thing). Once you make the transition you'll get out of the cycle of new and shiny, focus on getting stuff done, you'll save a ton on hardware and no more Apple and google.
(post is archived)