HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
artsy
README
TypeScript2021–2023
artsy / README

README

:wave: - The documentation for being an Artsy Engineer

ProductivityLearning & Reference
Explore on GitHubRead Hacker News discussions
6Distinct people
7Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:wave: - The documentation for being an Artsy Engineer

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month7 dated mentions

Observed mentions: 2021-12-08 10:30:41 UTC to 2023-01-07 18:11:41 UTC.

02462021-12-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 20212022-01-01 00:00:00 UTC to 2022-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-02-01 00:00:00 UTC to 2022-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-03-01 00:00:00 UTC to 2022-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-01 00:00:00 UTC to 2022-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-01 00:00:00 UTC to 2022-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 20222022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 commentsJan 2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 20212021-12-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
Jan 20222022-01-01 00:00:00 UTC2022-02-01 00:00:00 UTC000
Feb 20222022-02-01 00:00:00 UTC2022-03-01 00:00:00 UTC000
Mar 20222022-03-01 00:00:00 UTC2022-04-01 00:00:00 UTC000
Apr 20222022-04-01 00:00:00 UTC2022-05-01 00:00:00 UTC000
May 20222022-05-01 00:00:00 UTC2022-06-01 00:00:00 UTC000
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC000
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC000
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC000
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC615

What Hacker News says

7 sources
quadrifoliate·Jan 7, 2023
> an extensive month long discussion that leaks implementation details of a private repo and ultimately leads to adding 1 readme comment that merely _suggests_ something https://github.com/artsy/README/issues/459 What implementation details? Most of the stuff linked in there seems to be in public repos that have interfaces to this private repo, so I can't see that the discussion itself is leaking more implementation details than reading the code in the public repos that interacts with the private repo. Secondly, the conversation in there is long, but hardly unusually so. At most each comment apart from the initial one took up ~10 minutes of time for each of the authors. Are we at the point where 8 well-formatted comments on a GitHub issue are going to make us go "ooh, long discussion, must be something wrong with it"? I would rather have
Read the rest
long, well-formatted comments than "lol ok" style garbage. Finally, I wish more people would conclude a month-long discussion with a simple action rather than carrying out an unnecessary and complicated one because "Well, something has to be done, and it has to be large because we have discussed a lot". This can be counterproductive with dealing with complex libraries that you don't understand yet. > adding politically motivated language and starting a policy to open issues in dependencies that do not conform. Look at the time and energy putting into changing master -> main and white/blacklist -> allow/deny. Also https://github.com/artsy/README/issues/427 I would prefer to stop talking about this stuff, but it's hard when I often see lazy drive-by denouncements like "Politically motivated" in comments near the top. Language seems to be important to the people working on the project. It would probably not be the first thing I pick up, but I don't understand why it's considered a "doozy". Good documentation does think about the people using it as well as clarity; and "denylist" is more informational than "blacklist" in addition to being more sensitive. Real language idioms change just like programming language idioms, and railing against them is about as useful as claiming you hate Python 3 because they took out the print statement.
In Artsy Engineering Handbook
poyes99680·Jan 7, 2023
Man there are some real doozies in this repo's issues. - an extensive month long discussion that leaks implementation details of a private repo and ultimately leads to adding 1 readme comment that merely _suggests_ something https://github.com/artsy/README/issues/459 - starting a 3 full-day hackathon every quarter. https://github.com/artsy/README/issues/441 - adding politically motivated language and starting a policy to open issues in dependencies that do not conform. Look at the time and energy putting into changing master -> main and white/blacklist -> allow/deny. Also https://github.com/artsy/README/issues/427
In Artsy Engineering Handbook
dblock·Jan 7, 2023
(I was CTO of Artsy then.) tl;dr The README became possible because Artsy is open-source by default, and someone just decided one day to create a repo and some content, and didn't need permission to do so. It's also the repo that most new hires read before they even apply to the job, and they don't need permission to make changes either. GitHub workflow is how everything gets done. More practically, check out https://github.com/artsy/meta/pull/1, which is one of the repos that merged into the handbook via https://github.com/artsy/README/pull/1. Also note that Artsy was founded in 2010. This handbook in its current iteration is 7-8 years in, but its content goes back to ~2011 in some kind of evolution. You'll want to check out https://artsy.github.io/blog/archives/ as well.
In Artsy Engineering Handbook
emilymh·Dec 8, 2021
Artsy | Berlin (Hybrid), NYC (Hybrid) or Remote USA | Full-time Engineering Manager USA - preference for platform, data or infrastructure experience Engineering Manager Berlin & USA - preference for front-end or mobile experience Artsy’s mission is to expand the art market to support more artists and art in the world. Artsy has created the world’s largest two-sided art marketplace, with more than 1,000,000 works by 100,000 artists from 4,000 of the world’s leading galleries, auction houses, art fairs, and institutions across 190 countries. Apply via https://www.artsy.net/jobs More info https://github.com/artsy/README
In Ask HN: Who is hiring? (December 2021)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.