71–80 of 93 posts
Software does not suck; requirements, especially from non-technical stake-holders suck. Every single piece of software starts with a single and easy to understand idea, then different stakeholders arrive and start adding inputs and often conflicting requirements, and then software starts to suck. None of these would have happened if we knew how to say "No". :(
I see you've read that terrible book by uncle Bob and now you're a professional coder. :)
Earlier quoted context omitted.
This isn't a bug. Recommendations are just hard. He's trivializing it, but specifically mentions that including one 5.7 miles away would be fine. And then promptly says because he visited it before. That's some complicated intelligence and pattern matching that he's asking for. What exactly should it be ranking by? Proximity and popularity and traffic density and Google rating and awhole load of other things. The rul…
Seems like a case of adding "ORDER BY number_of_previous_visits, distance" to a SQL query...
Especially when you add in rankings, you start having to think about sorting by multiple layers, circles of distance with ranking sorted by that.
So the really good match 20 miles away is shown lower than the pretty good match 5 miles away, but they're both shown above the bad match 7 miles away.
And that's before you add categories, past history, any paid ranking, etc. And then the queries get really expensive and you've got to decide what to fudge or not to keep the system responsive and stop your search system eating all your CPU.
And you can bet people will still find scenarios where they'll say "why's it doing this? I'd expect the order to be different".
This is pattern matching and value assignment, something humans are amazing at and computers aren't.
The reason for pretty much any bug found in software driven by a huge company is that there is a large disconnect between fixing bugs and profit. Fixing a bug almost never excites users, and even if it did in this case, they won't see a measurable increase of users of their software, so you can't prove a profit increase. Even if a bug is fixed, the effort might be wasted when a large overhaul of the system happens be…
The counter-argument is that we’re (mostly) talking about profitable companies making billions a year, which will be wasting tens or hundreds of millions anyway on unneccessary spending, poor strategic decisions, and other standard corporate cash sinks. Why not gain reputation and good will by making users happy and deliberately cultivating a reputation for low-frustration, responsive, thoughtful and reliable product…
The reason for pretty much any bug found in software driven by a huge company is that there is a large disconnect between fixing bugs and profit. Fixing a bug almost never excites users, and even if it did in this case, they won't see a measurable increase of users of their software, so you can't prove a profit increase. Even if a bug is fixed, the effort might be wasted when a large overhaul of the system happens be…
The reason for pretty much any bug found in software driven by a huge company is that there is a large disconnect between fixing bugs and profit. Fixing a bug almost never excites users, and even if it did in this case, they won't see a measurable increase of users of their software, so you can't prove a profit increase. Even if a bug is fixed, the effort might be wasted when a large overhaul of the system happens be…
This isn't a bug. Recommendations are just hard. He's trivializing it, but specifically mentions that including one 5.7 miles away would be fine. And then promptly says because he visited it before. That's some complicated intelligence and pattern matching that he's asking for. What exactly should it be ranking by? Proximity and popularity and traffic density and Google rating and awhole load of other things. The rul…
Unrelated but similar and I feel like venting... On Google Maps you'll search for something, and the results are shown as a list that almost covers the entire map. It's Google MAPS and it hides the map for so many things. I'd rather go to a place that's 3 miles straight down a free way than 2 miles of stop lights, but I don't know that if the map is covered!
Or why's it so hard to get it to show a street name? It will show some, and it won't show others. If the one you want is in the latter category you've got a lot of zooming before you see it. Ugh.
The reason for pretty much any bug found in software driven by a huge company is that there is a large disconnect between fixing bugs and profit. Fixing a bug almost never excites users, and even if it did in this case, they won't see a measurable increase of users of their software, so you can't prove a profit increase. Even if a bug is fixed, the effort might be wasted when a large overhaul of the system happens be…
There is a tipping point. Just ask TSB. At some point you need to clean up your tech debt or you risk systemic failure.
I feel that the worst new "feature" in Google Maps is when you're on your way to your destination and it suddenly suggests you might first want to go to a random place you've never heard of before. You then have 3 seconds to tap "No" before it silently adds the destination (and 15-30 minutes of extra driving) to your route. I have found no way to disable this feature. I'm worried that there could be people who were i…
I have never heard of this. And judging by other responses, nobody else has, either. Are you sure you're not confusing that with rerouting you based on traffic? And that the extra driving was done to get around a traffic jam? EDIT: Are you tapping the map while driving? https://productforums.google.com/forum/#!topic/maps/LqK7zqz6... Also, why are people using Google Maps instead of Waze for navigation?