Not saying it’d hurt, but I’ve never worked anywhere that had network teams managing docker (that’d be a different team). Linux knowledge is just enough to install a vendor supplied appliance on your hypervisor of choice (managed by a different team), anything more than that would have the OS managed by a different team. And I really haven’t seen them script much of anything in any language, they have prebuilt tools to do any mass config changes or monitoring or whatever.
They are generally way more concerned about working with horribly convoluted routing issues, misbehaving BGP, firewall policies, etc.
Fisuxcel@exploding-heads.com 1 year ago
im linux user so that would not be a big problem, python might though
masterofballs@exploding-heads.com 1 year ago
Honestly you can pick it up. You’ll need to understand and apply what is a for loop, a class, a map, a set, http request, snmp request, byte vs bit, ip 4 vs 6, what is a container, what is a vm, internet vs intranet, port forwarding, rate limiting, load balancing, network shares, maybe elasta search queries.
That’s mostly it. In the states a lot of vets get hired as network engineers without degrees. They sometimes have it experience in the military.
squashkin@exploding-heads.com 1 year ago
learn some python with automatetheboringstuff.com maybe