Now in beta!

Yes, I’m rebooting the site. Again. This time, I have a plan. More so, I have a couple of accountability partners keeping me honest. Allow me to explain…

New Year, Same Me

I’ve lost track of how many times I’ve written a post like this. Especially at this time of year. I’m sure you have too, especially after a down year. New year, new me. You see it all over social media. As I’m sure you’re aware, it’s all bullshit.

I’m turning 35 in a few days. I’m old enough now to know that there isn’t another “new me” coming. I’ve changed a lot over the 17 years I’ve been an adult. Usually, I’ve grown. Sometimes I’ve regressed. Occasionally, it’s a mix of both with the same year, hopefully ending on the positive.

But that doesn’t mean I can’t get better. I just have to build on what’s there. That’s not just the thesis of this article, but the new purpose of this website. I’ve said this before too, but this time I mean it. I’m older. Hopefully wiser. Maybe a little bit desperate. Most importantly though, I’m committed. I don’t have any other choice.

Never Finished, On Purpose

Walt Disney famously said about Disneyland that “Disneyland will never be completed. It will continue to grow as long as there is imagination left in the world.” That sentiment is one most developers are intimately familiar with. We’re always thinking up something else we can do for a project. If we have the time or the budget, we do it. Plenty of times we don’t and those ideas fall by the wayside. More often than not, those great ideas get half-implemented on a client project but never get touched again.

The idea behind this site, and the larger project it is built on, is progress. WordPress is changing, and more importantly how we develop WordPress is changing. Frontenders like me who have avoided JavaScript because we just didn’t need it are going to be left behind as blocks become more and more important. I was in the audience when Matt Mullenweg told the room to “learn JavaScript deeply.” I didn’t take him seriously, figuring that I’d be able to get by because when it comes down to it, so much of what we do is HTML and CSS at its core. I should have heeded Matt’s warning.

Being late to the party sucks, but it isn’t a death sentence. There were plenty of search engines before Google launched, but they did it better than anyone else, at least initially, and now their name is a verb. I don’t expect my company to be the next Google. I’m not insane. But I do know that if I learn, grow, and most importantly adapt at a rapid pace, I’ll survive.

Documenting Everything

I’ll be doing my best to document everything I can. When I change the code on the site, I’ll tell you. Regardless of the reason, even if it makes me look like a dumbass. Yeah, I’ve been making stuff for the Internet professionally for seven years now, but I still make mistakes. It’s important for younger, newer developers to see people more experienced not only acknowledge their mistakes but see how they fix them.

Beyond my mistakes, I’ll be documenting the development of Wyvern, the theme that runs this site. Right now, this site looks terrible, and that’s somewhat on purpose. The idea is that every time I publish a new article, at least for a while, or finish a client project, the site will improve. I’ll take what I’ve learned or built, and roll it back into Wyvern proper. This site will, hopefully, become the shining example of what Wyvern is capable of.

Perhaps most importantly, I plan on explaining why I made the choices I’ve made. For instance, I’m currently debating whether or not I should follow the Genesis model for themes or the Underscores model – do I use one base theme that keeps updating over time, with child themes containing the customizations, or do I constantly improve the base and let each project serve as a relic of that particular moment of my development skills. I haven’t decided yet, but once I have, I’ll talk about it in this space.

Regular Schedule

Thanks to my accountability partners, something I highly recommend, I’m actually going to be able to keep a regular writing schedule. I’m building it into my general work schedule. Soon, I’ll be writing for three platforms: here, my Star Wars news site, and my company site (currently under reconstruction). My target is one article a week for this site. It won’t always be a development post. Sometimes it will be a life update or passing on knowledge I’ve gathered in regards to living with type II diabetes at a young(ish) age. In general, content/thoughts/ideas that don’t belong on the other two sites end up here. Those sites will have their own schedules as well.

Throughout my time in the WordPress community, I’ve been lucky to have the patience and support of so many friends and acquaintances. I’m betting on the idea that I haven’t worn out my welcome. With that in mind, I look forward to any and all feedback you’re willing to provide. Just leave it in the comments, or drop me a line if you’d prefer that feedback remain private.

Oh, and about that beta thing. This should explain it.

Adam Soucie
Adam is a WordPress developer based in Orlando, FL, and the founder/CEO of Impossibly Creative. He is a member of the WordPress Orlando organizing team and a frequent speaker at the WordPress Orlando meetup.


Leave a Reply

Your email address will not be published.