Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kloud
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
1.
▲
by
kloud
6d ago
The problem is there is no good metric to describe code quality, it cannot be RLd and that's likely why latest models have such problems with slop. It is great to raise the conversation so that labs focus on this more. Picking specific
2.
▲
by
kloud
2mo ago
GitHub is really two separate products: a code forge for teams and a social coding platform to collaborate on open source. When I use the social platform, it is mostly as a read-only website. I am occasionally commenting, opening issues, PR
3.
▲
by
kloud
2mo ago
This is quite puzzling. Back in the day I saw the breakthrough with Opus 4.5, and since then was very lightweight on CLAUDE.md, trying to declare intent, rather than prescribe imperative instructions. If it was off the mark, I would see cl
4.
▲
by
kloud
2mo ago
Gotcha, yeah if a prompt does not produce the result you want, you need to add more details to it, depending on the scope it can be a lot. When it includes all sufficient details it becomes a spec.
5.
▲
by
kloud
2mo ago
You can reference other specs in a prompt. Video codecs are well specified with hundreds of pages of specs, they are probably in some form in the weights already, but you could also reference them and hash them as inputs directly to create
6.
▲
by
kloud
2mo ago
This resonates, I can imagine the development process as a cascade: we get business goals and user feedback, product is defined which can be pretty fuzzy, designers define UI, engineering works data models and tech constraints. Inputs at th
7.
▲
by
kloud
2mo ago
I agree, another issue I have with existing SDD frameworks I've seen like spec-kit or openspec, is they seem to miss the mark by coupling specification (what the software should be) and execution (how to get there). If the description
8.
▲
by
kloud
2mo ago
As a counter argument for the compiler perspective: what Cursor did is basically transpiling a project to another language, which is a form of compilation. If you distill the feedback into a spec (probably a combination of both docs and tes
9.
▲
by
kloud
2mo ago
Specs might become one solution for coping with the need to review increased volume of code. A spec is a higher level of abstraction than code, which is a higher level of abstraction than machine code. The industry made the transition to hi
10.
▲
by
kloud
3mo ago
Would be interesting to see coding performance on SWE benchmarks.
11.
▲
by
kloud
3mo ago
Fusion of frontier models beating Fable, or cheaper models matching Fable performance at half the cost. Great announcement timing. What is missing in the article is the reasoning/effort levels, so it is not ruled out the results differ
12.
▲
by
kloud
4mo ago
Fair point, given it is more unconventional design, it is a riskier way in order to get something that works.
13.
▲
by
kloud
4mo ago
Cool project, I like the idea of having tmux-compatible CLI. I used Zellij to get better UX, but many agent tools integrate with tmux. This way agent tools can still integrate tmux as a defacto standard for programmatic interface while havi
14.
▲
by
kloud
7mo ago
Reviewing large volume of code is a problem. In the pre-LLM era, as a workaround to occasionally review large PRs, I used to checkout the PR, reset commits, and stage code as I would review. In the first pass I would stage the trivial chang
15.
▲
by
kloud
7mo ago
Exactly this, existing code review tools became insufficient with the increase of volume of code, I would like to see more innovation here. One idea that comes to mind to make review easier would be to re-create commits following Kent Beck&
16.
▲
by
kloud
8mo ago
Good to know, that makes it even better. I still find Opus 4.5 to be the best model currently. But if next generation of GPT/Gemini close the gap that will cross the inflection point for me and make 3rd party harnesses viable. Or if th
17.
▲
by
kloud
8mo ago
The OpenClaw/pi-agent situation seems similar to ollama/llama-cpp, where the former gets all the hype, while the latter is actually the more impressive part. This is great work, I am looking forward how it evolves in the future. S
18.
▲
by
kloud
8mo ago
This is awesome! I was thinking it would be neat to have something like abduco but on a more reliable foundation, like libghostty-vt. For my agent management scripts I use zellij since it is more ergonomic than tmux. Abduco sounded good in
19.
▲
by
kloud
10mo ago
Great thought provoking article! Indeed, typing commands on the command line feels primitive like typing code into interactive interpreters (python, irb, etc.). Those are primitive REPLs. With lisp REPLs one types in the IDE/editor hav
20.
▲
by
kloud
11mo ago
Also in the context of LLMs I think model weights themselves could be considered an untrusted input, because who knows what was in the training dataset. Even an innocent looking prompt could potentially trigger a harmful outcome. In that re
21.
▲
by
kloud
11mo ago
Non-determinism is just a limitation of current implementations, but it is not a fundamental property: https://thinkingmachines.ai/blog/defeating-nondeterminism-in...
22.
▲
by
kloud
11mo ago
The strength of Lisps is in ability to define DSLs and then concisely express solutions for problems in that domain. Arguably no other programming language was able to exceed or even match that power until now. The math behind transformers
23.
▲
by
kloud
11mo ago
That linear trend line does not seem to fit very well, I say we are looking at the beginning of a hockey stick :) Stopped dual-booting for games and formatted the partition some time after Windows 7 EOL. Thank you Wine contributors, Valve a
24.
▲
by
kloud
11mo ago
> It seems to me that LISP will probably be superseded for many purposes by a language that does to LISP what LISP does to machine language. Namely it will be a higher level language than LISP that, like LISP and machine language, can re
25.
▲
by
kloud
11mo ago
Although niche, things are pretty lively in the community. Among other things this year great progress was made on Jank, the native LLVM-based implementation with seamless low-level C++ interop. As part of that work a test suite is being cr
26.
▲
by
kloud
11mo ago
That sounds super cool, let me add another voice of encouragement, please do publish it.
27.
▲
by
kloud
11mo ago
Great work! I was just thinking the other day how an interface like this would be useful, it seems strange we don't see more UI attempts beyond basic linear chat. I find most need for managing context for problem solving. I describe a
28.
▲
Code Tours as Code
(dundalek.com)
2 points
by
kloud
11mo ago
|
0 comments
29.
▲
by
kloud
1y ago
Very cool! I created something similar for Casio F-91W. It also uses XState. The benefit of specifying a machine in XState, is that one can embed Stately editor to visualize the states and their transitions. https://github.com&#x
30.
▲
by
kloud
1y ago
When a complex system cannot be meaningfully reduced, another approach might be trying to reduce scope. Current areas include managing services on a server, managing a single-user laptop, and enterprise features for fleet of devices/us
More ›