1,208 karma · joined October 7, 2009
From the paper: "The drives in our study are custom designed high performance solid state drives, which are based on commodity flash chips, but use a custom PCIe interface, firmware and driver."
These aren't drives that you can just go out and buy, so brands and model numbers would be meaningless to anyone outside of Google.
Link to the paper: http://0b4af6cdc2f0c5998459-c0245c5c937c5dedcca3f1764ecc9b2f...
Picasa Web Albums will continue working until the album archive view is ready.
Also, all of the photo from PWA are hosted in Google Photos Backend - and will continue to be hosted there. There are accessible in Google Photos and the URLs will continue to work.
If you haven't seen it, the original blog post has better information than the linked article: http://googlephotos.blogspot.com/2016/02/moving-on-from-pica...
Source - I'm a mid-level engineer at Google and my total comp is within the stated range.
I really want it to be true...
It's hard to imagine how a gas-based "containerless processing system" will lend itself to producing the thin, uniform sheets of glass for windows or complex shapes like tableware.
It's a cool prototype, but figuring out how to produce at scale is often the hard part.
It varies a lot by project and by how widely used the code is.
There are few (if any) strictly enforced rules for documentation or invariant checking. You basically have to convince at least one other engineer that what you have is sufficient.
The documentation is _generally_ pretty decent for core libraries, but sometimes you just have to read the code.
OWNER and readability approvals may require additional reviewers but not always.
At the end of the day you were the one sitting in the chair and had to make a judgement call based on your training and observations.
Think of this way - if you hadn't reacted as you did and the girl ended up injured or dead, how much worse would you feel today?
Conceptually, Google Photos is very much a V1 product. It might sound a little weird since the team is experienced and a lot of the technology it is built on has been through multiple iterations.
But from a _product perspective_ Google Photos is a new product.
The product team was really focused on a few key aspects of the user experience (I'm not going to try to enumerate them here. The main reason is that I would certainly do a poor job of explaining them. The other reasons are that I can't remember how much of the strategy has been talked about publicly and it doesn't really matter for the point I'm trying to make).
Being focused meant saying no to things - at least for the initial launch.
So the first answer to your question is that for most of the mentioned features the answer is that they simply didn't make the cut for V1. I can't comment on which features will or won't make it to future versions.
Date picker is an interesting one. Really, the only reason it existed was to work around how painful it was access older pictures in Google+ Photos, Date picker was added to (somewhat) ease that pain.
In building a new product, there was a desire to make things like date-picker unnecessary. Make finding older photos so fast and painless that you don't even need it. Try grabbing the scroll bar in the new web-app - you can scroll to any time you want in seconds. On mobile, it's easy to zoom out, scroll and zoom back in.
There is also search, which often means you don't even _need_ to scroll through your photos to find what you want. Just this morning my wife wanted me to find a picture of a tatoo from six years ago. I was able to find it by searching for tatoo. It was awesome! In Google+ Photos I would have spent a long time trying to figure out the right date range and then searching around.
If you really want to jump to a date, just type it in search - I just tried "September 2012" and "9/23/2012" and they both worked great.
So I would argue that date-picker just flat out isn't needed any more, because the team focused on some core user experience flows.
The blogger photos will still be stored in the same place and the urls should continue to work.
Picasaweb, Google+ Photos and Google Photos all store the photos in the same place.
There was never any need to "shuffle gigabytes of photos" when moving from picasaweb to G+ Photos and there won't be any needed to move from G+ Photos to Google Photos.
I don't see howany of that adds up to "do not rely on Google for your photo storage needs".
From the article: "I had been worrying about things like -0x12345 and -9223372036854775809 and 9999999999999999999, even though those numbers would not be something a programmer would be likely to encounter"
For his project, negative hex numbers were an explicit non-goal.
My understanding is that it comes down to a "reasonable person" doctrine - i.e. would a reasonable person consider the location to be private.
Another way of thinking about it is if there is a reasonable chance that you will be seen by people engaging in normal everyday activities.
Personally, I would say that peeking through a small gap in the curtains would not qualify as normal behavior. Someone doing that is clearly snooping.
On the other end of the spectrum, having sex in front of a window that fronts a public sidewalk with no curtains would pretty clearly be public indecency.
It doesn't match my experience. In almost seven years at Google I've worked on amazingly interesting projects - from hardware to user-facing products.
I've never once, in my entire time, had any level of management tell me that I should be worrying about selling ads or monetizing my projects. The consistent message has been "build great products".
So the notion that 99% (or really any majority) of developers at Google "drive the ad hive" is completely untrue - at least in my experience.
Because in my personal experience - as both an interviewer and a hiring committee member - what you said is completely wrong.
> they don't count a lot of factors while rejecting a candidate, you make one > mistake on their particular set of questions, you are out.
Completely false. I have personally seen many people get hired despite doing poorly in an interview or making mistakes.
The hiring committee looks at all of the available information - resume, recommendations, and interview feedback when making a decision. There is no "one-thing" that will make or break a candidate.
> They don't even look at your resumes until all your 4 interviews are completed
I have no idea where you are getting this from. All interviewers receive the candidate's resume prior to the interview. I always review the resume's to get a sense of what the candidate has done so I can ask appropriate questions.
I can reproduce this on my own account.
I uploaded a raw (NEF) using desktop uploader using the "Original" setting. Downloading through the photos app returns the original NEF file.
Downloading via Drive returns a file with the original name ("Foo.NEF") that is actually a jpeg.
So this is clearly broken.
Bug filed. I will follow up when there is some kind of resolution.
It's definitely something that we've talked about internally and is something that I'd personally love to see in the product.
There are geo-tagging feature in the new app: * For any photo you can click on the "info" icon (i with a circle around it) which will show the photo's location (if we have geo information for the photo) * The search functionality makes use of geo-tagging information - so you can search for photos from a specific place.
Is that what you were looking for, or is there something else?
I can't really comment on what might or might not happen in the future, but I can pass on requests/comments to our PMs and/or help you out with the application.
I will file bugs for the drive-sync issue and the issue with the large downloads failing and try to get some answers.
If you have concrete examples I could investigate.
I just tested on Android with the latest build and I get a trash icon in the expected places - in the bottom right corner in the single photo view and in the top right corner in the thumbnail view (once at least one photo is selected).
BTW, I work on the photos team.
In all of the hiring committees I've participated in I can't remember a case where the candidate's school was a significant factor in the hiring decision. Even for new grads.
It's possible that it's given more weight in the pre-screening process, but once you get to interviews it just doesn't matter much at all. At least that's my experience as both an interviewer and a hiring committee member.
As I was reading I kept waiting for the big "..BUT.." that would talk about how Shakespeare wasn't a genius. It wasn't until I got to the section on garden path sentences that the purpose of the title clicked. The author of the article was employing one of the very "tricks" he talks about in the article!