6gvONxR4sf7o

36 ms·

1.
by 6gvONxR4sf7o 5d ago
I'd bet that it needs a better abstraction like LSP. IDEs are super expensive to build, so an IDE company isn't going to try to abstract away their business, so it's a long time between LSP-like developments, and I can imagin
2.
by 6gvONxR4sf7o 5d ago
I'd bet it depends on what they write to the LLM, since sycophancy is so strong in these things. If they write in a fairly agnostic way, it might default to sycophancy to you the dev, while if they write it in an opinionated way it mig
3.
by 6gvONxR4sf7o 8d ago
Is this the future we're headed towards? Where I'll be afraid to use google docs in case Google identifies value in whatever I'm writing about and snipes it if it my docs make it into the next round of model training?
4.
by 6gvONxR4sf7o 10d ago
> Automated AI research is a more dramatic form of scaling intelligence with compute; and of course as a part of it, AI will improve the computational substrate itself . And similarly to scaling, we focus OpenAI research towards RSI as w
5.
by 6gvONxR4sf7o 13d ago
So, probably most aligned as measured by the metrics that are the least reliable on it.
6.
by 6gvONxR4sf7o 27d ago
If we add types or a geometric abstract manifold or something, the issue is that we do want cos and sin to take numbers with a scale (e.g. cos(90 degrees) vs cos pi/2 rads), but we generally don't give the same thing to e or ex
7.
by 6gvONxR4sf7o 27d ago
Why not e^{2 pi i x} = cos x + i sin x then? We already handle e^{2 pi/360 i x} = cos x + i sin x for x in degrees just fine. It's not that euler no longer holds, it's that you just have to be clear about what units[0] you us
8.
by 6gvONxR4sf7o 1mo ago
Seems to be Altman's playbook, just like how he got the CEO job back.
9.
by 6gvONxR4sf7o 2mo ago
Huh, I wasn't actually going for snark. I was trying to preemptively be over-specific about what I meant. As in, you said "... writing the correct program..." and I meant that I'm talking in terms where functions are equ
10.
by 6gvONxR4sf7o 2mo ago
> Congrats, that sounds at least as hard as writing the correct program in most cases. That's not remotely true. Or, more formally speaking since we're in a thread about proof assistants, it's not remotely true, up to exte
11.
by 6gvONxR4sf7o 2mo ago
I wonder how the "added value" argument can apply to Anthropic and not to the Kimi team. If Claude's value is that you don't have to pay a team of slow expensive subject-matter experts, and Kimi's value is that you
12.
by 6gvONxR4sf7o 3mo ago
Oh man, that resonates with me. One of the constant frustrations for me was that once you get foundations in a topic, the rest follows, but the foundations are often full of things that are axioms under one metatheory and theorems under ano
13.
by 6gvONxR4sf7o 3mo ago
One piece of this that could be really nice in a normal language is if an LLM could generate a decent syntax highlighter or code-folding-spec or something for each "aspect." The idea of tooling to help us focus on one piece at a t
14.
by 6gvONxR4sf7o 3mo ago
My point wasn’t about risk vs reward, or in their words “harm” vs reward. It’s about how increasing the opportunity for reward increases the justifiable harm. “X is bad (unless it makes me rich).” I guess it’s the fact that Anthropic usuall
15.
by 6gvONxR4sf7o 4mo ago
The framing they use is hilarious and their little graphic is perfect. The risk of harm doesn't go down, but the reward goes up, so the harm just becomes the cost of doing business, justified by the reward. So as the reward gets higher
16.
by 6gvONxR4sf7o 4mo ago
Another view of the accountability is that we're currently often pointing accountability in the wrong direction, and it's gaining momentum. Aspects of it have been around so long it's a trope: important work around maintainab
17.
by 6gvONxR4sf7o 5mo ago
Why just the $10k? Could you get a full refund? If I order a $12 burrito and you give me a $10 sandwich, I would feel owed my $12 back, not the $2 difference in price.
18.
by 6gvONxR4sf7o 7mo ago
I don't mourn coding for itself, since I've always kinda disliked that side of my work (numerical software, largely). What I do mourn is the reliability. We're in this weird limbo where it's like rolling a die for every
19.
by 6gvONxR4sf7o 8mo ago
plan -> code -> verify is nice in theory, but is super failure prone without the TDD or “preregistration” version: plan -> code verification -> code implementation -> verify. Doing the verification after the execution tends t
20.
by 6gvONxR4sf7o 8mo ago
If they just remade it with modern AF software , I'd probably carry mine around most every I went. Not to mention what they could do by updating hardware.
21.
by 6gvONxR4sf7o 9mo ago
So is the "bitter lesson" that fuzzy overlords will be practically preferable to hand coded legislation?
22.
by 6gvONxR4sf7o 9mo ago
How's that account for language drift over centuries?
23.
by 6gvONxR4sf7o 9mo ago
I have a potentially more optimistic (and simultaneously more pessimistic!) view to offer. Some differing interpretations of the law distinguish between the lawmakers' intention vs the literal meaning (and keep in mind that language it
24.
by 6gvONxR4sf7o 11mo ago
10 days later... sorry, I didn't see your comment. The example I gave had a few pieces: - x is defined prior to the if/else, and overwritten in just one branch - y is defined in both branches So in the rest of the function, we hav
25.
by 6gvONxR4sf7o 11mo ago
As always, labor is a marketplace, and the supply side boils down to a) how much the next person else is willing to work (all else equal), and b) external forces (like overtime requirements kicking in at 40 hours).
26.
by 6gvONxR4sf7o 11mo ago
OCR for printed documents is super robust, but handwriting, low res, and aligned recognition (not just image to "hello world" but also having "h is here in space e is here in space...) are all still well behind "basicall
27.
by 6gvONxR4sf7o 11mo ago
There's more to this that I'd absolutely love to see in a language, and I can't tell if rye supports. If you want an ergonomic `if` you need its scope aspects too. Consider this example <beginning of the function>
28.
by 6gvONxR4sf7o 1y ago
Mercury is one of those languages that seems to support so many different styles of programming in a nicely unified way, I've always been curious about it. This is so much more readable than I remember any of the Mercury docs being. Wo
29.
by 6gvONxR4sf7o 1y ago
> Not particularly, no. What I want is for you to purchase the seats your family needs ahead of time, not ask me for them for free. What happened to "if you want it, then you have to pay for the privilege?" If you want to be su
30.
by 6gvONxR4sf7o 1y ago
Of course, the challenge is that the next question after solving a leetcode problem is often to explain and optimize the performance characteristics, which in prolog can get stupidly hairy.

More ›