You can't just let the fires hang, so you need to start with putting fires out. Just do that with the long term in mind. Start putting fires out by solving the underlying issue and not just patching the symptom. The next step is to implement monitoring. Something like Nagios or Cacti. This process requires you to inventory systems/services and document those systems/services. It is a productive way to start peeking into the setup. It also helps you to notice fires before others do, so you can put them out before anyone has to ask you about it. "Fires" often exist long before anyone tells you about it. People just deal with issues until it prevents them from getting something urgent done. Then it becomes a fire. With all that in place, you will get ahead of the fires and better understand the systems under your care. Now you can start to plan and rebuild "in your own image".

So is the next big thing going to be mining for bottles?

I suggest you become a regular at the local coffee shop. Something I used to do was set up a chess board, buy a cup of coffee, and wait for people to challenge me to a game. Ask people if they want to play if they are eying the board. You meet lots of people, get to chat with them, and there is no commitment by anyone so it isn't that scary. If you have a good time offer up your number or tell them when you will be in next for another game. This doesn't have to be chess. Just make it a 2 or 3 person game that is commonly know and doesn't take to long to play. Chess, Checkers, Cribbage, domino, etc. are perfect. This will get you used to talking to strangers at the drop of a hat, you will start to know people around town, and have a good time. Even if the activity itself isn't leading to long term relationships the ability to talk to random people at the drop of a hat will help you when that pretty girl passes you in a store and will get further in your professional life, etc.

This doesn't make it invalid. This makes it un-scientific. Therefore, it doesn't belong in science class.