I used to work at an accounting/consulting firm who were dead set on writing business applications in VBA within Excel. The code was embedded in the notebook, and to distribute the software was sending the latest version of the Excel file. This made version control virtually impossible, and we would instead combine our work manually.
I cannot recommend having tech-illiterate people lead software projects.
The amount of times I hear people telling me that "I should just do it in Excel". Excel. Is not. A database.
Excel is a whole OS unto itself. Like Emacs except you can get out of it.
Excel is a single-assignment dynamically-typed functional programming language with a really obtuse editor.
Stop... Stop... I'm already dead
Good software starts in Excel honestly. But oh god should you not stay there... Its not designed as a database indeed.
Access is the worst of both worlds.
There's nothing more permanent than a temporary solution
Close enough when your actual database system is written in fucking COBOL.
I used to work at an accounting/consulting firm who were dead set on writing business applications in VBA within Excel. The code was embedded in the notebook, and to distribute the software was sending the latest version of the Excel file. This made version control virtually impossible, and we would instead combine our work manually.
I cannot recommend having tech-illiterate people lead software projects.
The amount of times I hear people telling me that "I should just do it in Excel". Excel. Is not. A database.
Excel is a whole OS unto itself. Like Emacs except you can get out of it.
Excel is a single-assignment dynamically-typed functional programming language with a really obtuse editor.
Stop... Stop... I'm already dead
Good software starts in Excel honestly. But oh god should you not stay there... Its not designed as a database indeed.
Access is the worst of both worlds.
There's nothing more permanent than a temporary solution
Close enough when your actual database system is written in fucking COBOL.