@TDWTF123 said:
I haven't said that once. Your anti-Excel prejudice is so strong that you refuse to accept the correct way of doing things.
Like I keep telling you, the fixed Excel proposal was half an hour's work for someone who knows Excel. You haven't suggested at any point that the alternative was comparable in terms of resource commitment
Bullshit. Go back and read the OP. OP's company has data stored in a database somewhere. They need to get that data out to another company. That other company helpfully has a webservice API. Where the fuck does excel even come into the scenario? Why would anyone even THINK about using excel to do this?
And how would using excel as a middle layer from the database to the other company have any savings whatsoever? They'd still have to learn the webservice API and figure out any integration issues. Just now you've added a layer of excel quirks to the process.
Unless your plan is to fiddle with the excel spreadsheets the data entry monkeys may or may not be using to put that data in the database in the first place. That's a bad idea for several reasons, and again runs into the problem of STILL needing to do the same work as the database-to-API scenario anyway.
@TDWTF123 said:
It's very obvious to anyone without prejudice that the manager cancelled the project not out of irrational spite, but because something that was supposed to be a quick job was suddenly being quoted as a major programming task because the programmers insisted on reinventing the wheel, the axle, the cart, the horse, and the road.
The problem here is that it was ALWAYS going to be a major programming task. If she was thinking of it as a "quick job," then that was a stupid estimate by someone who isn't competent to make that determination. And if that's why she cancelled it, that is STILL a major management WTF.