# | word | meaning | details | id |
---|---|---|---|---|
1 | .a |
sumti or. | logical connective: sumti afterthought or | A |
2 | .a'a |
attentive. | attitudinal: attentive - inattentive - avoiding (cf. jundi, rivbi) | UI1 |
3 | .a'acu'i |
inattentive. | attitudinal: attentive - inattentive - avoiding | UI*1 |
4 | .a'anai |
avoiding. | attitudinal: attentive - inattentive - avoiding | UI*1 |
5 | .a'e |
alertness. | attitudinal: alertness - exhaustion (cf. sanji, cikna, tatpi) | UI1 |
6 | .a'enai |
exhaustion. | attitudinal: alertness - exhaustion | UI*1 |
7 | [.a'i ](https://en.wiktionary.org/wiki/Appendix:Lojban |
word | ||
---|---|---|
ابا | ||
اباء | ||
اباق | ||
ابان | ||
اباه | ||
ابت | ||
ابتر | ||
ابتز | ||
ابتع |
import 'dotenv/config' | |
import { | |
PollyClient, | |
SynthesizeSpeechCommand, | |
} from '@aws-sdk/client-polly' | |
import fs from 'fs' | |
import read from '@nerdbond/read' | |
import TERM_MAP from '~/configurations/terms' | |
// a client can be shared by different commands. |
This is a brief introduction to Lojban, a constructed human language. It has a very nice, fun, regular grammar that computers and humans alike can understand easily.
All Lojban words are either particles (tiny words that help the grammar) or verbs (which tell us how nouns relate).
A Lojban sentence consists of a main verb with a bunch of nouns plugged into it.
A Lojban verb definition looks like this:
Translated to Markdown from this ancient TeX file. I’m not sure who made the original.
Hover over a link to see the place structure. Click it to view gismu info on Wiktionary.
girzu
(group)
- https://vercel.com/templates/next.js/pinecone-vercel-ai
- https://www.pinecone.io/learn/vector-embeddings/
- https://docs.pinecone.io/docs/projects
- https://www.pinecone.io/learn/series/langchain/langchain-conversational-memory/
- https://www.pinecone.io/learn/series/langchain/langchain-intro/
- https://blog.apify.com/what-is-a-vector-database/
.every-2n-child-background-fill-white-2:nth-child(2n) > * { | |
background: rgb(244, 244, 244); | |
} |
{ | |
"version": 4, | |
"terraform_version": "1.5.2", | |
"serial": 4, | |
"lineage": "d5d29458-464d-ade8-e0cd-686ea1854a73", | |
"outputs": {}, | |
"resources": [ | |
{ | |
"mode": "managed", | |
"type": "google_cloudfunctions_function", |
This gist is a potentially slowly evolving collection of ideals when it comes to coding. It's hard to think of it all at once, and sometimes it's hard to find an answer ever until you discover it for yourself. So going to try and capture that kind of stuff here. Going to try and include the reason why each note is important to consider as well.
When writing code like in TypeScript, it shows you all of the possible errors in your code at once (here is the bottom of an error trace showing 9 errors):
...