3 ms·
Doing complex modelling in Excel is not a good idea. There is no way to do proper software engineering, so bugs are common and hard to find. For examples, see
by adrianN 11y ago
Doing complex modelling in Excel is not a good idea. There is no way to do proper software engineering, so bugs are common and hard to find. For examples, see
http://www.eusprig.org/horror-stories.htm http://www.eusprig.org/horror-stories.htm
- CPLX 11y agoA complex model in Excel is software engineering. The degree to which it is "proper" of course, is situational.
- crispyambulance 11y agoSo? Many great projects start out as excel spreadsheets: someone has a problem, solves it with excel, then goes on to solve other problems with that spreadsheet. People use it and become dependent on it, but over time the thing becomes intractable. At that point in time, the functionality of the spreadsheet gets implemented by actual developers into some "engineered application." If you are suggesting to NOT start with excel, then propose another solution-- but good luck getting anyone to use it. The key thing is, no one wants to engage "software engineers $$$" to solve a problem that lands on their desk which they handle by themselves.
- osullivj 11y agoAnd once some devs turn it into an "engineered application" the change cycle jumps from minutes or hours to days, weeks or even months.
- TheLogothete 11y agoShh! Your logic and practical experience is not welcomed. We like to scream with self-righteousness from our software engineering high horses here. Software engineers know best and everybody else is wrong because he doesn't know any better, since he has a limited perspective.
- cm2187 11y agoor years. I often have the fantasy to write "Powered by COBOL" below the logo of my company.
- eterm 11y agoExcept "proper software engineering" would mean whatever is being built simply never gets built. In many cases it's better to get somewhere quickly with excel then work out if "proper software engineering" is required than never get off the ground because engineering something is too difficult. Think of excel like lego. Someone can quickly build something out of lego. Now if someone tried to build a cathedral from lego, you might suggest that they find an architect and do some proper house building, but without lego they would never have tried. And chances are they're not building a cathedral.
- elcapitan 11y agoThere's actually an interesting gap between 'building some model in Excel' and 'moving on into a programming model where code and data are separated'. Like generating model code in some normal programming language from a spreadsheet.
- eterm 11y agoDoes VBA fill that gap? I once worked on a system where one of the more important parts of the business was a system of VBA modules in an access file. One of my more important contributions as a fresh graduate entering the workplace was to get people to copy the file from the network share to a local drive before running. Run-times went from "leave overnight" to ~15 minutes.
- tamana 11y agoRight, but why VBA? Because VBA is the only language with first class support in Excel, not because VBA is good at all. If not fon its "privilege", you'd use something like Python or JavaScript (yah it sucks, but not as bad a VB) or a purpose-built sane language, not something Joel Spolsky dashed off a spec for one Tuesday afternoon.
- adrianN 11y agoJust like I wouldn't want to live in a house built from LEGO, I'm somewhat wary of Excel models as the basis for investment strategies in major banks. The problem with the quick and hacky solution is that it's never replaced, because that would cost money, and the current solution "looks like it works".
- cm2187 11y agoThe proper software equivalent is https://web.nvd.nist.gov/view/vuln/search-results?query=&search_type=last3years&cves=on https://web.nvd.nist.gov/view/vuln/search-results?query=&sea...