While you do have to know what you are looking for, and walk the long way around from the larger Bletchley Park site, the National Museum of Computing is still (as of last year) there with volunteers showing off the workings of a bunch of rebuilt computers including the Colossus. I can't recommend a visit, with a guided tour, enough. And you might as well visit Bletchley itself while you are there, which is a different experience, but still worth while.
I had an issue with my own address on google maps (not as severe as this, it just had the wrong zipcode). After trying to correct it using the tools built in to maps 3 times and having my correction rejected every time, I tweeted my complaint @googlemaps, did a quick DM back and forth and it was fixed shortly thereafter.
(please do not take this as an endorsement of google maps support, merely an anecdote of what did work for me that I hope might help you)
When going from JFK to somewhere else in queens, yellow cabs are supposed to get a voucher from the dispatcher that allows them to skip to the front of the line when they get back to the airport. The fact that he was surprised when you said Queens implies that the dispatcher failed to do this, which explains both his going back to the dispatcher and his annoyance.
Re: daily standups. A lot of what the OP criticizes standups for is what I like about them. The content is only half of it. In my experience, it can be very easy for a team to cease feeling like one and instead become a loosely-coupled collection of independent contractors. 15-20 minutes a day of forced synchronous communication goes a long way to making you feel like you're actually on a team and therefore act like it, and is well worth the minimal time. This is especially true if the team isn't all in the same physical space. It can be disruptive, so scheduling it at the right time is important.
Of course, if you already have meeting overload, standup is going to feel like the worst.
it may not be possible to conceptualize all parts of a system simultaneously but that doesn't mean nobody can fully understand the system. A layer of abstraction isn't about not having to understand what's beneath it; it's a tool to aid in understanding.
Is it everything? No. But according to WGBH's media access group, "All major studios now caption and describe all wide released features and nearly all independent studios caption all releases."[1] In 2014, that description was available on at least 88 films released on DVD or Blu-ray[2]. As for television, in the US, the networks and the 5 largest cable stations are required to air about 4 hours of programming a week with description[3].
My point is: The biggest problem is no longer a lack of described content, it's a lack of access, particularly through internet streaming services which have the potential to provide the most accessible experience of all.
When I say that it seems no harder than adding more language tracks, what I'm talking about is adding pre-existing description tracks to Netflix. Of course producing new description is harder than adding existing language tracks.
Agreed that starting with their own content makes sense. As for the difficulty of adding existing AD assets, I'm unclear as to why this is any more difficult than adding more language tracks, something Netflix has been doing for years. As for procedural and contractual issues, advocates in the past have gone so far as to get the owners of the assets to agree to license to Netflix free of charge, to no avail.
It's sad that in the UK, VOD services are even further behind on accessibility. I do hope that Netflix is actively seeking out AD, but given their track record so far, I'll believe it when I see it.
Most of all though, I wanted to respond to one particular thing you said: "And for all the stick they get, Netflix actually leads the way in accessible content"
The lesson I've taken from this is that they don't get nearly enough, or perhaps the right kind of, stick. Advocates (and legislators in some countries) have been after Netflix on this issue for years, but what finally seems to have gotten Netflix to take action was when the mainstream media started picking up on the story. That action was swift and completely addressed the story that the media told. I therefore think it important to keep the story going in an attempt to ensure that Netflix keeps working on this problem.
this is the result of a multi-year fight by disability advocates, most notably Robert Kingett from the accessible Netflix project (https://netflixproject.wordpress.com/). What finally put them over the edge was the release of Daredevil, which made for a story the popular press finally bit: blind people can't enjoy a show about a blind superhero.
honestly, the fact that netflix remedied the situation so quickly once the PR situation got bad enough does not improve their reputation on this issue in my eyes. For a long time, I thought that maybe there was some great technical complication I just didn't understand that made this much harder than it seemed from the outside. Apparently that wasn't the case.
Also, as Kingett has said, "now comes the easy part." Adding description tracks on Netflix for all of the movies and TV shows for which they have been available all along.
The Samsung TVs do perform voice recognition through the mic on the TV as well as on the remote (well, at least mine, which is a couple years old, does). Even if you have the voice recognition setting turned off, the one on the remote still works by pressing the button.
The non-remote one does use a trigger word ("hi tv" by default) and it definitely does that processing locally (I know because i disconnected my TV from the internet and tried it). Basic commands ("channel up" etc) also worked. I don't know what else to try to figure out when it goes out to the internet. I'd also add that the camera/microphone have a very visible hardware off (which I keep off, because life is too much like 1984 already).
if you're using android, i suggest you try bubbleupnp https://play.google.com/store/apps/details?id=com.bubblesoft.... It doesn't seem to have the problems you describe, and it's also very happy to send stuff to a chromecast instead of a DLNA renderer. I could see how it's possible that your renderer is the cause of the problems, and that can be harder to replace since it's probably embedded in your TV (I've only used chromecast and samsung TVs).
I've actually had little to no trouble with DLNA overall, using among other things the ReadyDLNA server for a sparc readynas and rygel on ubuntu. i suppose it only takes one bad implementation among the components in your setup to ruin the whole experience, but i've been pleasantly surprised over the years how well it seems to work.
bubble doesn't have the best UI, but it's not bad, and there are other apps that are prettier (allcast comes to mind). in the past i would have totally agreed that most upnp controllers i had used had TERRIBLE usability, but most of those were embedded in A/V equipment (TVs, receivers), and what A/V equipment have you ever used with a good UI?