Mac Reiter
My feedback
2 results found
-
429 votes
An error occurred while saving the comment An error occurred while saving the comment Since you seem to have been ignoring the hundreds of votes for this on the other suggestions for at least EIGHT YEARS, the only thing I can think to do is increase the NUMBER of separate suggestions until you pull your head out.
An error occurred while saving the comment Since you seem to have been ignoring the hundreds of votes for this on the other suggestions for at least EIGHT YEARS, the only thing I can think to do is increase the NUMBER of separate suggestions until you pull your head out.
An error occurred while saving the comment Eight years. EIGHT years. EIGHT _YEARS_! Just precisely how far do you have your head up your backside that you haven't even assigned an intern code-monkey to this at some point in the last eight flipping years? Do you understand, at _ANY_ level, how stupid this makes your team look? In pretty much ANY app, for ANY reason, when the user makes a preference change, there is some simple way to immediately experience that preference change. Would you leave "language selection" or "dark mode" settings without some way to experience them BEFORE getting into a fully routed drive? NO. You let the user experience their choice immediately or almost immediately. Is your code base such garbage that it is actually DIFFICULT to get a selected voice to say something? I mean, it should just be adding "say('Hello, it's nice to meet you')". But how could it possibly take you -- and I know I'm getting extremely repetitive, but I have to say this again -- EIGHT DAMNED YEARS to do something that simple? Which suggests to me, a software engineer, that your code base is so hopelessly baroque and fragile that I shouldn't be trusting it with any decision making...
An error occurred while saving the comment Eight years. EIGHT years. EIGHT _YEARS_! Just precisely how far do you have your head up your backside that you haven't even assigned an intern code-monkey to this at some point in the last eight flipping years? Do you understand, at _ANY_ level, how stupid this makes your team look? In pretty much ANY app, for ANY reason, when the user makes a preference change, there is some simple way to immediately experience that preference change. Would you leave "language selection" or "dark mode" settings without some way to experience them BEFORE getting into a fully routed drive? NO. You let the user experience their choice immediately or almost immediately. Is your code base such garbage that it is actually DIFFICULT to get a selected voice to say something? I mean, it should just be adding "say('Hello, it's nice to meet you')". But how could it possibly take you -- and I know I'm getting extremely repetitive, but I have to say this again -- EIGHT DAMNED YEARS to do something that simple? Which suggests to me, a software engineer, that your code base is so hopelessly baroque and fragile that I shouldn't be trusting it with any decision making...
An error occurred while saving the comment Since you seem to have been ignoring the hundreds of votes for this on the other suggestions for at least EIGHT YEARS, the only thing I can think to do is increase the NUMBER of separate suggestions until you pull your head out.
An error occurred while saving the comment Eight years. EIGHT years. EIGHT _YEARS_! Just precisely how far do you have your head up your backside that you haven't even assigned an intern code-monkey to this at some point in the last eight flipping years? Do you understand, at _ANY_ level, how stupid this makes your team look? In pretty much ANY app, for ANY reason, when the user makes a preference change, there is some simple way to immediately experience that preference change. Would you leave "language selection" or "dark mode" settings without some way to experience them BEFORE getting into a fully routed drive? NO. You let the user experience their choice immediately or almost immediately. Is your code base such garbage that it is actually DIFFICULT to get a selected voice to say something? I mean, it should just be adding "say('Hello, it's nice to meet you')". But how could it possibly take you -- and I know I'm getting extremely repetitive, but I have to say this again -- EIGHT DAMNED YEARS to do something that simple? Which suggests to me, a software engineer, that your code base is so hopelessly baroque and fragile that I shouldn't be trusting it with any decision making...
-
47 votes
We plan to work on adding an option to hear Voice samples when choosing in the near future. In the meantime, make sure you’ve got the latest version of Waze for all the latest features.
An error occurred while saving the comment Eight years. EIGHT years. EIGHT _YEARS_! Just precisely how far do you have your head up your backside that you haven't even assigned an intern code-monkey to this at some point in the last eight flipping years? Do you understand, at _ANY_ level, how stupid this makes your team look? In pretty much ANY app, for ANY reason, when the user makes a preference change, there is some simple way to immediately experience that preference change. Would you leave "language selection" or "dark mode" settings without some way to experience them BEFORE getting into a fully routed drive? NO. You let the user experience their choice immediately or almost immediately. Is your code base such garbage that it is actually DIFFICULT to get a selected voice to say something? I mean, it should just be adding "say('Hello, it's nice to meet you')". But how could it possibly take you -- and I know I'm getting extremely repetitive, but I have to say this again -- EIGHT DAMNED YEARS to do something that simple? Which suggests to me, a software engineer, that your code base is so hopelessly baroque and fragile that I shouldn't be trusting it with any decision making...
Since you seem to have been ignoring the hundreds of votes for this on the other suggestions for at least EIGHT YEARS, the only thing I can think to do is increase the NUMBER of separate suggestions until you pull your head out.