4 ms·
Thanks for saying that. I worked on a bunch of large transit fare-card implementation projects for accenture, over a decade ago. Having a large company, with pe
by charles_f 4y ago
Thanks for saying that. I worked on a bunch of large transit fare-card implementation projects for accenture, over a decade ago. Having a large company, with people having some know how from previous implementations, and the ability to handle a project that was far, far beyond the capacity of the transit operators cautioning them, made TOTAL SENSE. We effectively shipped stuff, in a very political environment (as in, with actual politicians trying to dictate requirements so the schedule fits their re-elections and stuff like that), through lots of integration pains and issues with large scale hardware deployments. I'm pretty proud of those projects, I'm sure some of the code I wrote back then is still in prod. I never worked as a bodyshop, or sold useless erp replacement projects. The outcome was a working system that millions of users can use. It's palpable. It's concrete. It's useful.
It pains me that it's always seen as an evil, because sometimes it is the best option.
- AaronFriel 4y agoWas the use of your team necessary due to the political and regulatory capture, however? I don't know what you did, and I don't want to besmirch it. So let's take a recent "successful" project: OMNY, the new transit fare system in NYC. That system cost the New York Metropolitan Transit Authority over three quarters of a billion dollars. $772,000,000. To put that in comparison, the point of sale payment processor Square raised 170 million fewer dollars over from seed to series E and does fifty times as much payment volume. There is a staggering amount of inefficiency in these projects, and I suspect it's because of capture.