juped

6 ms·

1.
by juped 1mo ago
A youtube competitor is a CDN problem, i.e., business deals
2.
by juped 2mo ago
In this particular case it means the Nx ecosystem, which is a solid Numpy alternative.
3.
by juped 2mo ago
They're fairly large (larger than lowercase letters in the header text, comparable to uppercase). Glad you were able to fix it since you prefer them much larger.
4.
by juped 5mo ago
Another angry all-caps rant in an agents file (cf. "NEVER FUCKING GUESS"). As the operator of this tool which you used to delete your production database, you should at least know that angry all-caps ranting pushes the big
5.
by juped 5mo ago
I wouldn't do it this exact way either but the benefit is "having any local throwaway integration branch" vs. having none at all. You don't need to do it this exact way to have one.
6.
by juped 5mo ago
The "A" in "AGI" doesn't stand for "Apocalypse", you know. It made some sense as a goalpost when the frontier of "AI" was "a computer plays, specifically, Go really well", now that typi
7.
by juped 5mo ago
It's interesting to see the strange workflows that come from jujutsu users, as someone who works on git workflows. There's some counterproductive stuff in there from my perspective but at its core you're keeping up a throwawa
8.
by juped 5mo ago
I think you should revisit the word "just", its presence in the comment you're trying to discuss, and how it's used.
9.
by juped 5mo ago
While this is a perfectly fine policy in the space of possible policies (it's probably what I'd pick, for what it's worth) the arguments being given for it leave a bad taste in my mouth.
10.
by juped 5mo ago
You can pry my em dash—short for "Emily's dash", after the poet—from my cold dead hands.
11.
by juped 5mo ago
Just like with NFTs, this is all going to discredit the actually sensible use cases for years.
12.
by juped 5mo ago
Neither! A logistic curve is just an exponential with a carrying capacity - it is still an exponential! There is no reason to believe that AI capability, which grows logarithmically with the handwaved-resources used on it (roughly, this i
13.
by juped 5mo ago
Yeah, what you're going to get is more efficient proofs: you can do induction on one case to get results about elementary functions. Not sure where anyone's getting computational efficiency thoughts from this.
14.
by juped 5mo ago
I'm productizing the unique Git workflow work I do - this may be the last week I'm ever available for consulting engagements, so head to https://merge-base.com now if you're interested!
15.
by juped 5mo ago
Pijul is the future in some ways, but not others - it's a darcs, and I'm afraid darcsen will always be niche. Jujutsu steals it, though! You should probably give it a look.
16.
by juped 5mo ago
Why would you put a second, jankier API in front of your API when you could just use the API?
17.
by juped 5mo ago
No. The cases where bisect fails you are, basically, ones where it lands on a merge that does too much - you now have to manually disentangle the side that did too much to find out exactly what interaction caused the regression. But this is
18.
by juped 5mo ago
Somewhat Linux-like. You could probably improve it purely from a git perspective by letting subtask dependencies be many-to-many (the commit graph is a dependency graph), but what you have is probably best for your whole Jira workflow.
19.
by juped 5mo ago
I agree. I set merge.ff = false and alias ff to merge --ff-only. I don't use pull but I do have pull.ff = only set, just in case someday I do. The graph log and the first-parent log serve different purposes and possibly shouldn't
20.
by juped 6mo ago
It's like switching to jujutsu gives people some kind of mental permission to do this - jujutsu justifies its existence just by that alone, really.
21.
by juped 6mo ago
Even even worse, angry all-caps shouting will make it more stupid, because it pushes you into a significantly stupider vector subspace full of angry all-caps shouting. The only thing that can possibly save you then is if you land in the eve
22.
by juped 6mo ago
No, you can do it on all the major providers for either no or low cost.
23.
by juped 6mo ago
Many people use it like this - this is playing to its strengths, rather than trying to work around its weaknesses. "What's the idiomatic X language way to do Y?" gets you a solid, useful answer in seconds. But it's just
24.
by juped 6mo ago
>Cornell, for example, had a limited capacity to pay software developers to maintain and upgrade the site, which still has a very no-frills look and feel. arXiv is doomed. It was nice while it lasted.
25.
by juped 7mo ago
Tools eat up so much context space, too. By contrast the shell tool is trained into Claude.
26.
by juped 7mo ago
It's the best starting point in many ways!
27.
by juped 7mo ago
Now this is a definite human comment, shoehorned in xkcd links are a huge human tell.
28.
by juped 7mo ago
It's very unclear to me why AI companies are so focused on using LLMs for things they struggle with rather than what they're actually good at; are they really just all Singularitarians?
29.
by juped 8mo ago
I'm baffled that people, unknown to me, have apparently been considering Claude Code, the program, some kind of "secret sauce". It's a tool harness. Claude could one-shot write it for you, lol.
30.
by juped 9mo ago
No, the Japanese imperial calendar oddness is that it's otherwise exactly the Gregorian calendar, but the era may change midyear.

More ›