| title | description |
|---|---|
Conferences |
Attending or speaking at a conference |
We encourage engineers to attend and speak at conferences. It is a great way to stay up-to-date with the industry, be inspired by challenges others are facing, develop one's career, and connect with the community. Here are some guidelines:
- We aim for each engineer to be able to attend a conference every year, subject to budget. The conference should be related to the individual's role/growth or Artsy's challenges/technologies.
- Please be mindful when expensing your travel. A good rule of thumb is to spend Artsy money like you would your own. Refer to Atlas for more details and rate card.
- It's strongly recommended writing up take-aways and sharing with the team upon return, e.g. a list of take-aways and links to resources (decks, videos, etc.) shared in relevant Slack channels.
- We encourage engineers to speak at conferences, and budget-wise the expense gets higher priority.
- If you need help preparing a conference talk, stop by Ash's weekly Writing Office Hours.
- It's also recommended sharing the talk and lessons with the team.
A growing list of related conferences:
- JSConf: https://jsconf.com/
- RailsConf: https://railsconf.com/
- React conferences: https://reactjs.org/community/conferences.html
- RubyConf: https://rubyconf.org/
- SmashingConf: https://smashingconf.com/
- Strange Loop: https://www.thestrangeloop.com/index.html
- dotJS: https://www.dotjs.io/