Now and then, life feels like your adrift in an ocean of work on a sinking ship. There's water so choppy that it feels like you can't see land off in the distance let alone dream of swimming there. That was this week of converting elements by hand. But sometimes, when you think that the shore line is too far to swim, you prove yourself wrong.
I haven't felt this confident in my abilities, process, team, and vision of where we're heading. I'm starting to be able to embrace it as opposed to grasping at straws. I'm finding my voice in this space and making my message more coherent.
Usually I write of family victories or to recount something I see in the world. This is different though. I feel confident I'm going the right direction. I may exude confidence (loudness will come across that way at time) but really, I'm just trying to find my way in the dark water like we all are.
Drupalcon was a huge success. I've had interest in my work previously and it's always a cool feeling but it leaves you empty when you walk away without changing anyone's process. That you're trying to impart knowledge but also get people to join you on the life raft you stumbled on.
This year we got people adopting our work (both HAX and WCFactory) on site, across multiple days. We worked out documentation issues and clearly struck a cord as far as coherence of message both me personally and Potter (@hey__mp ).
And this isn't even to speak to the talk we did with Kendall and Casandra from Red Hat. That talk was awesome and we got a lot of really good feedback and I think finally moved the needle on adoption of web components. That and I love their passion for our craft and Potter nailed his part too so I was so happy for him.
Why do I care about adoption? Because the only way we'll transform the industry is if we're all pushing together. I have no idea what element or idea or library that someone in that road will produce that I can leverage next month, next year or further on.
I found a bug in the polymer CLI that directly related to our build routine. Unfortunately I'd never looked at typescript before, and the idea of contributing to a google property is a bit daunting. Web components has been a bear just for me to figure out how to leverage their work, let alone rewrite part of their core compiler that allows us to work.
But. 7 hours of frustration paid off and I was able to fix the issue (it was related to Firefox build routines and dynamic imports / bare path resolution . boring stuff). My pull request was accepted rather quickly after explaining the problem to their engineers.
This has left me feeling pretty good about what we're doing. You get those gut check situations occasionally and continue to soldier through hoping to find your way out of the ocean you're lost in. Imposter syndrome strikes us all, so it was a big break through for me to contribute to something we depend on and do so in a manner that tells me I know what I'm doing in this space.
It took about three days, but I completely rewrote and optimized all of our elements in our portfolio. In working towards this, I came to realize that we've made 433 elements to date. I tend to say we have 168 or so elements but that's repos.
That's an insanely daunting figure that's a testament to our team, as well as my process / workflow improvements of the last 6 months that would allow me to wrangle and enhance the quality of 433 items in three days.
In editing files by hand / bulk replace / preg, in the end I only came up with about 10 issues. This is after 7+ hour sprints of doing 0 testing. The web component development methodology in general as well as how we are doing it, is insane. The performance gains are nice but the process gains in this work are far greater.
I said, I'm finding my voice again in this space (I've had it before but have gone a bit dark in order to just swim to shore). We've been building an arsenal of elements, process, and people that believe in what we're doing. I wrote my thesis in changing organizations through open contribution, and this.. "research project"... is... much wider in scope then that small scale exercise of the past.
I've written before about the next research project. And now, we begin the climb on land toward that vision. The place where pedagogy is unleashed. Fun facts you can piece together, even if you is just future me reading this to recall who I used to be.. and who I hopefully still am.
I posted this online.. I held it back for a long time. It was in the lead up to my first son being born (about a month before hand) and represents the day I woke up... finally... woke up to the fact that the industry I was in had been coopted. It's my formula for disruption and bringing about lasting social change, using technology as the vehicle.
I dated it because I knew one day, I'd look back on it. It's been on my desk every day since. I've never felt so alive.