41 karma · joined January 4, 2019
> Put another way, there is always some shared context going on; that's what language actually is in the first place. I have used a number of words in writing this comment, but I haven't set out any definitions; that's because I'm assuming that you know English in order to read my comment. If I were trying to communicate to a child, I wouldn't be using all of the words that I'm using here, because it is too complicated for them to comprehend. But, trying to explain the topic of this comment to that child would take much longer, and be much more difficult.
Thanks for this. I always struggle to articulate it.
I understand a shell script is not suitable for orchestrating a datacenter, but sometimes it is suitable for installing a couple of things.
Is the algorithm deficient?
To me that looks like code that indeed checks the strength, so I must be missing something.
Not the kind of reading material most people would turn to, admittedly. I've recently found this:
It feels like a good balance between quotes straight from the spec, and explanation from the author.
If you worked in a company that had a core product in a repo, and you wanted to create a slack bot for internal use, where would you put the code? I assume not within your core product's codebase, but within a separate repo, thus creating a polyrepo situation.
So when you say a monorepo will serve you in 99% of cases, are you not counting "side" projects, and simply talking about the core product?