Re:Software Engineering Insights from 10 Years at Google
by dlp211 on Thursday May 19, 2022 @01:39PM
(#31437724)
It's not your code, it's Google's and I don't see how this is an anti-pattern. It is actually one of the best thought out solutions to balancing source code supply chain security and productivity. The fact that the industry has moved towards git and allows employees to clone proprietary codebases onto developer machines anywhere in the world is pure insanity.
[ Parent
| on HN ]
Re:Software Engineering Insights from 10 Years at Google
by saagarjha on Thursday May 19, 2022 @04:47PM
(#31439957)
It’s also Google’s laptop but maybe they should have me remote into it instead of letting me touch it. Who knows, I might steal it…
Re:Software Engineering Insights from 10 Years at Google
by enneff on Thursday May 19, 2022 @05:30PM
(#31440420)
To Google, a laptop is worthless compared to their intellectual property.
Re:Software Engineering Insights from 10 Years at Google
by saagarjha on Friday May 20, 2022 @04:49AM
(#31444874)
It's more the principle of the thing–if I wanted to steal code from Google their "no source code on laptops" policy wouldn't stop me at all. And given that I don't actually want to steal code the policy sucks, so the real question is what the benefit is here by treating me like a criminal.
Re:Software Engineering Insights from 10 Years at Google
by enneff on Friday May 20, 2022 @06:28PM
(#31453319)
It’s not that a google employee would steal the code, it’s that if a laptop is compromised the access to the source code can be immediately revoked. So if someone steals an employee’s laptop and coerces their password from them, the source code can not be accessed for long, and exactly what source code was seen is known.