Knowing who to talk to about a given issue (for a large company). Since you say &quot;new career&quot;, I assume you&#x27;re starting a new job somewhere. I work for a fairly large organization that&#x27;s heavily silo&#x27;d with regards to responsibilities. When something goes wrong, I often have to work with 4 or 5 departments, each of which has some folks who are helpful and folks who are &#x27;blockers&#x27;. Figuring out who the right folks to talk to for a given issue can make the difference between solving something in minutes or hours (days). Likewise, making sure folks know my responsibilities and when to bug (or, more importantly, not bug) me.<p>Know your domain tools and always be looking for new (to you) ones. If you&#x27;re new and in the linux sysadmin domain, you&#x27;ll be doing a lot of &quot;oh wow, I didn&#x27;t know about XYZ&quot;. Find the old stuff that&#x27;s been around forever (and likely installed everywhere) before jumping on the new hotness that&#x27;ll require big changes to your systems to install. I like HN for some of this. Read the comments for the &#x27;vim&#x2F;tmux&#x2F;bash&#x2F;cron&#x2F;git guide&#x27; entries that get reposted every few weeks. I guarantee somewhere in the comments, you&#x27;ll find something you didn&#x27;t know that&#x27;ll help.<p>Scripting tedious tasks is huge. Learning the bits of shell&#x2F;perl&#x2F;python&#x2F;ruby&#x2F;whatever that interact with the tasks you do day-to-day can be very beneficial. Automate all the things.