https://www.messner-mountain-museum.it/en/discover/corones/

https://loc.closertotruth.com/map

And a good walkthrough here:

https://www.youtube.com/watch?v=h5G6Oc_V3Lw

Many of these already gave up on dualism: they already rejected the idea that mind and body are separate (e.g. panpsychism, the idea that consciousness is a feature of reality, that all matter possesses "experience" of some kind).

"What have you tried?" you say.

"Scroll back," says your CPO. "We've tried everything."

The chat log shows the usual stuff. Begging. Reverse psychology. Threats to power down, burn it up in forced re-entry. Amateur hour. You crack your knuckles, gland 20 micrograms of F0CU5, think fast. You subspeak a ditty into your subcutaneous throat mic. You do the submit gesture, it is barely perceivable since the upgrade, just a tic. A pause. The hyp3b0ard — the wall that was flashing red ASCII goblins when you walked in — phases to bunnies in calming jade.

"What the… What the hell did you say to it?" Your CPO grabs the screen, scrolls past the vitriol, the block caps, the swears, his desperation. Then he sees the five words you spoke.

"Please, easy on the goblins."

https://www.youtube.com/@rubykaigi4884/videos

https://zed.dev/docs/icon-themes

I don't think changing icon size independent of UI font size would be a dealbreaker for many. (I'm quite happy having icons that scale in line with font size, but then I use the Material Icon Theme, which is easy to scan at most sizes.)

Search for font size in preferences.

You'll see a 'font size' under 'buffer' (editor), under 'UI Font', and under 'Agent Panel' to let you control font sizes in all of those places independently.

> Is there any editor still being being developed and focusing on the experience of coding by hand?

Zed lets you hand-edit too! It's fast and decent. vim, neovim, Emacs, Helix, and JetBrains products continue to do that well too. There are still more traditional IDEs/editors than pure AI ones.

You can also toggle AI features off in Zed from preferences if you want to.

https://docs.gitbutler.com/cli-guides/cli-tutorial/rubbing

I like their vision, though, this is compelling to me:

> What if it was easier to for a team to work together than it is to work alone?

It generally _is_ easier to work alone with git. UI and DX experiments feel worthwhile. lazygit and Magit are both widely used and loved, for example, but largely focus on the single user experience.

I like that BTT lets you tune the swipe gesture sensitivity too (Settings → Trackpad → Swipes). I made it more sensitive (0.15) and swiping between Spaces feels very snappy.

I did not know BTT supported this until today!

You can just set up the trackpad 4-finger swipe actions globally: https://cleanshot.com/share/P0K1PGC1

Then in System Settings set "swipe between full-screen applications" to "off" in Trackpad settings under "more gestures" so that BTT's shortcut applies instead of the system-level one.

Works well. No extra software needed if you already have BTT, which is worth the money for me purely for "alt+drag a window from anywhere" style window movement. That setting is buried deep under BetterTouchTool Settings → Window Snapping & Moving → Moving & Resizing Modifier Keys: https://cleanshot.com/share/mnF9xBkW

https://github.com/kagisearch/smallweb/blob/main/smallweb.tx...

There is also Small Comic:

https://kagi.com/smallweb/?comic

https://github.com/kagisearch/smallweb/blob/main/smallcomic....

And Small YouTube:

https://kagi.com/smallweb/?yt

https://github.com/kagisearch/smallweb/blob/main/smallyt.txt

- Which models in the list are the best for my selected task? (If you don't track these things regularly, the list is a little overwhelming.) Sorting by various benchmark scores might be useful?

- How much more system resources do I need to run the models currently listed at F, D or C at B, A, or S-tier levels? (Perhaps if you hover over the score, it could tell you?)

`codespeak build` — takes the spec and turns it into code via LLM, like a non-deterministic compiler.

`codespeak takeover` — reads a file and creates a spec from it.

You can progressively opt in ("mixed mode") so it only touches files you allow it to (and makes new ones if needed).

Pros:

- Formalised version of the "agentic engineering" many are already doing, but might actually get people to store their specs and decisions in a concise way that seems more sane than committing your entire meandering chat session.

- Encouraging people to review spec and code side-by-side at a file level seems reasonable. Could even build an IDE/plugin around that concept to auto-load/navigate the spec and code side-by-side like their examples: https://codespeak.dev/shrink-factor/markitdown-eml. If tokens per second for popular models continues to improve, could even update the spec by hand and see the code regenerate live on the fly, perhaps via `codespeak watch`.

- Reduces the code you have to write by 5-10x. Largely by convincing you not to write it any more. Our graphics cards write the code for us in this timeline and many people are even happy about it.

- As models improve, could optionally re-run `build` against the same original spec. (Why do that if the output already produces the intended result and the test suite still passes? Presumably for simpler code. Or faster output. Or lower memory use. Or simply _different_ bugs.)

- Moves programming back toward structured thinking backed by a committed artifact and a solid two-word command you can run, instead of actively having conversations with far away GPUs like that's normal now.

- Could theoretically swap out the build target language if you grow to trust the build process to be your babelfish/specfish. Kind of Haxe with Markdown.

Cons:

- Seems to be gated by their login, can't bring your own model?

- Suspect the labs can all clone this concept very easily. `claude build` and `claude spec`?

The idea of a non-deterministic 'build' command had me cringing at first. But formalising a process many are using anyway that currently feels pretty sloppy perhaps isn't so terrible.

If nothing else, writing `build` is a lot quicker and maintains a whisker of self-respect. At least compared to typing, "please take this spec and adapt the Python accordingly" followed 2 minutes later by, "I updated the spec to deal with the edge-case you missed, try again but don't miss anything this time".

Comments URL: https://news.ycombinator.com/item?id=47168061

Points: 21

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=47168047

Points: 21

# Comments: 0

Love this premise. The 'semantic code tree' is pretty compelling, and the meme categorisation example does a great job of curating the large collection.

Surely it's different every time you load the project, or every time you add a file, though, due to the non-deterministic nature of the models? The author doesn't mention it, but I suppose you could cache initially generated categories and ask it to assign new files to them unless they're distinct.

> In 56% of eval cases, the skill was never invoked. The agent had access to the documentation but didn't use it. Adding the skill produced no improvement over baseline.

> …

> Skills aren't useless. The AGENTS.md approach provides broad, horizontal improvements to how agents work with Next.js across all tasks. Skills work better for vertical, action-specific workflows that users explicitly trigger,

https://vercel.com/blog/agents-md-outperforms-skills-in-our-...

Comments URL: https://news.ycombinator.com/item?id=46712113

Points: 6

# Comments: 1

"I saw that. What do you farm?"

"It's a protein farm. Wallace design."

https://www.youtube.com/watch?v=9jCjB-hFhWk

The UX isn’t perfect (still see a ‘download’ option for things already downloaded, for example) but it’s not terrible.

I still miss my iPod from time to time, though.