Just finished cs50 need some guidance.
Just finished cs50 need some guidance.
My bachelor's in software engineering starts in quite a few months
I am thinking of downloading Linux and learning the Linux terminal using the Linux bible.
then learning video, photo, and vector editing.
After that finishing the rest of the cs50 except the scratch one.
Lastly, becoming extremely good at Python
How does it all sound?
Sorry if this is the wrong community to post
Apart from actual system administration or kernel developing, there's no real "learn Linux" .
Video/Photo/Vector editing on Linux is not "learning Linux", it's learning to use a tool which runs on Linux. You can learn to use Blender, Gimp or Inkscape on Windows. You don't edit videos/photos/vectors with the Linux kernel. You can even "learn the linux terminal" installing bash on Windows.
You can also install Visual Code or IDLE on Windows and on Linux. Learning to code on Visual Code or IDLE is not really "learning Linux".
Also going on distro hopping looking for the "perfect distro" many times means the hopper simply doesn't stick to one long enough to learn how to customize the environment to their liking (which usually means the window manager).
Most of the things you can do on the GUI, even the administration ones are just layers and layers of tools to make things "easier" - and they'll be different on each distro and release. Command line administration will change much less, or at least less frequently.
Things I consider "learning Linux" are for example:
-
installing Linux (specially a headless server)
-
understanding how to use the package managers - again, on the command line
-
understand how systemd works
-
(hard core) dive into the kernel workings
-
understand how grub works
-
learn the general filesystem structure
-
learn how to analyze logs
-
learn user administration and how the permissions (and extended permissions) work
-
learn how to integrate Linux to a Windows environment (join a workgroup or domain, share storage, authenticate users)
-
learn how to check resources usage and how to troubleshoot it
-
understand the nuances and of partitioning and when they are needed, as well as the different filesystems
-
etc (and /etc)
And yes, many of those are not strictly "Linux", but are specific to a Linux system, unlike photo editing.
Mostly good advice. I disagree on the headless server part though. Most people who are interesting in learning "Linux” have a much less reductive idea of what that means than you do, I think. Specifically, I think becoming a comfortable, fluent speaker of a typical Unix/Linux environment and userland is probably the most important thing. I think the best way to start doing that is to just live in Linux, and you’re not going to do that on a headless server. Learning the GUI that your distribution uses to add users isn’t important, but having a GUI where you can run standard browsers and photo editors and such is important, because otherwise, you’ll spend all your time in Windows and never have the chance to develop fluency in all the stuff that is actually important.
Limiting yourself to only using command line stuff I suspect does more harm than good, unless you’re hyper-motivated to learn fast. For most people, the smoother path is probably more gradual. Start with Gnome or whatever and just use the computer. Over many years, you’ll learn a lot of piecemeal things just by becoming frustrated with some problem and learning how to solve it. I do think it’s good advice to do as much from a shell as you can from day one. Instead of using the GUI to copy files, learn to do it from a shell. Just don’t feel like you aren’t allowed to use Firefox to browse the web.
I agree; I mentioned headless server because that would be a more "pure" and general Linux administration - learning how to administer a SUSE Linux using the graphical yast tool won't translate as well to general Linux admin as if you learn and understand how to fo it in the command line and config files.
And absolutely; one can use Firefox, LibreOffice and any other tool on Linux, but I don't consider that as "learning" or "knowing" Linux. My wife uses exclusively Linux for 20+ years (because when she left her job where they still had Windows 95, that's what the desktop at home ran; kubuntu). She does text editing, internet banking, shopping, browsing, printing, everything there (even updates sw through the gui package manager), but she doesn't "know Linux".
You can setup a Linux system for a computer illiterate, and they may happily learn how to use it for their social media and streaming consuming, and whatever endusers do in their computers, without ever knowing that's "Linux".
Strictly speaking, that already happens. How many Android users know they are running on a Linux kernel?
That's why when OP said "learn Linux", I prioritized the admin on command line; as you don't need to really "learn Linux" to interact with it through automated/graphical admin tools (no shame on doing it, they're sometimes quicker and more practical than command line).
What I mean is that learning how to use cPanel or Yast is useful, but you're learning how to administer as system through a tool, which in theory could even be adapted to administer a non-Linux system.
Thank you for the detailed advice.
-
What is your end goal with this? Going for BSc in Computer Science / Engineering would enable you to become a developer / computer scientist.
Photo/video/vector editing seems very out of place in your plan. That's just another domain. If you're passionate about those visual arts, that's great and more power to you, but know they're not relevant for a computer scientist. Src: I've been there.
Regarding everything else you've said, it seems to me that you're learning stuff without a direction and just because you've heard those things (cs50 / linux), are important. I suggest you choose a moderately difficult task (game, app, tool, website, ehatever) that seems interesting for you to create, (install linux) and start working on it, and focus on finishing it. You'll learn a lot on the way and gain a broader understanding of how a project is pieced together. Most importantly, you'll figure out what you don't know, and thus eill have a direction going forward.
And don't get me wrong, you're right, you can gain a lot of valuable knowledge by going through cs50 or learning to use the linux terminal, but it's not really useful unless information, unless you apply it to a project.
The reason I am learning photo/video editing is because my sibling has done game dev/web, freelance and office work, those things come in handy to showcase your work and for a lot of other uses.
The reason for learning Linux is because of this post and I am thinking of (later on after finishing my bachelors) getting a Red Hat certificate since I have seen multiple job posting on LinkedIn related to it. So I was thinking of downloading Fedora and learning the Linux terminal now, to get comfortable with it.
Thanks for your input, I should definitely focus on making and finishing projects.
As other poster recommended, you should by all means install Linux and learn by using it as a daily driver.