Current status: enjoying the beach.
Found this article especially relevant as I'm currently following just behind our UX team prototyping in code as they design early mockups using InVision. The spirit of what we're doing is aiming for the "collaborative" narrative outlined in this post, but the fact that there is still a handoff occasionally makes it feel like what the article calls “bridging the gap.” It is very early days, but I'm anxious for a future where more of our tools can speak the same language and actually impact code that will be used in the final project. Still a long way to go on that front though.
I found this embedded quote to be especially insightful:
Production code is a surrogate for decision-making power. Production code is the source of truth. It is the realtime sum total of all the conversations, all the decisions, all the politics…it is everything. Whoever is pushing code to production is running the product. Everyone else only has influence. Rebekah Cox
I don't necessarily want all of that power. In a perfect world, I help enable others to assert control on the areas of the project where they are experts. With our current tools there is just too much risk of things being lost in translation. Today we're doing the best we can with the tools we have and against all odds we often find a way to make it work.
Back in June I got a chance to see a taping of How Did This Get Made, which is one of my all time favorite podcasts. I was coming home from Texas that day and just barely made it to the show in time because my flight was delayed. Thankfully all of the travel stress was worth it - seeing the show live was amazing, and our 80's BMX Bike movie Rad was the best kind of bad movie.
They released the live show as a podcast episode a few weeks back, and it is well worth the listen.
In June I had the chance to see two dates of the Be More Kind tour with Frank Turner and the Sleeping Souls. Both shows had completely different and amazing sets of openers.
June 23, 2018 - Aragon Ballroom (Chicago)
June 27, 2018 - Royale (Boston)
I had to bail before Frank Turner in Boston because I had to get prepped for a presentation the next day, but I'm sure it was great.
(Photo credit: Andy Olson)
Being back in Cambridge pretty much feels like being home for me, so I jumped at the chance to participate in Design 4 Drupal this year. While I currently live in the Chicago area, I grew up in Rhode Island and lived in Waltham, MA for about 5 years before heading midwest. Cambridge-wise I performed at ImprovBoston for many years, and also did contract and part-time work for Harvard and MIT. Combine that with a total of four HS2 related talks, keynotes from Jeremy Keith and Dries Buytaert and the excitement levels for this one were super high.
Two keynotes from folks I follow closely were undeniably a big draw here, and they did not disappoint.
The Building Blocks Of The Indie Web
The concepts behind the indie web aren't for everyone, at least not with the tools that exist today. But for me, having your own website and owning your own data are a big motivator behind how I'm approaching this site and there is quite a bit more that I'd like to do in the future. Jeremy's talk was a great introduction to the concepts that power the indie web, how they actually work, and what can be done to make this movement thrive. He's a really engaging speaker as well - I'd recommend both watching the recording and also reading the recap of his Boston trip.
In response to some praise during the Q&A related to improvements in Drupal user experience, Dries was brutally honest about the fact that we still have a long way to go. In his opinion, ease of use is still the number one thing holding Drupal back, going as far as stating explicitly "I'm not satisfied with Drupal's ease of use." It would have been easy for him to accept the compliment on behalf of Drupal, but I think many in the design-focused audience would have found that disappointing. Hearing such an impassioned, clear counterpoint from Dries is likely to stand out in my mind for a long time.
Given all I've said, I doubt this would be surprising, but I think that this talk is a must watch for anyone invested in the future of Drupal.
Fellow HS2'ers at Design for Drupal
I was very happy to have a handful of friends from HS2 Solutions presenting at Design 4 Drupal as well.
Amanda and Seth provided an insightful look at one of the hidden challenges of this profession - cross functional communication. The talk was full of thoughtful reminders (always assume positive intent, listen to understand - don't listen to interrupt) and just as impressively provided a great model for a seamless approach to co-presenting. I'll be looking back at this one when prepping for future joint talks. (Video)
Projects like the Wilson product configurator are among the things that make me proud to work at HS2. Creating a UI to allow customers to design custom versions of uniforms and sporting equipment can seem simple, until you consider the sheer number of possible unique variations that need to be provided. Solving for the hidden complexity in a system like this is something that I find endlessly fascinating, and Andy did an excellent job explaining how it was done. (Video)
I gave two talks for the first time which was pretty stressful, but I'm happy with how both turned out.
Prepping for this talk allowed me to go back and formalize some of the things I had learned about using Storybook as a development environment for React components. The biggest lesson learned for me was how much following a few conventions related to mocking data can streamline the setup and configuration process. I also continue to be impressed with how useful the addon ecosystem is and how well Storybook can inform testing.
I had intended for this to be a beginner talk, but I don't think it really ended up that way. Maybe beginner++? I do think there is useful information for beginners in here, but I acknowledge that this would be a tough place to jump in. In any case, the process of putting this talk together and re-evaluating my workflow was an extremely useful exercise for me. I also heard feedback from more than one backend developer who attended that thought it was a nice overview. Hoping to refine this one and present it again. And maybe this time I'll try to not be quite as punchy and over caffeinated :)
Other Sessions I Enjoyed
Sessions I Hope to Follow Up On
I worked on the UI Patterns Pattern Lab module - merged a pull request, responded to two issues (resolving one,) and got a few cleanup commits. I'm also hoping that the MacBook that had coffee spilled on it at the end of the day is still functioning.
Dinners with friends and family, Drupal Karaoke (and sent Dwane on a walk I'll probably never hear the end of,) saw Restorations and Jeff Rosenstock open for Frank Turner at Royale, and repeatedly had some of my all time favorite iced coffee at Clover. Phew!
Thanks to all at Design 4 Drupal, especially Leslie Glynn who was extremely supportive and organized a great event. Hope to be back with the New England Drupal community soon.