I’m not an experienced professional but I have more websites and blogs on the topics of my career than any of the other people at my workplace do. That might be because they spend a lot of time actually doing the work, while I am an inexperienced young newbie with lots of free time and mad web design skillz. Or it may be because they know so much about the topic that blogging disconnected bits and pieces that might do more harm than good doesn’t make sense to them.
But it makes great sense to me, because every little thing I discover (usually because they showed me) is cool and interesting and (to me) seems to solve all of my problems (at least until I run into the next one).
Therefore I blog “how to” tips all the time. Even if they are often short-sighted, usually incomplete, and mostly lacking in sufficient detail. My blogs get hella traffic. I’m kind of a big deal on the Internet (amongst my Facebook friends). I might even get a raise because of that.
Today’s post is about Advanced IT Topic “A”. I had no idea about this stuff until this week, when my plain vanilla install of Open Source MegaPackage broke. It was throwing error messages like a circus monkey. Most were crazy incomprehensible but one caught my eye. I asked the old dude in my department about it, and he gave me a wicked smart command to run from the command line of the web server. I posted it below, so you can use it too. It might totally fix your broken MegaPackage install, especially if you get error messages like the one I got (which I used in the title of this post, so you could find it via Google).
So if you got that error, just try this command. It might work for you, too! If not, just keep trying stuff, because you might eventually come across a command that works for you, too. That’s how you learn! Or else you can just try a different open Source MegaPackage and see if that one works. No sense wasting hella time if the bugs seem too strong.
Oh and be sure to blog about your experiences, to help others!