How to get people who installed a leaked build to stop using that build?

Re:How to get people who installed a leaked build to stop us... by yongjik on Tuesday September 06, 2016 @05:17PM (#12439351)

Heh, sounds much better than my previous employer's way of occasionally sending company-wide emails along the line of "The employee who was responsible for the XXX leak was found and terminated. We remind you that leaks damage our culture and make it difficult to share ideas inside the company."

For some reason such emails made me feel like I was inside a tech cult. Guess my culture fit wasn't good enough...

Well, to be fair, I guess MS also utilizes these emails in addition to reverse psychology...

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by hota_mazi on Tuesday September 06, 2016 @09:38PM (#12440473)

Sounds like standard business practice to me.

If you can't understand basic instructions such as not leaking internal, confidential info, you deserve to be fired.

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by derefr on Wednesday September 07, 2016 @01:55AM (#12441207)

Oh, sure; I think the parent commenter's point was in thinking that emailing everyone about the termination of the leaker served as any sort of deterrence mechanism for people's use of the leaked build.

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by yongjik on Wednesday September 07, 2016 @05:12PM (#12447746)

Well, emails are not exactly deterrence against people using the leaked "build": being an internet service company, that part is usually achieved by shutting down the server.

Emails are supposed to be deterrence against further leaks by reinforcing the "company culture". (Whether they work, I have no idea.)

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by verst on Tuesday September 06, 2016 @06:43PM (#12439799)

Google right? I used to work there too. I thought Google was especially open internally, which really allowed me to thrive.

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by yongjik on Tuesday September 06, 2016 @06:50PM (#12439828)

Yeah, I really liked Google's internal openness too, but the way they protected it felt a bit overzealous. As if I'm live-action roleplaying a spy organization or something.

Almost nobody seemed to have any problem with it, so I guess it's just me. ¯\_(ツ)_/¯

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by khuey on Tuesday September 06, 2016 @07:11PM (#12439918)

The alternative, where people don't share information internally because they're afraid of leaks, is pretty shitty.

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by Iv on Wednesday September 07, 2016 @01:03AM (#12441057)

Another alternative is to work in an organization (most likely not a private company) that does not care about leaks. Non profits, administrations, many people work there and love it.

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by Chronic9q on Tuesday September 06, 2016 @09:50PM (#12440521)

Cupertino

[ Parent | on HN ]

Re:How to get people who installed a leaked build to stop us... by j28xfc5qsc on Tuesday September 06, 2016 @06:06PM (#12439619)

I never received an email like that when I worked at Microsoft. Granted, maybe they would send emails like that within a specific department, and my department was probably less prone to leaks.

[ Parent | on HN ]