2 ms·
It's somewhat curious to me that neither she not Google are spelling out exactly what was changed in the code. The "policy notifier" existed already as an inte
by tyingq 7y ago
It's somewhat curious to me that neither she not Google are spelling out exactly what was changed in the code.
The "policy notifier" existed already as an internal use Chrome plugin. It apparently had a list of sites that would merit it popping a policy reminder.
So, she clearly mapped a policy reminder for that website. But, elsewhere in this thread (https://news.ycombinator.com/item?id=21961447 https://news.ycombinator.com/item?id=21961447) it's suggested that she also made a special rule to show it every time for that site, where other sites would only show it on first visit.
- CydeWeys 7y agoThat's just a config option on the notification whether it shows every time or once per month or whatever.
- tyingq 7y agoSo there wasn't a "code change" per se, then? She just pushed a config file or similar?
- CydeWeys 7y agoI think so. Note that there's likely not a huge distinction between the two, because Google uses some pretty complicated configuration languages that are often Turing complete (e.g. Blaze essentially allows arbitrary Python). It's all checked into the one true monorepo as well.
- sp332 7y agoGoogle claims that she was fired for violating security policies, not for being annoying. So neither side is claiming that was the reason.
- tyingq 7y agoThey claimed change management policy as a reason, so I was curious if any code actually changed.