| title | description |
|---|---|
Knowledge Share |
A meetup where we share knowledge formally and informally across the org |
When Artsy was under 50 people, we would hold "Brown Bag" meetings. These were talks on a variety of art+science topics. As we out-grew the format, we started doing engineering "Brown Bag" meetings. Occasionally.
This worked for a while, but was sporadic and mostly the same speakers. Once we moved to a new stand-up format it felt like time to re-vamp our brown bags too.
For a few years we ran a weekly "Lunch & Learn" on Thursdays to educate the team about our stack, business proceses, recent projects, or other interesting technical topics. Alan described it well on Professional Development at Artsy:
Every Thursday, we do a Lunch-and-Learn session. Historically, we mostly showed off tech we use internally. But over about a year, most of our tech stack has been presented this way, so we also bring in engineers we know at other companies
After a while we decided to mix things up by:
- Inviting the occasional external speaker (see some examples below)
- Alternating formal, scheduled Lunch & Learns with informal, open-mic style Show & Tells
As the team has grown and become more international (and no longer lunches around the same time), we've renamed this event to Engineering Knowledge Share. We still aim to alternate between formal presentations, and informal show-and-tells.
In the past we've had external contributors, for example:
- How Buffer does Transparency by Katie Womersley
- How I got started in OSS by Henry Zhu of Babel/Behance
- A D3 Overview by Amit Schechter of TWO-N
- How Zalado Works by Laurita Apple and Alexander Kops
- The ODEN Tech Stack by @ODEN_tech
- Creating a Research Dept in a Startup by Joe Carrafa of Warby Parker
- Data Scince at Tumblr by Nicola Barbieri
- Marketing Automation by Jon Hyman of AppBoy
- How we use Docker by Devon Blandin of Code Climate
- Technical Dept at Meetup by Yvette Pasqua
- OSS in the fast lane by Felix Krause of Google/fastlane
- What is C4Q by Jukay Hsu of C4Q
- Getting started in cryptocurrency trading by Jake Brukhman of Coinfund
- NYTimes Career Ladder by Brian Hamman
- Swift & The Blockchain by Tamar Nachmany
- CI & CD at Spotify by Jason Palmer
- Building great API clients by Haroen Viaene
- Using The Art Genome Project data in computational sociology by Taylor Brown
- Events listings & direct support for art spaces by withfriends.co
- Conflict-free Replicated Data Types by Andrey Sitnik
- George F on Bed Stuy Strong's System Automation
Here are some examples of internal presentations:
- The Artsy WeChat launch
- A retrospective on a recently launched feature written in React Native
- An introduction to the Artsy sales team process
- How we use Hokusai to deploy software
- How to use vim
If you are an Artsy employee you can find an archive of many, many more such topics in our archives.
You may be seeing this as an external developer to Artsy, who has been invited to talk, or as an internal colleage who's been asked to give a presentation.
The format is definitely not set in stone, however these are what has worked for us internally and for past contributors.
Traditional conference/meetup style: You bring slides, we watch. You talk, we listen. You finish, we ask questions.
We don't expect conference/meetup-level presentation or practice. A lack of polish is okay. This is a great opportunity to present new talks ideas.
More informal, you can come with other speakers and talk about the ways in which your company works. Covering your tech stack, the decisions behind them. With the presentation mainly being a series of demos, and showing code architecture.
We ask that we can share a livestream of your talk, because we have a lot of global colleagues. This involves loading a Zoom.us link on your computer and sharing your screen.
We also ask that we get a recording of the talk (kept internal within Artsy), for colleagues who couldn't attend or want to review your awesome talk later. This is done through Zoom.us automatically, no additional setup is required. We'd like to get a copy of your slides, too. Of course, we're happy to send you a copy of the recording.
If you don't want to be recorded, no problem. We understand that you might talk and show things that are not for public consumption. We will not share anything externally without your express permission.