I see this kind of reply often, but I don't think it's the right approach: "We are sorry: what you are saying is correct, but we won't fix it because it's hard to do. Next time, try to complain about the easy fixes".
I don't think the customer should be required to be an engineer before noting that something is wrong, nor the company should be able to use its own deficiencies as an excuse about why they won't solve it. And particularly not in the case when the company is directly benefiting from its own incompetence.
I think you misunderstood his point. He was calling out "why would you wait for a fare increase to do that" as being naive, not "this is a problem that needs to be fixed".
Nothing wrong with calling out the problem as needing to be fixed, just saying that making two changes at once is vastly superior to trying to make two sets of changes in these situations.
The problem comes in when these same people make uninformed proclamations of how easy or simple things are to fix.
My answer is yes.
(Though for the sake of whomever maintains the system I'd certainly hope to be wrong about this! Either way, an update to all of these machines is likely not the trivial change the author presumes it to be.)
Also you would want to test every machine that gets the update in either case, so you need some kind of tech to touch every machine.
Maybe it's better if the network interactions of these sorts of machines are strictly limited to operational transactions. Maybe it's better if it does takes a human being with a key, guarded by a cop with a gun, to update this software.
Agreed, one should be fairly close to the dev team before coming up with estimates. Other red flags: "government agencies" & "So the MTA could make a small software change that only applies to the Credit Card Only machines with limited effort"
Clearly it is more work than a simple price change to create a new user interface that asks whether you're going to be using a credit card or not before displaying the prices.
It had been a longstanding pattern in software engineering to gradually simplify UI. As a result a lot of UI's are simple and people are assuming underlying systems are simple as well. In majority of the cases that is not true and simple UI is produced by highly complex underlying software. Confusion comes from the fact that people look at the UI and think this is simple, you just need to change this number there. When in reality you need to change an underlying system and that change could range from trivial to rewrite entire system in complexity.
Where there is an issue here is that if the software change only applied to credit card sales, there would be an accusation that the machines now favor more affluent customers who can afford to own credit cards.
Now figure out why your comment's wrong as an exercise in getting better at gathering requirements. Hint, they have to do something to all the machines every year or two...
I don't know how software updates are rolled out, but it wouldn't surprise me if a technician has visit each machine individually.
This isn't some trivial change to a non-essential web app, but rather a significant investment in time, energy and money.
The prudent thing to do would therefore be to roll many changes into releases and minimize the number of releases done.
Given how few people this issue affects, I'm glad the MTA is pushing this off: I'd actually prefer they didn't fix this issue.
---
Also, to argue that this affects poor people the most while arguing that an acceptable solution is to make a change exclusively for people who use credit cards illustrates having a minimal understanding of poverty.
---
Finally, judging agreement by how many hits you get is an absurd thing to do.