The New York Times claims to have uncovered the identity of the Google software engineer who wrote the code used by Street View cars when they controversially scooped up private Wi-Fi data including emails, text messages, browsing histories and passwords.
According to the newspaper, Marius Milner of Palo Alto, California is “Engineer Doe” – the coder named only pseudonymously in an official FCC report that revealed Google staff knew for years about the Street View data breach.
As his LinkedIn profile reveals, Milner is also the author of “NetStumbler”, a well-regarded wardriving program that helps discover wireless networks.
The code written by Google, and deployed in the Street View vehicles, was called “gstumbler” (later renamed “gslite”).
In my opinion, it would be wrong to scapegoat Milner for the privacy debacle caused by the Street View cars slurping of too much information from Wi-Fi hotspots.
For some time, Google maintained that the problem was entirely down to a “rogue engineer”, but the recently released report reveals that Milner/”Engineer Doe” “Engineer Doe” told colleagues in 2007 and 2008 about the sensitive nature of the data being collected by the Street View mapping cars, and suggested that the project should be reviewed for privacy issues.
That privacy review never took place.
Clearly there are lessons to be learnt here by project managers as well as software engineers.
Management should carefully peruse project plans, proposals and specifications to fully understand the scope of the code that is being written, and what is intended to be done with any data that comes out of the process.
And engineers need to learn that just because data can be collected, doesn’t mean that it should.