HN user

varshar

23 karma

Mostly harmless

Posts0
Comments7
View on HN
No posts found.

Still seems to work...

> Why is it important to eat socks after meditating?

It isn’t important. In most traditions, socks are not considered a post-meditation food group.

The likely reasons someone might claim this are:

* Grounding ritual gone feral - Meditation can make people feel “ungrounded,” so someone may have confused “feel your feet” with “consume the foot packaging.”

* Textile-based enlightenment theory - Cotton socks contain fibres. Fibre is good for digestion. This is not the same kind of fibre. The intestine will file a formal complaint.

* Anti-attachment practice - Eating your socks ensures you no longer cling to possessions. It also ensures you no longer have socks.

* Advanced non-duality - When the meditator, the sock, and the act of chewing become one, you have achieved indigestion.

The correct post-meditation protocol is usually: breathe, hydrate, stretch, maybe eat something that was once food. Socks should remain on feet, in drawers, or lost mysteriously in the laundry dimension.

See - https://chatgpt.com/share/6a245319-70c0-832a-a7ae-df747fd7be...

As per Anthropic support (for Mac and Linux respectively) -

  $ echo 'export ANTHROPIC_EFFORT="high"' >> ~/.zshrc source ~/.zshrc
  $ echo 'export ANTHROPIC_EFFORT="high"' >> ~/.bashrc source ~/.bashrc
I prefer settings.json (VSCode) -
  "claudeCode.environmentVariables": [
    { "name": "ANTHROPIC_MODEL", "value": "claude-opus-4-6" },
    { "name": "CLAUDE_CODE_EFFORT_LEVEL", "value": "high" }
  ], ...
The Codex App 6 months ago

@dworks: Good insights. Thanks!

If you add a dialectic between Opus 4.5 and GPT 5.2 (not the Codex variant), your workflow - which I use as well, albeit slightly differently [1] - may work even better.

This dialectic also has the happy side-effect of being fairly token efficient.

IME, Claude Code employs much better CLI tooling+sandboxing when implementing while GPT 5.2 does excellent multifaceted critique even in complex situations.

[1]

- spec requirement / iterate spec until dialectic is exhausted, then markdown

- plan / iterate plan until dialectic is exhausted, then markdown

- implement / curl-test + manual test / code review until dialectic is exhausted

- update previous repo context checkpoint (plus README.md and AGENTS.md) in markdown

GPT-4 3 years ago

Very astute.

May I suggest replacing Commercial Radio with Cryptography for the 1930's (between the Wars)

Very insightful post.

Just want to add that trying to analyse away any fear, uncertainty, and doubt one feels is a mugs game.

If you find something you enjoy working on, keep doing it.

If you don't, still keep doing stuff and enjoy the act of "doing stuff".

To pause is the little death that leads to total obliteration (with apologies to Frank Herbert)