WordPress, better cities, and everything else
Friday night: solo parent at Justin (my cousin) and Justine’s wedding. Charlie was one of three ring bearers, and Ava one of nine flower girls. Ton of fun getting to spend so much time with my kids.
Saturday night: kid-free at Jane and George’s wedding. Leah gave a wonderful maid of honor speech. Much debauchery followed this picture.
Next up: Maggie’s wedding in August!
Universal Basic Income, machine learning, Fusion post-mortem, and opioids.
The reality is that no one is more concerned about the impact of AI on society than the people who are building it. Almost always, the more someone knows, the higher his or her concern level is.
Some might ask, “Isn’t it their fault? Aren’t they the ones building the technology that is going to replace workers?” But technologists, VCs, and entrepreneurs are simply doing all they can to push their companies and products forward. It is not their fault that the gains are being concentrated in the hands of a very few, and it’s nearly impossible for them to know and account for the downstream social and economic impacts. It’s OUR job—that is, it’s the responsibility of our government and leaders to account for the impact of innovation on human well-being.
Unfortunately, we are decades behind. And we need to speed up fast.
One investor said something to me on Tuesday that struck me as profound. “At this point, we don’t even need much more technological innovation. We could be busy for a long time just applying the tech we already have. What we really need is much more social innovation.” He’s on to something. He’s a good man who is supporting my campaign. And there are many others like him.
Andrew Yang – Yang 2020
Our vacation in Sunriver last weekend was far too short. I climbed the cinder cone twice, once with a Burley and once without. Ava took her first bike ride to the marina. And we regained all of our calories from ice cream at Goody’s.
This was originally posted on make.wordpress.org/hosting.
Looking for something to do at Contributor Day? We could use your help!
The Gutenberg Migration Guide is a crowdsourcing project to document WordPress Classic Editor customization points and their Gutenberg equivalents (if such exist). media_buttons is the quintessential example; whereas you might’ve used this action previously in the Classic Editor to register a button, it no longer exists in Gutenberg and the block inserter is its direct equivalent.
We want the migration guide to be as comprehensive as it can be. This is defined as:
You can help make the migration guide more comprehensive. If you don’t have any examples of your own to include, here are a couple of places you can start looking:
Everyone can contribute to the migration guide, regardless of skill set. All you need to do is open a new GitHub issue and report the incompatibility you’ve found. Screenshots and GIFs are tremendously helpful. If you know the underlying problem, then please include that too. If all you know is that a given plugin’s feature doesn’t work in Gutenberg, no worries; simply open an issue and we can help track down the cause. Identifying examples of breakage are what we need help with most.
Feel free to join #hosting-community in the WordPress.org Slack if you have any questions, etc. Thanks for your help!
In particular, Open Source gives engineers the power to collaborate across legal entites (companies) without involving bizdev.
The benefits of this workaround are extraordinary and underappreciated.
Yehuda Katz (via Simon Willison)
Want to have a huge impact on Gutenberg’s rollout to a larger number of users? Here are some high value issues that would benefit from a pull request over the next week:
Read through the contributing guide for details on how to get started. Feel free to ask questions on the specific issue, or join us in the #core-editor channel with any questions you might have.
Drafted last time I flew and to be revised next time.
Not quite, but almost.
On Saturday, I ran the Spray Half to the tune of 1:48:22.
It was a great event and I was really happy with my performance. Notably, I hit faster and faster splits in the last five miles: 8:19 (mile 9), 8:02 (mile 10), 7:44 (mile 11), 7:51 (mile 12), and 7:23 (mile 13).
We left Spray on Sunday but we weren’t done yet.
On Monday, Leah and I subjected Ava and Charlie to a grueling ~14 mile hike around Timothy Lake.
For better or for worse, this is the epitome of our marriage — “should we turn around now?” is left unanswered and we keep going. Fortunately, our kids are more hardcore than we are.
An A+ Memorial Day weekend for the year in review book.
ADU legislation, pro-housing density efforts, software eats retail, and PDX exploring.