342 karma · joined December 29, 2013
At a certain point you can't. I was recently asked to implement a feature for a usecase for another engineer. It required a design doc and review by a few representatives from related teams. He and I wrote the doc, and the initial review was that any solution that would fix his usecase would break the testing infrastructure for practically every other developer in the building. He could write a few fewer loc when testing, at the cost of tests failing due to unrelated changes.
Neither he nor I had the awareness of the impact, and realistically couldn't have, it was neither of our responsibilities. And because I spent an hour filling out a template document, I didn't need to waste my time doing that.
Also, to be clear, Linux is relatively small compared to Google or Microsoft, or indeed many corporations codebases. Someone could conceivably read the entire Linux kernel codebase. That's not true for BigCorp.
Its not a permission to do work, its permission to merge the results of the work to master. Those are different.
>Google's design document culture is bad.
Then why do we have JEPs, PEPs, and rfcs in perhaps every other major project out there?
It doesn't do ambient recording. Its basically shazaam.
>There should be one-- and preferably only one --obvious way to do it.
The zen of python isn't saying "only have one way to do anything" it says "have at least one obvious way, and preferably only one obvious way to do this".
There can be lots of ways to iterate over a list:
[x for x in l]
for x in l:
x
while (x for x in [1,2,3]).next():
...
Only one is obvious for a given situation.- no mention of non-sigmoid activation functions - calling overfitting 'grandmothering' and - diving comparatively deep into gradient descent (which while absolutely the most common, is not the only way to train a neural network), while being an inch deep on practically every other aspect.
Its a bit of a confused intro that simultaneously tries to teach you the basics while throwing jargon at you ('delta-rule', 'beta-coefficient', 'hyperparaboloid', etc.).
There will absolutely be people who are willing to sacrifice some ease-of-use in the name of additional privacy, but it seems that those people are in the minority, and that means that Google (or whomever) needs to provide 99/99 when everyone else is only 90/90, if they want to continue being market leaders.
Competition is good. You can make a standards based browser and then add additional features that others can't or won't provide. Building it in house gives them more control. Do you think Mozilla would have developed V8 if google just threw money at them?
What's the difference? I consider inclusivity a minimum standard of mutual respect, do you not?
>Shouldn't it be what's best for the project? I understand that's nitpicking but the focus is wrong.
The CC is (to my knowledge) an opt-in thing, meaning that by opting in, you are consenting to put the greater community before your project (in some contexts). Is that a problem?
It would get upvoted, perhaps to the front page, and then news outlets would likely pick up the story.
Is that not exactly what happened here? OkCupid refused to do work with Mozilla based on Mozilla's (CEO's) beliefs, and this led to action on the part of Mozilla.
I'm not sure how you can call this a liberal action when it is essentially what the right espouses as 'the way things should be'.
# optionally: Number = Union[int, float, complex]
def sum_and_stringify(nums: Iterable[Number]) -> str:
return str(sum(nums))
also works. Except no one knows what the Number abstract base class is (or even the Iterable abstract base class for that matter)Or perhaps, he realizes that to require these typechecks at runtime would either
- require a massive rewrite of the CPython interpreter
- cause a performance penalty in code that is statically typed (there are pure python libraries that allow this, and yes your code runs slower)
Further, it offers a relatively narrow amount of help to pypy, which has already come out and said that they have no interest in using annotations for efficiency gains, because they're a jit and they don't need them.
I think is incredibly important. If your information is put at risk due to bad practices by Google/Yahoo/Apple/Facebook/whomever that's a problem to be taken up with the company. If you use insecure passwords and someone is able to access your information that way, then the problem is with your passwords, not with the platform.
>Think harder. Who has the root access to the servers holding the data?
As far as I'm aware, no one. Like I said, from my experience, accessing personal data and user information as an engineer required a lot of red tape and approval from 'the powers that be', and violating those rules would get you fired faster than anything else.
>Could the existing infrastructure and data segregation ever change? How many external checks and balances are in play that can't be manipulated by internal forces (i.e. is there anything stopping Google, or holding Google accountable if their data protection policies change)?
Here I agree with you, probably not (or very little). They obviously have public privacy policies, but you have no proof that they abide by those, and I don't know (and doubt that) they get audited or whatnot to make sure that those policies are followed. Which is why being an employee made me more comfortable. If nothing else, it meant I'd know ;)