Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/artsy/README

:wave: - The documentation for being an Artsy Engineer
https://github.com/artsy/README

art culture docs documentation markdown

Last synced: 3 months ago
JSON representation

:wave: - The documentation for being an Artsy Engineer

Awesome Lists containing this project

README 

        
# Artsy Engineering [![CircleCI](https://circleci.com/gh/artsy/README.svg?style=svg)](https://circleci.com/gh/artsy/README)



Welcome to Artsy! If you're a new team member, we're excited to have you! Here are your

[onboarding docs](/onboarding#readme).



This repo is a work in progress. In fact, your first pull request could be to fix or add to

[this doc](https://github.com/artsy/README/blob/master/README.md). Reach out to your mentor or anyone else on the

engineering team with questions, or try the [#dev Slack channel](https://artsy.slack.com/messages/dev) ๐Ÿ”’.



Whether you're seasoned or fresh out of school, take a moment to read

[Your First 60 Days at an Engineering Job](https://code.dblock.org/2015/04/23/your-first-60-days-at-an-engineering-job.html).



We split this repo out into different sections, each one has a summary of what's inside to make it easy to browse.



| Section |  |

|--|--|

| [[TODO] Add a summary.json to RFCs](/RFCs) | [TODO] |

| [Careers at Artsy](/careers#readme) | How do we grow people |

| [Conference Notes](/conference-notes#readme) | Artsy Engineers' notes from attending conferences. |

| [Engineering Culture](/culture#readme) | What makes Artsy Engineering tick? |

| [Events at Artsy](/events#readme) | Documentation on regularly occurring events and meetings. |

| [Hiring at Artsy](/hiring#readme) | How do we hire people |

| [Onboarding Notes for New Engineers](/onboarding#readme) | Your first steps to being productive |

| [Playbooks](/playbooks#readme) | Tips, procedures, and best practices |

| [Engineering Practices](/practices#readme) | How do we handle cross-functional concerns. |

| [Engineering Recommendations](/resources#readme) | 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 ๐Ÿ”‘](https://www.notion.so/artsy/Product-470238180cf94c87906ef1d3ee259e05).



In addition to working on a product team, engineers are encouraged to participate in our practices:



- Platform Practice



  - Practice lead: [Matt Jones](https://github.com/mc-jones)

  - [Slack: #practice-platform](https://artsy.slack.com/messages/practice-platform) ๐Ÿ”’

  - [Notion](https://www.notion.so/artsy/Platform-Practice-1b558d0627444c9c9bf7ed7583767ca2) ๐Ÿ”’



- Mobile Practice



  - Practice co-leads: [George Kartalis](https://github.com/gkartalis) and

    [Sultan Al-Maari](https://github.com/MrSltun)

  - [Slack: #practice-mobile](https://artsy.slack.com/messages/practice-mobile) ๐Ÿ”’

  - [Notion](https://www.notion.so/artsy/Mobile-Practice-ecc07763bfd04a848c74107dde3ec6dc) ๐Ÿ”’



- Web Practice



  - Practice lead: [Tamara Kiลก](https://github.com/tam-kis)

  - [Slack: #practice-web](https://artsy.slack.com/messages/practice-web) ๐Ÿ”’

  - [Notion](https://www.notion.so/artsy/Web-Practice-bfe55e2c614a4c0eae493b7830622843) ๐Ÿ”’



- Data Practice

  - Practice lead: [Anil Bawa-Cavia](https://github.com/cavvia)

  - [Slack: #practice-data](https://artsy.slack.com/messages/practice-data) ๐Ÿ”’

  - [Notion](https://www.notion.so/artsy/Data-Practice-e248b46638604067a89ba77ca70b39b1) ๐Ÿ”’



## 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][rfc_playbook] for all the details!



[rfc_playbook]: /playbooks/rfcs.md



## Support



If you are on call or asked to fix an immediate issue reference our

[support wiki](https://github.com/artsy/potential/wiki) ๐Ÿ”’ for up-to-date playbooks on how to solve issues.



Creative Commons License



## About Artsy





  




This project is the work of engineers at [Artsy][footer_website], the world's leading and largest online art

marketplace and platform for discovering art. One of our core [Engineering Principles][footer_principles] is being

[Open Source by Default][footer_open] which means we strive to share as many details of our work as possible.



You can learn more about this work from [our blog][footer_blog] and by following [@ArtsyOpenSource][footer_twitter]

or explore our public data by checking out [our API][footer_api]. If you're interested in a career at Artsy, read

through our [job postings][footer_jobs]!



[footer_website]: https://www.artsy.net/

[footer_principles]: https://github.com/artsy/README/blob/master/culture/engineering-principles.md

[footer_open]: https://github.com/artsy/README/blob/master/culture/engineering-principles.md#open-source-by-default

[footer_blog]: https://artsy.github.io/

[footer_twitter]: https://twitter.com/ArtsyOpenSource

[footer_api]: https://developers.artsy.net/

[footer_jobs]: https://www.artsy.net/jobs