There isn’t a singular “right way”, but you need to know the basics of computer science like OOP, algorithms, and data structures if you want to be a decent programmer. Everyone has their own advice, but here’s mine for whatever it’s worth.
If you want to be a sysadmin, you should learn command line languages like batch, sed, and bash (or a superset language like batsh). Start simple and don’t overwhelm yourself, these languages can behave strangely and directly impact your OS.
When you have a basic grasp on those languages (don’t need to get too complex, just know what you’re doing on the CLI), I’d recommend learning Python so you can better learn OOP and study networking while following along with the flask and socket libraries. The particular language doesn’t matter as much as the actual techniques you’ll learn, so don’t get hung up if you know or want to learn a different language.
Finally, make sure you understand the hardware, software, and firmware side of things. I’d avoid compTIA certs out of principle, but they’re the most recognizable IT certification a person can get. You need to have some understanding of operating systems, and need to understand how to troubleshoot beyond power cycling
Here’s a nickel kid. Get yourself a better computer.
If you want to be a sysadmin learn Linux/Unix. Basic bash scripting might be useful down the line to help understand a bit of what’s going on under the hood.
IMHO networking would probably be a better secondary place to focus for a sysadmin track rather than OOP concepts, algorithms etc.
Thank you for the response. I’ll be sure to up my PC hardware game soon since I have plans to leap into a career shift. What kinds of specs would look good in your opinion?
My advice would be install any free virtualization software (virtualbox comes to mind) and create some linux VMs, dick around with them. No need to upgrade anything unless you’re using some ancient potato with more than 10 years
As for Linux stuff grab something small and low powered (raspberry pi etc) and start installing some distros! The possibilities are really endless. Setup a network wide ad blocker, start your own IPTV server, you can setup a networked radio receiver, WireGuard for VPNs. Immerse yourself and figure out what you find interesting.
There is a website called roadmap.sh which has both Skill and Role based roadmaps to learn how to program. There is no actual “SysAdmin” role path since our job can technically have several routes by itself.
I personally use Debian at my org, and found Python and Bash enough to automate small things that need to be done in a regular basis.
But if for example, you were a Windows SysAdmin you’d have to learn to use PowerShell or VBS (idk if those scripts are still a thing).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
What actually is supposed to be the ideal way to learn? Say, for someone trying to be a sysadmin
College
There isn’t a singular “right way”, but you need to know the basics of computer science like OOP, algorithms, and data structures if you want to be a decent programmer. Everyone has their own advice, but here’s mine for whatever it’s worth.
If you want to be a sysadmin, you should learn command line languages like batch, sed, and bash (or a superset language like batsh). Start simple and don’t overwhelm yourself, these languages can behave strangely and directly impact your OS.
When you have a basic grasp on those languages (don’t need to get too complex, just know what you’re doing on the CLI), I’d recommend learning Python so you can better learn OOP and study networking while following along with the flask and socket libraries. The particular language doesn’t matter as much as the actual techniques you’ll learn, so don’t get hung up if you know or want to learn a different language.
Finally, make sure you understand the hardware, software, and firmware side of things. I’d avoid compTIA certs out of principle, but they’re the most recognizable IT certification a person can get. You need to have some understanding of operating systems, and need to understand how to troubleshoot beyond power cycling
Here’s a nickel kid. Get yourself a better computer.
If you want to be a sysadmin learn Linux/Unix. Basic bash scripting might be useful down the line to help understand a bit of what’s going on under the hood.
IMHO networking would probably be a better secondary place to focus for a sysadmin track rather than OOP concepts, algorithms etc.
Thank you for the response. I’ll be sure to up my PC hardware game soon since I have plans to leap into a career shift. What kinds of specs would look good in your opinion?
My advice would be install any free virtualization software (virtualbox comes to mind) and create some linux VMs, dick around with them. No need to upgrade anything unless you’re using some ancient potato with more than 10 years
It’s a reference from an old comic
https://blogs.warwick.ac.uk/images/steverumsby/2004/09/20/1b2.JPG
As for Linux stuff grab something small and low powered (raspberry pi etc) and start installing some distros! The possibilities are really endless. Setup a network wide ad blocker, start your own IPTV server, you can setup a networked radio receiver, WireGuard for VPNs. Immerse yourself and figure out what you find interesting.
There is a website called roadmap.sh which has both Skill and Role based roadmaps to learn how to program. There is no actual “SysAdmin” role path since our job can technically have several routes by itself.
I personally use Debian at my org, and found Python and Bash enough to automate small things that need to be done in a regular basis.
But if for example, you were a Windows SysAdmin you’d have to learn to use PowerShell or VBS (idk if those scripts are still a thing).
Windows sys admin here, I haven’t seen a vbs script in ages. I’m primarily in PowerShell these days.