No problem. As for IT being repetitive, it depends on where you work as well. Where I work, I was slowly building up a list of canned responses to people and was not really "thinking" in my job. When this starts happening, I start handing out resumes. I need to be challenged at my job or I get bored.
As a DBA, I find I am challenged a lot more. Plus my boss is good at keeping me busy. But having the IT background is also helpful. When I see something break, my first thought isn't that the database is bad. My first thought is "lets gather evidence of what happened and why and then decide how best to solve it". Sometimes it means re-running a SQL job. Sometimes it means rebooting a VM. Sometimes it means doing nothing (for me) as the problem isn't related to the database or software I manage.
If you are thinking of working in the IT industry (including being a DBA), one of the best resources for troubleshooting is the logs. When somebody reports a problem, check the logs. Doesn't matter what software it is. Find the logs, and read them.
Also, before posting any logs or SQL code online, always make sure you are allowed to. That is, that it doesn't contain any company proprietary data.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.