i think i mentioned before my coworker is sort of devops. it's more of an install/configure/maintain versus traditional coders.
IMO one of the first things you should do is learn basic scripting for your OS. if you're a microsoft person, learn powershell. if you're linux (or mac), then get comfortable with shell scripting. you will be writing a lot of scripts to interact with just about anything. you should be comfortable reading in a config file, parsing to get the data you want, and sending it as a param to another program (or writing to another config file). moving files, creating directories, deleting files older than x days, etc.
i do recommend python in addition to powershell/shell. it works on all the major OS.
i don't know what your coding experience is. generally, you don't simply write code, compile, and you're done. i'll describe a little bit of our build process.
we use GIT/Subversion for source control. so we checkout from source control, then write our code, use maven to build a deployable file so we can test it (keeping resources in artifactory), and then commit it. when it gets committed, jenkins pulls the code from source control, builds it, dockerizes it, and moves it to another server. if it fails to build (missing code, bad configuration, etc) we get alerts that we broke the build.
some companies do more than this, some companies do less. but it gives you an idea of what to look into. you need to understand the overall picture.
This post was edited by carteblanche on Jul 8 2015 06:26pm