Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dnautics
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
22 ms
·
511.
▲
by
dnautics
8mo ago
jira/trello: ergonomics. to set them up correctly exactly the way i want would take me 20 hours (or hire a PM), i can vibecode for 20h and get the same result. plus, being able to crossref internal data types is chef's kiss. i
512.
▲
by
dnautics
8mo ago
you cant easily vibecode everything . in my startup this is what I am not buying (and vibecoding): - JIRA/trello/monday.com - benchling - obsidian this is what i buy and have no intent to replace: - carta - docusign - gusto/
513.
▲
by
dnautics
8mo ago
Honestly claude doesn't typically do this the way you think. It's perfectly capable of working in files that are "way too big for its allowed download window". But in general you want some amount of context (what functi
514.
▲
by
dnautics
8mo ago
Where would it inject the code?
515.
▲
by
dnautics
8mo ago
Ok fine but never here have I not been talking specifically about C
516.
▲
by
dnautics
8mo ago
> The kinds of mistakes AI makes are very different. I think that's a bit extreme. If a programming language has good ergonomics for a short attention span human, it will likely be better for an LLM too. However, to make good predic
517.
▲
by
dnautics
8mo ago
A+B > A+C => B > C
518.
▲
by
dnautics
8mo ago
It's a thing in c. foo * bar; Is that multiplication? Or a declaration of type foo*?
519.
▲
by
dnautics
8mo ago
Reading files is not that input tokien heavy, I suspect. But anyways I omitted it because presumably it would have done so to gain local context in general.
520.
▲
by
dnautics
8mo ago
No problem. It's an SLM, I have a dedicated on-prem GPU server that I deploy behind tailscale for inference. For training, I reach out to lambdalabs and just get a beefy GPU for a few hours for the cost of a Starbucks coffee.
521.
▲
by
dnautics
8mo ago
I think we need a LLM equivalent of this part's of fitt's law: The fastest place to click under a cursor is the location of the cursor. For an LLM the least context-expensive feedback is no feedback at all, the LLM should be able
522.
▲
by
dnautics
8mo ago
why? I suspect that writing code itself is extremely token efficient (unless like your keywords happen to be silly, super-long alien text). Like which do you think is more token-efficient? 1) <tool-call write_code "my_functi
523.
▲
by
dnautics
8mo ago
in the era of LLMs, syntax might matter more than you think. The c form of `type name;` is ambiguous because it could actually be more than one thing depending on context. Even worse if you include macro sheananigans. The alternate (~rust
524.
▲
by
dnautics
8mo ago
Here are my thoughts: https://m.youtube.com/watch?v=YZa5GqrZeao
525.
▲
by
dnautics
8mo ago
Think about fitts law: the fastest place to click under a cursor is the location of the cursor. For an LLM the least context-expensive feedback is no feedback at all. I think codebases that are strongly typed sometimes have bad habits tha
526.
▲
by
dnautics
8mo ago
> Succinctness, functionality and popularity of the language are now much more important factors. No. I would argue that popularity per se is irrelevant: if there are a billion examples of crap code, the LLMs learn crap code. conver
527.
▲
by
dnautics
8mo ago
Don't assume. Empirically, they are not. (This post Feb 2026 may change in future yadda yadda) See: autocodebench https://github.com/Tencent-Hunyuan/AutoCodeBenchmark/tree/ma...
528.
▲
by
dnautics
8mo ago
I don't think LLMs benefit from having code properly typed (at the call definition). It's costly to have to check a possibly remote file to check. The LLM should be able to intuit what the types are at the callsite and elixir
529.
▲
by
dnautics
8mo ago
It's 2026 and the LLMs score high on elixir, just write it in python and patch it over to elixir gradually
530.
▲
by
dnautics
8mo ago
I have one vibecoded ml pipeline now and I'm strongly considering just clauding it into Nx so I can ditch the python
531.
▲
by
dnautics
8mo ago
Did you get to the end of the article?
532.
▲
by
dnautics
8mo ago
oh awesome. I thought error traces were only on debug and optionally on ReleaseSafe.
533.
▲
by
dnautics
8mo ago
Can you phrase that as a direct answer to my question? Trying to learn something here. Appreciate it!
534.
▲
by
dnautics
8mo ago
If you can statically analyze c for memory safety, why did pazlo bother building fil-C?
535.
▲
by
dnautics
8mo ago
Zig has error unions on return types which are basically a special cased (rust enum aka sum type) of the return type with a special cased (c enum aka enumerated type), and stacktraces are only available in certain build modes. A "diagn
536.
▲
by
dnautics
8mo ago
You can't really easily have useful user defined payloads in errors without implicit allocations. Best way to do it is to pass a payload pointer into the function call. You can put it into an options struct with a default null pointer
537.
▲
by
dnautics
8mo ago
You should just build your own slack for your company
538.
▲
by
dnautics
8mo ago
It will never be in the main compiler, since it was written by Claude. I think that's ok. The general concept is sound and won't break (modulo names of instructions changing etc). In fact it will get better. With the new io, c
539.
▲
by
dnautics
8mo ago
wow, what a list! all of these are statically analyzable using a slightly hacked zig compiler and a library! https://github.com/ityonemo/clr (Btw: you can't null pointer dereference in zig without using the naviga
540.
▲
by
dnautics
8mo ago
It's possible to do memory safety analysis for zig. I think you could pretty easily add a noalias checker on top of this: https://github.com/ityonemo/clr
More ›