Awesome
Artsy Engineering 
Welcome to Artsy! If you're a new team member, we're excited to have you! Here are your onboarding docs.
This repo is a work in progress. In fact, your first pull request could be to fix or add to this doc. Reach out to your mentor or anyone else on the engineering team with questions, or try the #dev Slack channel ๐.
Whether you're seasoned or fresh out of school, take a moment to read Your First 60 Days at an Engineering Job.
We split this repo out into different sections, each one has a summary of what's inside to make it easy to browse.
<!-- prettier-ignore-start --> <!-- start_toc -->| Section | |
|---|---|
| [TODO] Add a summary.json to RFCs | [TODO] |
| Careers at Artsy | How do we grow people |
| Conference Notes | Artsy Engineers' notes from attending conferences. |
| Engineering Culture | What makes Artsy Engineering tick? |
| Events at Artsy | Documentation on regularly occurring events and meetings. |
| Hiring at Artsy | How do we hire people |
| Onboarding Notes for New Engineers | Your first steps to being productive |
| Playbooks | Tips, procedures, and best practices |
| Engineering Practices | How do we handle cross-functional concerns. |
| Engineering Recommendations | Collections of further reading. |
Artsy Engineering Operations
Product & Engineering Teams
Artsy product engineering is organized in product teams. Each team has a purpose, eg. "Help galleries get the most out of Artsy and run their business better", and Key Performance Indicators, or KPIs, eg. "The number of artworks uploaded by partners." Each team has members with different responsibilities, including a Product Manager, a Designer, a Technical Lead and Engineers, depending on size. Sometimes the same person wears multiple hats.
You can see this organization in the Product section of Notion ๐.
In addition to working on a product team, engineers are encouraged to participate in our practices:
-
Platform Practice
- Practice lead: Matt Jones
- Slack: #practice-platform ๐
- Notion ๐
-
Mobile Practice
- Practice co-leads: George Kartalis and Sultan Al-Maari
- Slack: #practice-mobile ๐
- Notion ๐
-
Web Practice
- Practice lead: Tamara Kiลก
- Slack: #practice-web ๐
- Notion ๐
-
Data Practice
- Practice lead: Anil Bawa-Cavia
- Slack: #practice-data ๐
- Notion ๐
Request For Comments
A Request For Comments (or RFC) is how we change things, by opening a discussion that everyone can participate in and deciding if we want to move forward with the suggested change or not.
RFCs should be created by authoring a markdown file in the /RFCs folder and then opening a pull request. Read
the full playbook for all the details!
Support
If you are on call or asked to fix an immediate issue reference our support wiki ๐ for up-to-date playbooks on how to solve issues.
<a rel="license" href="https://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a>
About Artsy
<a href="https://www.artsy.net/"> <img align="left" src="https://avatars2.githubusercontent.com/u/546231?s=200&v=4"/> </a>This project is the work of engineers at Artsy, the world's leading and largest online art marketplace and platform for discovering art. One of our core Engineering Principles is being Open Source by Default which means we strive to share as many details of our work as possible.
You can learn more about this work from our blog and by following @ArtsyOpenSource or explore our public data by checking out our API. If you're interested in a career at Artsy, read through our job postings!