This is the most comprehensive and high quality writing I've seen that includes almost all engineering processes from interviewing to communication. Would love seeing other such engineering handbooks you've seen.<p>Also adding two other good ones: Sourcegraph - <a href="https://handbook.sourcegraph.com/" rel="nofollow">https://handbook.sourcegraph.com/</a> & Gitlab - <a href="https://about.gitlab.com/handbook/#engineering" rel="nofollow">https://about.gitlab.com/handbook/#engineering</a>
Man there are some real doozies in this repo's issues.<p>- 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 <a href="https://github.com/artsy/README/issues/459">https://github.com/artsy/README/issues/459</a><p>- starting a 3 full-day hackathon every quarter. <a href="https://github.com/artsy/README/issues/441">https://github.com/artsy/README/issues/441</a><p>- 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 <a href="https://github.com/artsy/README/issues/427">https://github.com/artsy/README/issues/427</a>
Oh man I wish I could get my (non-tech) org to do this. Instead we’ve got a twisted hellscape of docx and pptx inside MS Teams and 3 other enterprise storage apps. If anything is documented at all, that is.
:disclaimer I work at Artsy:<p>cool to see this on the front page!<p>If this interests you be sure to check out the artsy org on github:
<a href="https://github.com/artsy">https://github.com/artsy</a><p>Artsy is open source by default so there are a fair amount of interesting repos and projects, including our website and mobile apps (react and react native).<p>I am biased of course but I think the engineering culture at Artsy is pretty unique and special.<p>The blog and podcast may also be of interest:<p><a href="https://artsy.github.io/open-source/" rel="nofollow">https://artsy.github.io/open-source/</a><p><a href="https://podcasts.apple.com/us/podcast/artsy-engineering-radio/id1545870104" rel="nofollow">https://podcasts.apple.com/us/podcast/artsy-engineering-radi...</a>
I'd love to know the background of how something this comprehensive is created <i>and</i> maintained.<p>Was this the work of one person? A team? Was it created in one go or did it start small and evolve?<p>Very impressive!
How does this work? Do you just read it on github? Or you suppose to make copy of it on your computer. Looks like these are just linked md files. Is it similar to wiki? I'm confused.
I guess I'm in the minority here as a SWE but I find all this ongoing documentation about engineering expectations, culture, processes, etc. exhausting. I would not be excited to be onboarded somewhere that spends so much time and energy thinking and talking about a _proposal_ to document best practices and industry standards.<p>Perhaps I'm missing context but it all sounds so vague and low-impact that I just can't imagine spending so much time and energy engaging in these thought experiments on documentation improvements.<p>I understand the repo is for developer documentation but it took a long time of poking around to figure out what the product even was. Eventually I stumbled upon this blog post which seemed to anticipate my confusion and flat-out said: "For those unfamiliar, Artsy is a fine art marketplace." All the meta analysis is striking me as very distracted. Maybe its just the nature of the content but it seems like an inordinate amount of engineering resources are spent on process management, planning, and iterating on documentation thereof.