25 karma · joined December 22, 2023
I wish brevity and linguistic precision were taught more, as well. Miscommunication due to ambiguity is one of the biggest causes I see for confusion or heated arguments.
Glad to see some schools and teachers teach how to use them well, rather than ban them outright.
I tried to take advantage of it, but the implementation felt really clunky (formatting seemed to be via menus only), so I’ve stuck with .txt files.
If they're not labeled, or are shown even to paying users, I think that's a problem.
> Saying something like “Go to my cases” is awkward and unnatural – if I told you to go to my cases, you’d think I was telling you to go to my cases, not yours.
A help article should use proper capitalization. a couple extra words can add clarity too. For example, "Go to the 'My Cases' page."
Many people don't know how to write good help articles, though, so it's probably still best to avoid "my"/"your" in UIs.
I know that sounds kind of sad that my brain can't focus that well (and it is), but I appreciated the cat.
In other words, if your tables aren't referencing other tables, how do you perform JOINS for your queries? From my limited experience, they seem pretty essential for most databases. Or is the article just talking about foreign key CONSTRAINTS and cascading UPDATES and DELETES, rather than literally talking about the values stored in foreign key columns?
If anyone can explain, I would greatly appreciate it.