3 ms·
I understand the speed of the command line when it comes to entering data, and honestly, I've never even considered using something like Git to handle accountin
by cyberferret 10y ago
I understand the speed of the command line when it comes to entering data, and honestly, I've never even considered using something like Git to handle accounting data, but I think it sounds like a neat concept (after all, who of us wishes we could completely undo a set of journals that were accidentally entered into the wrong period).
But my experience is mainly in medium to large businesses with multiple users working on the information in real time, and with strict audit policies around them. I would imagine that would be a nightmare to try and handle using a distributed version control repository, let alone having situations such as one user uncommit their nefarious journals funnelling payments into their own bank account etc. I can imagine the face of the auditors having to run commands like `git compare` on the ledgers to trace transaction history... :)
- adrianratnapala 10y agoI imagine the biggest difficulty in these situations is dealing with other people: just like LaTeX might be better for certain kinds of documents, but the world still wants MS Word. But if we look narrowly at functionality, it seems that plain-text and git might be better for strict audit situations. In a Git history every thing you do has to has a "paper trail" in the form of a hash chain (admittedly using an outdated hash function). People can only "uncommit their nefarious <anything>" is along as those transactions never found their way to someone else' hard disk.