It's been more than an year since I started attending TC39 meetings, and this most recent meeting felt much like the first, as I faced a new personal challenge: I went there as the acting chair.
TC39 is a group of almost 50 highly skilled professionals, each with very strong positions on the existing form and the future form of the language. While the skills and opinions are visible strengths, time management remains a challenge. While everyone has an opinion, everyone else has something to add or a concern to express. The discussion is dense. Sometimes it's hard to follow all of the work being done on each proposal presented to the committee, not only in the meetings, but on an everyday basis, so it's common to see some delegates who are specialized in specific topics. As the acting chair at this most recent meeting, I faced new responsibilities and lessons to be learned.
The test showed up on my desk just like any other. There I was, working with
Google's Web Platform Predictability
team to find so-called
"flaky" tests in the venerable Web Platform Tests
project. I'd run a hundred or so at
a time, over and over again, looking for any that reported inconsistent
results. It was a bit like panning for gold, only my prize was more valuable
than any precious metal: interoperability.
Maybe you're not a "people person." It's not that you dislike other humans,
but you recognize certain realities of your work. Your day job is maintaining a
web application, after all, not carousing with your users. You know that
accessibility is an important topic, but you haven't been able to find the time
to learn more about it. Keeping the application running smoothly while your
team adds features, fixes bugs, and re-designs is quite enough to worry about,
thank you very much. That introduction to accessibility
has been open in a tab for the better part of a week, but the UI tests are
failing again. Is it any wonder that "a11y" concerns take a back seat?
Do you know a bit of R and have some data you need to visualize quickly? In this blog post we take a look at Rstudio's Shiny package and the first steps toward creating a working interactive to explore your data with it.
The Bocoup Data Visualization team will be at the Eyeo Festival in beautiful Minneapolis this week. We’re looking forward to learning, getting inspired, and meeting friends and colleagues from all over the world. If you’re attending too, be sure to say hello!
Meanwhile, we wanted to share some of our latest work:
On February 15, 2017 we had a screencast to talk about how to improve webpack build times by utilizing the new webpack HardSource plugin created by our colleague Z Goddard. This post contains the video of that event along with a transcript and visual aids.
I was helping a coworker recently who was looking at including raw markdown into a small project with webpack. Their application would then use a library to render that markdown as a slideshow.