> ""By submitting, posting or displaying the content you give Google a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content which you submit, post or display on or through, the Services.""
That doesn't sound great.
Introducing the worlds largest stock photography service "GOOGLE Stock Photography". So inclusive, it probably has many of the photo's you have taken in the last few years!!!
Years ago I was managing 10 racks, and I built some scripts to automate turning an SD card filled with images into HTML pages. I would bring in my midrange Nikon DSLR and take photos of the cabinets (upper, mid, lower, both front and back). These high quality photos allowed for high zoom levels that often came in handy. We had facility staff thank us for sending photos with our work requests on remote hands issues.
Now I watch youtube videos with people taking apart and repairing electrical and car related things and think "It sure could be handy to have a full video record of repair work."
I've also been remodeling my house and have taken copious photos of the work, both to help the inspectors, and for future work.
My brother in law just had a house water damage issue and several rooms were torn down to the studs. I recommended he take photos while the walls were open, for future reference.
There's a great use case for taking lots of photos.
I eventually "intuited" how it fit together, but I caused damage to the pins in doing so. A single photo of the assembled version would have really helped.
I've got a desk in a co-working space with a locking cabinet underneath that has a godawful (three-wheel, not dial) combination lock that is impossible to read in low light. Worse, the dials are chrome so shining a light on it produces specular highlights that make it even harder to distinguish the numbers. I regularly have to snap a photo of the lock, zoom in, and adjust the wheels based on the photo.
Although your method is bullet-proof in one sense: if a contractor agrees to show you pictures of other clients' infrastructure, you might not want to hire someone who is such a security risk :)
Whenever I have to debug / gut components out from my PC, you pretty much had to take pictures. Especially if you need to determine which point of failure you have (hardware, or software related).
I’ve never thought of using slo-mo video to capture overly fast error messages.
Dealing with any data that is defined under a compliance policy of some kind, for instance.
Gives one a hint of how useful good lifelogging could be.
However yes, I like photograph not only to fix for future reference something but also to document what I'm doing, and also other kind of logging, sometimes useful if something goes wrong not because of me but someone like to say it's because of me...
And for that a traditional pocket voice recorder is really good, plus eventual camera on it :-)