I don't know your background but "taking an Excel workbook and using that as requirements to drive an implementation" is not speedy. I've done this several times in my career and it's very, very difficult. Not because there is any "idealization", but because the reason the spreadsheet works is because a human is doing half of the work. These spreadsheets are not some "hello world" easy to understand product - they are the result of months/years of effort by a team of individuals which has grown beyond Excel's ability to handle. Translating that into code is not "quick and speedy" even if one is doing a like-for-like implementation.
simooooo|8 years ago
Additionally the original excel sheet made incorrect assumptions, resulting in a re-specification/design of what all the totals actually count.
NOT speedy.
endorphone|8 years ago
So...not as I described then? If you are evaluating assumptions and going back to the drawing board, of course it won't be speedy. The point is that if it's simply a requirement to be implemented as is, it is a quick and speedy process.
And it is. I mean, there are dozens of products that will automate the entire process it's so rote.