The healthcare system of a country was run in Excel. Didn't you read the title?
> so it should be used less, not more
I never said it should be used more, I said the fact that it could be used for that, makes it an impresive achievement for the app.
The healthcare system of a country was run in Excel. Didn't you read the title?
> so it should be used less, not more
I never said it should be used more, I said the fact that it could be used for that, makes it an impresive achievement for the app.
Obviously I have read not just the title, but also the article.
>I said the fact that it could be used for that, makes it an impresive achievement for the app
You can try to use a fork to dig a tunnel, but it is hardly an impressive achievement of the fork that it can be used this way, neither you could possibly dig anything big with it. It would be an impressive achievement for Excel, if it actually worked, but the article mentions that there were problems with accounting done this way.
Excel is a powerful tool that can handle massive amounts of data, no doubt. However its feature set is not enough for this kind of tasks. As @zimpenfish said in another comment in this thread, the problem was both in Excel and in processes. Task-appropriate tools help to build good processes around them.
Certainly the wrong tool for the job, but nevertheless impressive for both the technology and the operators if it somehow works.
Perhaps we should re-evaluate how and when we use things when presented with evidence that others are getting massive value out of tools we typically would have been biased against.
Still, if many successful enterprises started SQLite for things of this scale, I should probably reach out to them to see whether there's anything missing from my analysis.