There are three different sets of skills involved in what you are talking about. I don’t know which one do you want to focus on.
There is the system administrator (sysadmin) skill set related to “the ability to work with servers and websites”—systadmins are “responsible for the library’s network and site” and they “maintain a library’s network and computers”. It mostly has to do with deep understanding of Windows and/or Unixoid operating systems and doesn’t involve that much programming per se and that mostly in shell scripts and/or swiss-army-knife languages like Perl.
There is the web developer skill set related to websites and it involves, nowadays, a mix of HTML (which is NOT a programming language), Javascript, and a database backend (usually but not always SQL).
And finally there is the programmer (err… software engineer) skill set which varies a lot depending on the context, but is generally about the ability to architect, construct, and maintain complex software systems or subsystems. Different subfields tend to use different programming languages so there is no single recommendation to be made.
Most of the positions I apply for would involve knowledge of sysadmin work and, rarely, web developer work. As you can likely tell, my position is not as the sysadmin or web developer, but rather as the manager under whom these positions work.
Yes, that’s a little different. IT frequently doesn’t entail a lot of coding by hand. There’s a lot of copying and pasting code from scripts you come across, and then editing the code to get it to run properly on your system. An introductory course in computer science will help with that, but some of the more advanced stuff you’ll encounter will simply never come up. What you really need is basic familiarity with a wide variety of different frameworks; how to browse through them to find what you’re looking for. The hard part isn’t knowing how to solve the problem; it’s knowing where to look to find the problem. On the web development side, you will want to see what content management system your company is using and learn how that CMS functions. You can use builtwith.com to figure it out if you don’t already know. For each language or framework, make sure you focus on just the basics before moving onto a new one. If you try to go in-depth with all of them you’re never going to get through it all. When you have to do something in that language, just open up a cheat sheet for it, and use that to guide you.
There are three different sets of skills involved in what you are talking about. I don’t know which one do you want to focus on.
There is the system administrator (sysadmin) skill set related to “the ability to work with servers and websites”—systadmins are “responsible for the library’s network and site” and they “maintain a library’s network and computers”. It mostly has to do with deep understanding of Windows and/or Unixoid operating systems and doesn’t involve that much programming per se and that mostly in shell scripts and/or swiss-army-knife languages like Perl.
There is the web developer skill set related to websites and it involves, nowadays, a mix of HTML (which is NOT a programming language), Javascript, and a database backend (usually but not always SQL).
And finally there is the programmer (err… software engineer) skill set which varies a lot depending on the context, but is generally about the ability to architect, construct, and maintain complex software systems or subsystems. Different subfields tend to use different programming languages so there is no single recommendation to be made.
Thank you kindly for the break down.
Most of the positions I apply for would involve knowledge of sysadmin work and, rarely, web developer work. As you can likely tell, my position is not as the sysadmin or web developer, but rather as the manager under whom these positions work.
Yes, that’s a little different. IT frequently doesn’t entail a lot of coding by hand. There’s a lot of copying and pasting code from scripts you come across, and then editing the code to get it to run properly on your system. An introductory course in computer science will help with that, but some of the more advanced stuff you’ll encounter will simply never come up. What you really need is basic familiarity with a wide variety of different frameworks; how to browse through them to find what you’re looking for. The hard part isn’t knowing how to solve the problem; it’s knowing where to look to find the problem. On the web development side, you will want to see what content management system your company is using and learn how that CMS functions. You can use builtwith.com to figure it out if you don’t already know. For each language or framework, make sure you focus on just the basics before moving onto a new one. If you try to go in-depth with all of them you’re never going to get through it all. When you have to do something in that language, just open up a cheat sheet for it, and use that to guide you.
I see. Thank you for the explanation and the link.