This past weekend, May 20-22, I attended WordCamp Minneapolis 2016 (twitter hash tag #wcmpls) which was a huge lot of fun. I haven’t looked at WordPress and PHP in years, at least since around 2007. A lot has changed, and a lot hasn’t changed. I also found a really welcoming community among the #wcmpls crowd.
Since I stopped using it, WordPress has only continued to grow and improve, thanks to the dedicated efforts of the WordPress open source community and project leaders.
It was also great to step away from the Ruby on Rails server-side environment I’ve been running in for the past many years and engage in a bit of nostalgia in PHP (and perhaps some nastalgia as well).
One of the things that made this event so much fun for me was all the people I already knew through GDI.
For the first time, #wcmpls had a Friday-before-the-conference technical day, and I chose to dive deep into the development track and learn about creating a custom theme from scratch.
This was wonderful because it met my dual needs of expressing my creativity in software building and relearning and extending my knowledge into the platform.
I ended up a little frustrated with the day, because what I was building didn’t work as I expected. Not so unusual during these massive teaching days; I certainly wouldn’t expect them to hold up everything until I understood what I was doing wrong.
Likewise, there’s still a bit of a feeling I got that as far as development practices go, things are still sometimes pretty loose as far as source control, continuous testing/integration, and what-not.
From my “can’t leave it unfinished” feeling from Friday, I spent a fair bit of time hitting up other people and working on getting a working custom theme with custom post types and custom taxonomy in place, even using bootstrap to drive the theme, which I find pretty awesome.
There was this thing called the “Happy Bar” (I think) – which I didn’t find out what it was until late Sunday afternoon, at which point I went over and promptly got great answers for some lingering questions.
My prior experience extended to child themes and small changes here and there in CSS and layout, but having a packaged custom theme example is really great.
The example custom theme code can be seen out on github and there’s a demo available, too.
As often happens, while you’re trying to solve one problem, you come with another, and in the midst of that, an idea is spawned to automate something, and then another yak is ready for shaving. Randall Monroe captures this, of course:
So, yeah, part of the day I worked on building a Thor tool to automatically build a Vagrant box provisioned with Ansible that would be usable as a WordPress custom theme and plugin development environment. Yeah, it’s still in progress …
But at least I did get a custom theme, custom post type, and custom taxonomy built! Yay!
There were lots of great talks and speakers. I only attended two talks on Saturday, and they were awesome.
Amy Gebhardt’s From Junior to Senior: Why We Teach
With that, and with all the bootcamps, however, there is a backpressure created as many firms and agencies don’t wish to hire inexperienced or junior developers.
Amy’s talk struck right to the heart of this, outlining why it’s a good idea, and once you decide to try it, how to engage them, and then how to bring them up to speed once they join your organization.
In her usual brilliant and high-energy way, Amy provided a lot of human and humane reasons for all of this, and presented her own difficulties in dealing with the third step of this, handling your own work and reactions when working with someone who needs a lot of hand-holding.
Eryn O’Neil’s Programmers Can UX Too: Avoiding the Programmer’s User Interface
Eryn’s talk was very enjoyable, she has rather good comedic timing, and knows her audience. (In fact, she spent quite a bit of time up front making sure she had the right audience, inviting people to leave if they though they wouldn’t get much out of her talk.)
Eryn’s message is right there in the title: as a developer, you, too, must understand enough about what your user is trying to accomplish, and that you really need to make your software enjoyable enough for the user to operate that they’ll continue to do so.
My comment to Eryn afterwards was that I was struck (again) by the importance of paying attention to the user, whom all the value of your code resides in. There are intrinsic values, certainly, and your own aesthetic values, but the actual value rests on whether or not the user will use your code. We build these things not to sit in a repository, but to be out in the world, solving problems for people.
The morning was taken up with a brunch at the [Fountain Room] in downtown Minneapolis, which if you’ve never been is pretty doggone spectacular. One of the top spots for wedding receptions, apparently.
The lightning talks were rather good, but I think the first two were speaking to bloggers as a business more than mere devs.
Shawn Pfunder’s Bicycle Freelancing.
Shawn uses a bicycle shop as analogy and metaphor for creating your own business.
5 main points:
- build a tribe
- secure space
- get together
- teach others
- get personal
Aaron Rosell’s Why Email Newsletters Help Bloggers Build Influence
Aaron presented a case study of one of his clients, who runs a fashion blog. She began also putting out a few different newsletters:
- blog teaser
- news / article / interest aggregator, not limited to fashion
- weekend edition, more articles, lots of personal stuff, things not found on the blog itself.
Aaron’s points are that if you’re a serious blogger, consider adding an e-mail (or e-mails) to your blog, and capture more attention, more readers, make yourself more personable, more accessible, and in addition, gather a lot more data about your readers so you understand them better.
Cate DeRosia’s Why You Should Embrace Failure
Cate’s talk restated something most people have heard before, but that bears repeating often, as it’s something that hasn’t been fully grokked and integrated into our culture very well:
“We learn from failure”
It’s really important to remember that when you’ve just deleted the corporate database, or cost the company $100,000 in accidental overcharges (okay, it only looked like it was $7000, and it was only a data error, but still…). The key thing is to learn from those mistakes. Fix the causes of the errors so they won’t happen again. Fix the causes of the causes of the errors, find the root cause and fix that. Keep improving.
Ultimately, failing can be a very positive experience once we get over the fear and frustration. That won’t go away, we are human after all, but we don’t have to let those feelings rule us.
He does speak way too fast, though. :D
Josh Broton’s WordPress+React: A Match Made In Heaven
Wow. Josh is like the most dynamic speaker ever. He’s bouncing around the podium, his slides are just lousy with animated GIFs and he’s astoundingly funny and engaging. That’s just the outside.
Inside, Josh’s talk was super engaging, and super informative. For most of the people attending, I think React is a completely new concept, but I was quite eager to see how it could be used.
The upshot, and this is the same conclusion I’ve reached on the Rails side, is that WordPress can and should be used only as an API source (your web service) and completely eschew any of it’s own views. It only delivers up JSON to a Single Page App (SPA) which is written in a way that is really outside the entire WordPress Loop.
When the user comes in to your site, the main WordPress page would just deliver the SPA to the browser, and subsequent interaction with WordPress would be entirely AJAX-driven.
It’s quite compelling, I think, and it will be interesting to see how much traction this concept gets in the WP community. I like it a lot.
- No slides yet for Josh’s talk. Coming soon, I hope.
I was pretty tired, but also pretty jazzed. I had such a great time, and I’m so happy to those who made this possible.
A special shout-out to Michelle Schulp who organized this super event, and lovingly opened up a space for me at the last minute. Most excellent work!
"Nastalgia" is just a word I made-up by accident when referring to that feeling where you look at something in the past and it makes you a bit sick.
Images were taken from the #wcmpls twitter search feed. Copied without persmission, credit goes to the originators. Apologies all around. I do appreciate your work.