263 karma · joined April 17, 2015
I was losing my sanity over all the refusals (app refusing the photos).
I think it is a very common practice. Everyone will be forgotten eventually, no matter the fame.
https://cs.wikipedia.org/wiki/Tyr%C5%A1%C5%AFv_sad_(Brno-Vev...
Also they cache food they don't eat, they hide it, cover with leaves and make sure nobody is watching them, they act very casual. I am not sure if they remember the locations though.
Compared to ravens they have smaller head but I believe it is because they spend so much time near people (at least here in Europe you don't see ravens in cities, they are afraid,for historical reasons, of people and low in numbers) they get smarter and more crafty.
I can recommend a great book about corvids with beautiful illustrations: https://yalebooks.yale.edu/book/9780300122558/in-the-company...
⎿ API Error: 400 messages.1.content.17: `thinking` or `redacted_thinking` blocks in the latest assistant message cannot be modified. These blocks must remain as they were in the original response.
From /code-review max.
Example: https://github.com/rkuska/carn/blob/main/VOCABULARY.md
``` # Development Workflow
*Always use `bun`, not `npm`.*
# 1. Make changes
# 2. Typecheck (fast)
bun run typecheck
# 3. Run tests
bun run test -- -t "test name" # Single suite bun run test:file -- "glob" # Specific files
# 4. Lint before committing
bun run lint:file -- "file1.ts" bun run lint
# 5. Before creating PR
bun run lint:claude && bun run test ```
I have these things in pre-commit, this way the targets are always ran and the agent is forced to fix them (I ask claude to commit changes). The agents are erratic and very often skip these steps. Anything that can be deterministic I keep as scripts.
Regarding commits; both codex and claude are terrible at writing them. I have in my user CLAUDE.md:
``` Pattern: `type(scope): message` where type is `fix`, `feat`, `chore`, `docs`, `refactor`, or `style`; scope marks what is affected; message is a short lowercased description.
Keep subject and body lines under 72 characters. Always write a body explaining what, how, and why in continuous human-readable text. For fixes include the error message being fixed. No first-person speech. Re-read the actual git diff before writing — the message must describe what changed, not what was planned.
Use following command to create commit:
```bash git commit -F - <<'EOF' type(scope): subject line
Body paragraph explaining what, how, and why. EOF ```
```
Without it would write the body as a single long sentence; when asked to fix lines it would just insert \n (newlines), which were not respected and were instead just rendered as characters.
Another thing I find helpful is VOCABULARY.md. Very often the agent would assume (connect?) a different thing than what I had in mind, with VOCABULARY I make sure when I say "thing" claude and I have both the same "understading" (connection?) what "thing" is.
`claude --thinking-display summarized`
The thinking is then visible with ctrl+o in the claude cli (shortcut available at least on mac).
Well you can't really trust the documentation I guess. I can't edit my original comment anymore.
> Claude Opus 4.7 (claude-opus-4-7), adaptive thinking is the only supported thinking mode. Thinking is off unless you explicitly set thinking: {type: "adaptive"} in your request; manual thinking: {type: "enabled"} is rejected with a 400 error.
https://platform.claude.com/docs/en/build-with-claude/adapti...
For my claude code I went with following config:
* /effort xhigh (in the terminal cli) - To avoid lazying
* "env": {"CLAUDE_CODE_DISABLE_1M_CONTEXT": "1"} (settings.json) - It seems like opus is just worse with larger context
* "display": "summarized" (settings.json) - To bring back summaries.
* "showThinkingSummaries": true (settings.json) - Should show extended thinking summaries in interactive sessions
Freaking wizardry.
https://www.muzeumprahy.cz/en/visit-langweils-model-of-pragu...
> Like I said, America's a third world country as it is and... and we're just basically in a hopeless situation as it stands
https://www.youtube.com/watch?v=pP8XBJc2p_g
I keep GY!BE playing on repeat for the past several months.
I don’t have an X account and as such might miss additional information from subsequent replies but there is nowhere in the post mention about building a high growth/high revenue business? Maybe Andrej just enjoy teaching and sharing knowledge and want to bring like minded, well off people together rather than creating an unicorn?
Or do you mean by your post that it is not (or is very hard) to even reach non negative revenue to keep it sustainable on its own?
I switched to 24-200 during workshop with Pinkhassov as he is a strong proponent of superzooms.