225 karma · joined March 8, 2011
Have you taken a look at https://cloud.google.com/ml/? I assumed you would have but didn't see anyone mention it in the comments.
Do you see your product as complementary to a service like that? e.g. could you use the Google service as the execution engine for yours? or do you see that as competition?
My parents-in-law still can't figure out how to get on their G+ account to use Hangouts, but for them Skype is second-nature. Open it, click on the contact, phone rings, presto, we're chatting.
(Now I'll have to check my car tomorrow morning to be sure I haven't just been ignoring it all this time.)
"Indeed, the U.S. government does not have direct access or a “back door” to the information stored in our data centers."
Sure, that's fine. But the fact that the initial PPT gives a specific date on which Google cooperation began already suggests that Google may be handing over data, not that the gov't is sucking it all down automatically.
Also, they say "data centers" in particular. Data travels over lots of other pipes.
"We had not heard of a program called PRISM until yesterday."
Not surprising the NSA wouldn't tell them the secret code name of the project in their discussions.
"we provide user data to governments only in accordance with the law. Our legal team reviews each and every request, and frequently pushes back when requests are overly broad or don’t follow the correct process."
This is an enormous loophole. "in accordance to the law" could mean anything, and with automated review systems the volume of data passing through could be massive.
"Press reports that suggest that Google is providing open-ended access to our users’ data are false, period."
Not providing "open-ended acces" does not mean not providing any access.
"We were very surprised to learn that such broad orders exist."
But not surprised to learn that other not-so-broad orders exist. How broad is too broad?
"Any suggestion that Google is disclosing information about our users’ Internet activity on such a scale is completely false."
Not "on such a scale", but on a slightly smaller scale, sure.
"there needs to be a more transparent approach"
In other words, we wish we could tell you about everything we're doing with the NSA, but we aren't allowed to.
Really this doesn't read like any sort of denial at all.
Speaking from experience I know it is hard not to define yourself by the people around you, but it's deadly.
What helped (and continues to help) me is this question: Do you want to be that person?
As in, "do you want to be the person who sits in the office chatting and surfing facebook all day? or do you want to be the person who other people look to to get things done?"
The point is, look at yourself from outside. Decide how you want to act (for me, thinking about how I want to be perceived helps here). Then make it happen. Stop waiting for the people around you to make you into the person you want to be.
Which it never does. At least, I have yet to experience or hear of a (software) engineering culture in which that's true.
Right; there's some cargo culting in legal writing. Until a particular form of words has been tested in court, no-one really knows whether it will stand up.
If there's an untested standard form, most people won't want to experiment with a variation because if their variation happens to be the one that fails, there's a possibility of a negligence suit for not using the standard form.
If there's a tested standard form, even fewer people will want to experiment, for the same reason.
There really is nothing comparable to the Office suite when it comes to features and interoperability. Yes, it has its quirks, but you just can't make the other products do what the Office products can do.
Um, YEAH. And just started seeing a counsellor about it. I don't think there's anything wrong with me (or you) but I want someone to talk to about it.
I disagree with "Efforts taken at this point to turn things around would be futile." I'm living proof. I bounced from job to job for 10 years, then lost a job in finance in 2007 at 33, went back to school, got out in 2010 at 35 and now have a job as a software engineer. Yeah, I'm competing with young turks 10-15 years younger than me. Yeah, sometimes they're better... but a lot of the time they aren't. It turns out I actually did learn a few things bouncing from one job to another, and people do see that.
Is it the best job I could have at this point in my life, am I as rich as I could be, as if I had done everything "right"? NO. I threw away a bunch of fucking brilliant opportunities earlier in my career. But is it a good job that will give me a platform to build a satisfying career in the next 20 years? Absolutely.
The really hard thing for me at this point is figuring out where I really do want to go. In my case, a lot of the bad decisions were to do with "grass is greener" feelings -- I'd see one job that looked cooler than my current job, go out and get it, then decide it wasn't that cool and bounce to another one. So now that I've finally recognized that, where the fuck DO I want to go now, and how do I figure that out?
I think that's really important. Calling it "finding your passion" is bullshit, though, because it's not really about passion -- it's about making a sensible decision, taking everything into account including financial situation, family responsibilities, and the realities of various careers, as well as, yes, what you like to do. I'd love to be an astronaut, always wanted to, but -- life sucks -- it ain't gonna happen now. Not that it is 100% impossible, but I'm not willing to make the sacrifices it would entail. But there are great, exciting, satisfying things I can still do.
Another thing that's hard is making sense of the past while still keeping my focus on looking ahead to the future. That's what I'm trying to do now. I don't want to keep repeating broken patterns, so I feel like I need to think about what I've done in the past and understand it, to some extent, so I can see what I did wrong and how I can make sure not to do the same thing again. I think I've identified some of those things, but that's the main reason I'm seeing the counsellor -- I want to talk out my analyses of my past decisions and try to understand them and use my "lessons learned" for the future. I don't think completely ignoring everything that has gone before is right -- I did that for a long time and ended up making just the same mistakes 10 years later. But obsessing about the past is (obviously) not helpful either. It's a hard balance to strike.
So, you aren't alone. Very much not alone, I think. Hope you're able to make some sense of things. You can ALWAYS turn things around.
I have to disagree a little with one of the earlier points, though. Through start-up acquisitions, Google is getting a lot more groups with the developer/hacker mindset. Those groups tend to keep to themselves and rail against Google's slow pace, and often eventually quit. Google could learn from that mentality, but equally those developers could learn from Google's methodical approach. In my (limited) experience Google could do much better at integrating newly acquired start-up teams into the overall corporate culture and development philosophy.
Also, should you find an additional paper pass to be necessary, you'll find it complicated by the fact that the area to be wiped is now wet. Toilet paper notoriously doesn't hold up well when soaking wet.
Yes. It forces the expression of weak preferences which otherwise wouldn't be expressed.