Hello, Blog

Dear Blog,

I hope this finds you well. Do you remember a time on the internet when socializing was done via dotcoms and not through social media? We used to open our blog posts with an apology for being away for a while, and it never meant anything because nobody cared how long you were gone. Everyone would just be glad that you were still around. I almost committed to an apology at the beginning of this paragraph, but in 2018 I bet we're past that.

Blog, you've made substantial contributions to my life. You taught me the foundation for what I know about web development. You taught me PHP and JavaScript and jQuery and LESS and SCSS and WHM and cPanel and to be generous to other devs and scatter <!--these traffic cones--> in front of the potholes in the hazardous streets of codeland.

But I haven't been working with WordPress lately. My last few years have been a mixed bag of CMS's. WordPress was in there, sure. But the large part of those years was with a flat-file CMS, and I must say, I did greatly appreciate the security and flexibility of not having to tangle with a database. I did not miss MySQL. The whole keeping a CMS updated and patched-as-needed and secure and sanitized is just a never-ending game of cat-and-mouseover();.jk, js, this was CSS.

Here's the thing: I'm just an okay coder. Not quite mediocre, as web dev is an industry that requires being quick and efficient. If I already know the documentation, love the rush of a good code sprint or debug fumigation. But you can't always be up to date on your documentation if you need that time for production. And if StackOverflow doesn't know the answer, you can't simmer on that problem for too long before you have to get back in there and >git init a plan B. The show must go on.

Another excuse reason for my spending so much time away is that, uh, wow, you just kinda propped up a lot of my bad writing for the world to see, didn't you? Sorry to have made you go through that. The sentiments are sincere, but the execution is just a little too purple and downright angsty for my recent tastes. I've made many of the posts private for now. I'll maybe pick through them later to see which ones are appropriate for public display and which ones to sweep under the rug because they are, oof, ah, echo $facepalm;. But given time, who knows? I have new perspectives after reaching my mid-30's that are not completely congruous with those of the Me™ of the past. I'd like to think I'm now wiser, but I'm also wise enough to know I am never as wise as I think I am.

The short of it is that I have a maximum capacity for how much cringing at myself I can do, and a close look at my past work pins that pressure gauge in the red. I don't want to spend all of my time rolling my eyes when I can be looking forward.

I'd hate for anyone to be the same person for far too long. It would be a shame to not want to always grow into a better self.

The same goes for you, too, blog. I have developed a taste for markdown and YAML and flat-file life, but still prefer the hooks and documentation and extensibility of WordPress. Maybe if you work with me we can come up with a compromise. Maybe I'm totally wrong, and that I should return to working with MySQL to be standards compliant. Maybe someday I'll put something together and someone will fork the idea on github. Don't let your dreams be dreams, the internet told us. We will heed.

WHOIS tells me you've been part of my life for just over a decade. So you've seen all of it. In the latter half of that decade, I disappeared into corporate America and forgot about blogland. I forgot what you've done and can still do for me. You introduced me to the people who would help shape my career, and to the web languages I would use to communicate with them. If you can't help me figure out my next move, nothing can.

In our first post, you helped me say "Hello, World!" I am remiss to have not returned your salutation.

Good to see you again.

Let's get to work.