I helped setup React training with Michael Jackson, the creator of React Router, at our SF 22 office.
A big thank you to @mjackson for giving his workshop @SlackHQ and passing along his knowledge of the @reactjs ecosystem and architecture! 🙌🏽 🎉
I used React 16.6 today in my @ReactTraining workshop 😅 https://t.co/FkoKkEqu8w
I absolutely love the aesthetic of the @SlackHQ offices on 4th St. Dark concrete and wood next to lots of green plants everywhere 😍
Interesting stat: there are more women in today's workshop than men. First time that has happened in over 3 years of teaching these workshops. https://t.co/wSOsnexQYT
SAN ✈️ SFO // @ReactTraining at @SlackHQ
The point of WOTW is to increase visibility of, and to some extent socialize the possibility of, big wins coming from regular, solid, individual efforts on non-herculean scope. Unlike large, heavy launches, these happen pretty often, and are often the result of a single change, not always by a highly visible or well-known individual.
Essentially, this is a venue to recognize work that is:
- Technically excellent;
- Exemplary of Slack’s values;
- Modest in scope, less than one engineer-week;
- At risk of being under-recognized.
“These criteria are, necessarily, a matter of opinion. Smart, well-intentioned people will disagree about how any collection of work ranks under this rubric. We’re proceeding anyway, in the belief that doing something imperfect-yet-directionally-correct is better than failing to do anything for fear of imperfection.”
Update December 8th, 2018
I still have the trophy since it seems a lot of employees didn’t actually like how WOTW was given out. I may be the last WOTW awardee at Slack. RIP. ☠️