4 ms·
Yeah this article really seems to confuse the monorepo and files. The monorepo was always accessible to all. First day on the job, you can literally see all th
by crazygringo 7y ago
Yeah this article really seems to confuse the monorepo and files.
The monorepo was always accessible to all. First day on the job, you can literally see all the source code. Which is crazy cool. (With a few exceptions I'm sure, but not many.) I'm assuming that's not changing?
But any time someone creates a Google Doc it defaults to private. People will then share it with other editors and then their team as necessary.
It happens all the time that you follow a link to a deck to try to understand what a team is working on, and you get a "no permission" and have to e-mail them to explain why you want to see it... and you usually get permission within a few hours but sometimes you needed to look something up quick before a meeting and missed the chance.
Most of the time it's not out of any great secrecy, just that teams don't want other teams to misunderstand info out of context, like whether a team is actually pivoting or just exploring it or just brainstorming internally.
- vl 7y agoWhile monorepo is still a thing, they created a feature called “silos” to allow secret projects, to prevent fiascos like Dragonfly (censored search in China) and Maven (DOD drone image recognition) which both were discovered from monorepo. Ironically, Allo cancelation was discovered by Allo team from a comment in a check in which was made by mistake days/weeks before the announcement.
- badfrog 7y agoThe feature is actually called silos? I thought the hip thing to do was tear down all the silos in a company?
- username90 7y agoOther companies tries to be like Google, while Google tries to be like other companies.
- OneMoreGoogler 7y agoDuring my time there, the internal Android repo required VP approval to access. Though I understand this was relaxed later.