31 karma · joined June 23, 2021
I’ve had a similar issue with the Business Model Canvas which, while very useful in visualizing a business’ model, leaves me hanging and a bit uncomfortable because, as you said, there are no (or incomplete) hard data to back up its claims.
On the other hand, if we were to consider these tools as just hypotheses makers and validate those hypotheses with the company’s financials (among other things), I think they’d be a very valuable component of a very able business management toolkit.
Some time later, I came across the usage "X comprises Y and Z" and, based on my previous understanding that "comprise" == "compose," I took that to mean "X composes Y and Z" which, in other words, means "Y and Z are made up of X". But really, it means the other way around which is that "X is made up of Y and Z!" Only when I learned about the dual meaning of "comprise" did I correctly understand it to mean the latter.
To this day, I still have to actively juggle this arbitrary "dual-rule" in my head when I come across "comprise."
So given an interest per annum of 1% (for example), a $1m deposit would add $1m liquid, non-earning assets while also adding $1.01m to their liabilities. So, effectively, they’d have $10,000 in unsecured liabilities.
To counter that imbalance (as well as protect the cash from the effects of inflation), they’d have to put some of that cash to work via various investments.
That presupposes that our existing tools for detecting the presence of ToM are 100% accurate. Might it be possible that they are imprecise and it’s only now that their critical flaws have been exposed?
In other words, the LLM wouldn't be the equivalent of the human brain. Instead, it would just be equivalent to that part of the human brain that processes language.
https://github.com/relaxdiego/dotfiles/blob/main/run_once_07...
https://drive.google.com/file/d/0B75fn5jlTYO3ODQ5X0NhM0txQ2M...
Just recently (finally) added functionality that auto-tests the code snippets in my articles. I talked about it in this article: https://relaxdiego.com/2022/02/autotest-code-snippets.html
https://blog.thecodewhisperer.com/permalink/integrated-tests...
The above assumes though that I’ve done enough previous discovery to have a relatively robust model of the problem domain. If not, I prototype first and during this stage I won’t be using TDD. Prototypes produced are throwaway, of course.
I say this with the assumption that the team is large and members regularly come and go.
However, should a day come when a new method circumvents this very crude way of knowledge transmission, this debate will be significantly changed or even rendered moot.
It does but you have to use Fn with the delete key.