- Edited
Absolutely not correct, networking failover is not part of the sysadmin role. While a storage failover is indeed a part of the role.nuclearcat wrote Sysadmin is company puzzle solver. Sysadmin that refuse to know basics (and knowing networking stuff like failover is indeed basics) - is bad sysadmin.
https://www.sdxcentral.com/industry/career/skills/top-10-system-administrator-skills/
Check N2
don't mixup the word 'failover' over multiple things.
Can you please define what's a "Developer" in order for us to understand what you're exactly referring to? because I still disagree with you on this one. There's literally a "Developer" position just like a "Network Engineer" position.nuclearcat wrote Thats correct, but as i said, sysadmin without developer skills is very low paid position this days, unless he is extremely qualified and certified in specific niche(for example CCIE) and his job need this knowledge. And yes, this is only case where you can afford saying that you dont need to know specific unrelated fields.
If sysadmin learned programming a bit, then he can try to apply to companies who want "devops" (but dont really know what it means), it is paid way better.
Again you're saying things from the lebanese perspective. I am not applying in Lebanon due to this mixup on roles and responsibilities that the companies do.
I can tell you, I worked for several Silicon Valley companies that had ties with Facebook, and NON of them had such an enforcement for languages. They let you do whatever you want to get the job done, there are literally other people whom exist and are hired to make those things dynamic in organizations such as documenting, analyzing code for backwards and forwards compatibility which have to be adaptable across teams and departments.nuclearcat wrote Big companies actually have strict requirements for procedures/languages/etc you use in automation. They wont accept any language you like to use.
You will have to use automation procedures approved by company documents and teamlead.
it is. But not in here and definitely not in small companies because they do not have the requirements and people to make things dynamic.nuclearcat wrote No, its not up to person, unless it is very small messy company. No sane company will allow person to use any language he wants, because they need to be sure, that they if this person leave, they can find replacement who can continue supporting things he did. And it is some exotic language or approaches - it will be big problem for them.
I stopped reading when you said "ISP". Now i get younuclearcat wrote Not experienced...
You are telling that guy who run 4 large ISPs in Lebanon, and who did (minor) commits to Linux kernel and discovered CVE in netfilter subsystem :)
I did, from ipchains to nft/bpf, including writing my custom load balancer for sort of userspace port forwarder of HTTPS with SNI analysis.
Not when you have different operating systems and I only gave "some" of the modules, let alone custom modules and lua scripts.nuclearcat wrote You dont need to recompile nginx to add brotli or any other custom module. Yes you will use source tree of nginx, but it will be used only to make .so file of module. This job literally will take minutes, not even hours.
self-signed certificates are not something to do on production servers at all and is more of a network thing again.nuclearcat wrote Certificate... i did run them since 200x, there is nothing complex at all to generate certificate, self-sign (or sign at CA), and then put files in config. Also minutes.
I'm a bit familiar with this stuff, its not about ssl, but close enough as parsing certificates is similar hell : https://github.com/nuclearcat/cedarkey
The only thing worse than PEM format is writing parser of them using openssl libraries.
this allows you to have more control over your network.
Some companies do not like their website to have certificates issued by "Let's Encrypt" and rather have it from "Verisign", "GlobalSign", "Comodo", "Digicert" etc.
Yes, as you mentioned it's about parsing the certificate because such providers doesn't have a tool to use and you gotta do some scripting in order to renew those. And to be fair? this is a mandatory point to write on your CV/Resume because a lot of "Huge" companies even Google, sometimes in the past few years failed to renew a subdomain certificate and even forgot to renew the entire domain lease in the first place, those are important things to keep a company going and it is becoming more concerning over the recent years that huge companies are being targetted in this area (part of infosec), domain take over etc.
just to make one thing clear, I'm not a perfect sysadmin and I never claimed so, we all have our ups and downs and I clearly need to improve in some areas but our main topic is about "Roles" and "Hiring Process" which is biased