Profile cover photo
Profile photo
Matthew Wilson
542 followers
542 followers
About
Matthew's posts

Trying to shop for a metric lathe in this country is an exercise in frustration.

Post has attachment
Photo

Post has shared content
This can't come too soon. Electric will be better in every way.

Post has attachment
I just pre-ordered the Shaper Origin. Use my link below to order and we both get $100 off.

Post has attachment
I've played the teaser, and it's every bit as good as the original game. If you ever enjoyed Descent, you'll want to back this.

Post has shared content
This.
After being asked personally a few times and reading claims by others a few more, I thought I'd set the record straight....

Working at Google does not give you access to the data of users!

It's an easy assumption to make.  After all, most companies don't put internal access controls on data making it easy for every employee to access everything inside the firewall.  Google does not work that way.

Though there are many groups at Google, we'll simplify it into Software Engineering ("SWE") and Site Reliability Engineering ("SRE").  I was the latter for 5 years and I've been the former for 3.

SWE, in general, has access to nothing.  They run their code on their own workstations and sometimes test clusters with test data.  A few get access to anonymized user data for their service -- more on that later.

SRE is the group that owns the keys to the kingdom.  They're the group (actually many small groups) responsible for running Google services "in production".  They almost always have access to anonymized user data for their service and the ability to access "raw" logs if necessary, again for only their service.  The kicker is that, since around 2011, this latter access comes through a specific interface where you must explain with each request why you're doing this.  All those actions are logged and those logs are audited.  Misuse of the access will get you fired.

What is "misuse"?  I can't even look up my own queries.  I could be on-call for my service, have you on the phone fixing a problem with you saying, "go ahead" , and I still couldn't do it.  In five years, I only used raw logs twice, both on myself during training just so we'd know how.

So, for any given service, there may be somewhere between 10 and 100 people worldwide who could potentially access Personally Identifiable Information ("PII") of a user, but doing so without a good reason would be the end of them at the company.  And should that abusive employee somehow cause "material damage" to the company...  I don't even want to speculate.

On top of that, any attempt to track a single user, whether the user can be identified personally or not, will also get you fired.  Every user with any form of logs access has signed a paper (real paper, even) stating that they understand all this and the consequences.

This is serious stuff.  My own team would turn me in without a second thought if I did any of this.  And I'd do the same to them.

What are "anonymized" logs?  They're the requests that have had all PII stripped.  No IP address.  No account identifier.  No geo-locating finer than the city, etc.

Disclaimer:  I work for Google (obviously).  These thoughts are mine and mine alone.  Mine, I tell you!  Mine!!!
Photo

Post has attachment

Post has shared content

Post has shared content
Isn't he MAGNIFICENT?! (That is, in fact, his tongue sticking out.)
Photo

Post has attachment
I've been playing with OnShape lately, and I have to say that I'm impressed. I designed a case for the Raspberry Pi that I can mount to my 3D printer. Definitely going to do more projects with it.

My case if you are interested: https://cad.onshape.com/documents/91b5d9667bf049bf8a342992/w/61fd522c83ad48be9a3bc04f/e/ce2b7bd4885d446386386b27
Wait while more posts are being loaded