adelks

5 ms·

1.
by adelks 10d ago
"In Clojure this is fairly straightforward" Somehow when things get complex, I could never find fully functional style to be more understandable than imperative
2.
by adelks 10d ago
"In Clojure this is straightforward"
3.
by adelks 1mo ago
Very nice article. I agree with it, call it taste, call it judgment, call it quality, I want things done the way I see as satisfactory, and it requires me to make LLMs do things differently several times. Like exploring a tree with a heuris
4.
by adelks 4mo ago
"A sufficiently precise spec is code". I've read somewhere here before. So guardrails, i.e. sufficiently precise spec and tests, will need to be as strict as the LLM is bad at getting the right context and asking back the rig
5.
by adelks 4mo ago
I know this tool was meant for AI, but I am more interested in using it myself when exploring new code bases or even my own, when I want to refactor something and want an overview of where to change stuff. LSPs do that, but this tool sounds
6.
by adelks 5mo ago
My current understanding is that regular consumer GPUs are very much capable if they had enough VRAM, and buying like 2 isn't out of this world. A 64GB consumer GPU not existing has no technical nor financial (buyer side) reason to it,
7.
Hyperscalers are buying all the chips to then rent them to us later
7 points by adelks 5mo ago|4 comments
8.
by adelks 5mo ago
How about simply making the website an app and have it load your makedown file with a button and file browser. Just like e.g. https://app.diagrams.net/ And I believe you can then tell the browser that you need no network co
9.
by adelks 6mo ago
There's another markdown spec that's better mystmd.org
10.
by adelks 6mo ago
Indeed.