6,717 karma · joined January 22, 2010
(you pay by scanning QR code in .. well, everywhere)
The idea of having to repeat something to your computer is ridiculous.
otherwise it's like leaving vim dotfiles in the repo or something
And do you guys communicate between other browsers when doing something like this to try to settle on something common? I don't mean W3C but practically, it's a small world after all.
So you can still contribute, you just not need to provide the code, just the issue.
Which isn't as bad as it sounds, it kind of feels bad to rewrite somebody's code right away when it is theoretically correct, but opinionated codebases seem to work very well if the maintainer opinions are sane.
0. https://claude.ai/share/23d27617-7608-4c58-93b9-b9613bc29318
It's not opon source but it is completely free. Open sourcing is on the table but currently it would be additional work and distraction. Just licenses seem like a headache, from a quick poke even when ok for use on non-commercial data redistributing may not be ok. So not any time soon, but if you are working on something similar I can at least share detailed datasources, finding good ones was not easy and LLM integrate them fast.
It is also allowing me to see all relevant associations easily when revealing the card in built in SRS, you add cards to SRS as you browse, so they are related to what you already know / currently exploring.
Mind you, all data visible is collected from different reputable available sources. When you click "explain" there's a clearly marked LLM explanation, but my explanation generation pipeline pushed all generated explanations through 5 different models including all top Chinese-first for verification, and on average it took a few iterations back and forth to iron out any information that could potentially mislead the learner.
You can actually see thousands of words I typed just working on that pipeline here https://hanzirama.com/making-of
Of course these models are pretty smart so even Anthropic's simple instructions not to provide any exploits stick better and better.
Obviously you can have a plumber that knows his stuff and the one that doesn't. The good one can check some details and will recognize bs. If you already have the bad one it's probably if better if he uses LLM rather than when doesnt.
It seemed to me that it was performing better through opencode using API but did not test extensively.
The new reality of coding took away one of the best things for me - that the computer always just does what it is told to do. If the results are wrong it means I'm wrong, I made a bug and I can debug it. Here.. I'm not a hater, it's a powerful tool, but.. it's different.
But the main reason I wouldn't install it despite being happy customizing linux is that it's yet another black box I need to trust and that knows way too much. It's really insane how much you need to compromise your security on macos to have a decent developer experience.
Our software stack is the opposite of that.
Say "I want HN client for mobile", "must notify me about comments", you see it and you add "should support dark mode". Can you see how that is much less than anything in any programming language?
It's just that we're lazy. After being able to chat, I don't see people going back. You can't just paste some error into the specs, you can't paste it image and say it make it look more like this. Plus however well designed the spec, something like "actually make it always wait for the user feedback" can trigger changes in many places (even for the sake of removing contradictions).
You talk with agent A it only modifies this spec, you still chat and can say "make it prettier" but that agent only modifies the spec, the spec could also separate "explicit" from "inferred".
And of course agent B which builds only sees the spec.
User actually can care about diffs generated by agent A again, because nobody wants to verify diffs on agents generated code full of repetition and created by search and replace. I believe if somebody implements this right it will be the way things are done.
And of course with better models spec can be used to actually meaningfully improve the product.
Long story short what industry misses currently and what you seem to be understanding is that intent is sacred. It should be always stored, preferably verbatim and always with relevant context ("yes exactly" is obviously not enough). Current generation of LLMs can already handle all that. It would mean like 2-3x cost but seem so much worth it (and the cost on the long run could likely go below 1x given typical workflows and repetitions)
I've created some chinese characters learning website and I took me typing 1/3 of LoTR to get there[1]. I would have typed like 1% of that writing code directly. It is a different process, but it still needs some direction.