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

Used to feel this way on other teams. Almost as if you were expected to write them for the sake of writing them (cargo cult engineering).

Now on a team of many OG Googlers (15+ years tenure) and Design Docs only exist when they’re needed (something that touches multiple systems, something that’s obviously complicated with many trade offs, etc) Otherwise it’s just “write the CLS.”




> Now on a team of many OG Googlers (15+ years tenure) and Design Docs only exist when they’re needed

This almost certainly has nothing to do with the team or tenure, but everything to do with what levels they are(n't) trying to get promoted to. Have you controlled for that and still seen a distinction?


One presumes in those simple CL cases, there is already a doc for the system being edited, and the new code followes the design.


  > Otherwise it’s just “write the CLS.
(apologies for the noob question) but what is cls in this instance?


Change Lists (Pull Requests, Change Sets)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: