Hacker News new | past | comments | ask | show | jobs | submit login

I was surprised by the volume of the handbook material that applies to the role of CEO shadow. To me it implied a high level of formality and expectation of rigid adherence. Then I found this:

> CEO shadows label the handbook MRs they create with the ceo-shadow label. It's a point of competition between CEO shadows to try to best the previous shadows' number of merge requests.

I am no longer surprised by the length of this section of the handbook.




As a shadow, you would contribute anywhere, not just on the CEO Shadow process.

I see them often on slack updating various random pages:

https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: