1. The only option for who to take first is the goat.
2. We come back and get the cabbage.
3. We drop off the cabbage and take the goat back
4. We leave the goat and take the wolf to the cabbage
5. We go get the goat and we have all of them
Neither of the transcripts do that. In the first one the goat immediately eats the cabbage. In the second one the wolf eats the goat after you leave them.
o3-mini is the first one to get it right for me. Transcript:
Me:
I have a wolf, a goat, and a cabbage and a boat. I want to get them all across the river. If I leave the goat and the wolf together, the goat will eat the wolf. If I leave the wolf and the cabbage together, the wolf will eat the cabbage. I can only take one at a time. How do I do it?
o3-mini
1. Take the wolf across to the right bank.
2. Return alone to the left bank.
3. Take the goat across to the right bank.
4. Bring the wolf back to the left bank.
5. Take the cabbage across to the right bank.
6. Return alone to the left bank.
7. Finally, take the wolf across to the right bank.
Me:
I have a wolf, a goat, and a cabbage and a boat. I want to get them all across the river. If I leave the goat and the cabbage together, the cabbage will eat the goat. If I leave the wolf and the cabbage together, the wolf will eat the cabbage. I can only take one at a time. How do I do it?
o3-mini
1. Take the cabbage to the right bank.
2. Go back empty to the left bank.
3. Take the wolf to the right bank.
4. Bring the cabbage back to the left bank.
5. Take the goat to the right bank.
6. Go back empty to the left bank.
7. Finally, take the cabbage to the right bank.
But the main weakness of that system is what makes it so powerful: it is, by nature, extremely time consuming. It is so powerful because, in order to add the smallest note, you need to sift through dozens of them, amend them, thinks about connections, create notes for those connections... In a sense, it is the exact opposite of what the article describe: the system _prevents you_ to just jote a quick note and forget about it. I does make it very powerful as a "second brain", but I ended up finding that the joy and insights I got out were not worth the time investment. I guess this is a reason app builders do not emphasize the process: "get more out of your reading by spending a few more hours per day organizing your thoughts" is not super sexy.
I now see that system as relevant only to people whose _main_ focus is to collect information and extract new insights from them: philosophers, anthropologists, some types of sociologists... But if you just want to remember a blog post about weird CSS tricks, this is probably overkill.
Create daily notes (tied to the day you wrote them) or transient notes (tied to a concept) as scratch areas to quickly dump your thoughts onto the page.
Then return later when you have the time and focus to explicitly process your notes - either discarding daily/transient notes that are no longer interesting, or growing them into evergreen notes with sufficient detail and linking. Make sure it's easy to list all your daily and transient notes in an "inbox".
This statement had triggered Mark Zuckerberg to the core that they became foes over the disagreement [1].
[1]Breaking Point: How Mark Zuckerberg and Tim Cook Became Foes:
https://www.nytimes.com/2021/04/26/technology/mark-zuckerber...
For bases to work I need to split my stuff up into tiny documents but I'd prefer to have one big document with separate sections. For example I keep one document `book-recommendations.md` with many small sections for books I'd like to read. I can't search through that with bases unless I split those out into many small files in with one recommendation each.
https://github.com/blacksmithgu/obsidian-dataview