HNHacker News
TopNewBestAskShowJobs

dcre

5,024 karma · joined January 3, 2013

https://crespo.business/
submissionscomments
dcre··on Using LLMs at Oxide
In my experience, LLMs have been quite capable of producing code I am satisfied with (though of course it depends on the context — I have much lower standards for one-off tools than long-lived apps). They are able to follow conventions already present in a codebase and produce something passable. Whereas with writing prose, I am almost never happy with the feel of what an LLM produces (worth noting that Sonnet and Opus 4.5’s prose may be moving up from disgusting to tolerable). I think of it as prose being higher-dimensional — for a given goal, often the way to express it in code is pretty obvious, and many developers would do essentially the same thing. Not so for prose.
dcre··on Authorities investigating Waymo over failure to stop for school buses
I don't think any of us would like to know how many animals were killed by human drivers in the same time period.
dcre··on Authorities investigating Waymo over failure to stop for school buses
Really weird intro about the increase in auto fatalities, for two reasons:

1) fatalities have declined a lot from their pandemic peak. It looks kind of like a reversion to trend

2) exactly none of those fatalities were caused by a Waymo, because there has never been a Waymo fatality

https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/...

dcre··on Anthropic acquires Bun
No it isn’t. That’s not an acquihire. They’re keeping the product.
dcre··on React and Remix choose different futures
I think absorbing into React Router makes more sense when you consider that a) most of Remix was just RR, and b) Remix had at most 5-10% the users that RR has[0] (probably fewer). I think the "modes" distinction[1] within React Router is easier to understand and explain than a separate framework wrapping RR.

[0]: https://npmtrends.com/@remix-run/react-vs-react-router

[1]: https://reactrouter.com/start/modes

dcre··on React and Remix choose different futures
I am excited about Remix 3 and I've been following all their work for years, but I agree about the naming — when Ryan said at React Conf 2024 that Remix wasn't going away, but just "taking a nap", they should have taken the universal confusion that ensued as a sign that they should pick a new name.
dcre··on Ghostty compiled to WASM with xterm.js API compatibility
Just want to second this. I find Zed nearly unusable due to weird rendering in the terminal.
dcre··on A Remarkable Assertion from A16Z
It is appalling writing. Given that Opus is capable of a lot better than this, it seems likely they’re prompting it to be terrible.
dcre··on Student perceptions of AI coding assistants in learning
Interesting to see quotes but note N=20 and the methodology doesn’t seem all that rigorous. I didn’t see anything that wasn’t exactly what you would expect to hear.
dcre··on Claude Opus 4.5
I do not believe it exists.
dcre··on Claude Advanced Tool Use
That sounds even worse!
dcre··on Claude Opus 4.5
People like the tab completion model in Cursor.
dcre··on Claude Advanced Tool Use
GraphQL is just a typed schema (good) with a server capable of serving any subset of the entire schema at a time (pain in the ass).
dcre··on `satisfies` is my favorite TypeScript keyword (2024)
“ReScript is a rebranding of BuckleScript and Reason”

https://v11.rescript-lang.org/docs/manual/latest/migrate-to-...

https://rescript-lang.org/blog/bucklescript-is-rebranding/

dcre··on Agent design is still hard
It is the LLMs because they have to be RLed to be good at these things.
dcre··on Agent design is still hard
One example is that there used to be a whole complex apparatus around getting models to do chain of thought reasoning, e.g., LangChain. Now that is built in as reasoning and they are heavily trained to do it. Same with structured outputs and tool calls — you used to have to do a bunch of stuff to get models to produce valid JSON in the shape you want, now it’s built in and again, they are specifically trained around it. It used to be you would have to go find all relevant context up front and give it to the model. Now agent loops can dynamically figure out what they need and make the tool calls to retrieve it. Etc etc.
dcre··on AI is a front for consolidation of resources and power
The tools have reached the point where no special knowledge is required to get started. You can get going in 5 minutes. Try Claude Code with an API key (no subscription required). Run it in the terminal in a repo and ask how something works. Then ask it to make a straightforward but tedious change. Etc.
dcre··on Open-source Zig book
I suspect most developers do not know C.
dcre··on Structured outputs on the Claude Developer Platform
For the TS devs, Zod introduced a new toJSONSchema() method in v4 that makes this very easy.

https://zod.dev/json-schema

dcre··on Cursor: Past, Present, and Future
This article claimed they had single-digit monthly cash burn in August, when they had over $500M ARR (so let's say $41M monthly) and 150 employees. If that is true, they are spending way less than 200% of revenue.

"Anysphere runs pretty lean with around 150 employees and has a single digit monthly cash burn, a source tells me."

https://www.newcomer.co/p/cursors-popularity-has-come-at-a

dcre··on Dependent types and how to get rid of them
I asked GPT-5 about it before writing the above comment and got a pretty interesting answer about how, for example, you can’t write a function that takes a number as an argument and returns an array of that length (length enforced by the type system). You can partly get there with tuple types but you have to enumerate every length explicitly. And it only works if you pass a number literal to the function. If you pass a variable of type number, it can’t infer the particular number it is.
dcre··on Dependent types and how to get rid of them
This made me realize TypeScript’s conditional types are closer to dependent types than I thought.
dcre··on Kimi K2 Thinking, a SOTA open-source trillion-parameter reasoning model
The question is: fine-tuning for what? Reasoning is not a particular task, it is a general-purpose technique for directing more compute at any task.
dcre··on New gel restores dental enamel and could revolutionise tooth repair
Note the recent spate of 1 star reviews angry that what they received is not the Novamin version.
dcre··on How I use every Claude Code feature
"It shifts us from a “per-seat” license to “usage-based” pricing, which is a much better model for how we work. It accounts for the massive variance in developer usage (We’ve seen 1:100x differences between engineers)."

This is how we are doing it too, for the same reasons. For now, much easier to administer than trying to figure out who spends enough to get a real Claude Code seat. The other nice thing about using API keys is that you basically never hit rate limits.

dcre··on Beginner-friendly, unofficial documentation for Helix text editor
Here's one way to see. Look at closed PRs with "changes requested" reviews:

https://github.com/helix-editor/helix/pulls?q=is%3Apr+is%3Ac...

dcre··on Beginner-friendly, unofficial documentation for Helix text editor
It’s not even an obscure Lisp flavor. It’s Scheme. You’re getting thrown off by the fact that they need their own embeddable interpreter for it written in Rust.

https://github.com/mattwparas/steel

dcre··on Beginner-friendly, unofficial documentation for Helix text editor
It’s a ridiculous and inflammatory claim to make about a clearly successful project with an enthusiastic community of users who love it. The maintainers have day jobs and have a clear and narrow vision that they don’t want to mess up by carelessly expanding the pool of maintainers. That is the entire explanation!
dcre··on Beginner-friendly, unofficial documentation for Helix text editor
I think you have it backwards in two ways:

1. While Helix dev is on the slow side, I think what you’re describing as specific to Helix is in fact the typical case in open source

2. In this case the author did a bunch of work up front and the maintainers said no almost immediately after the PR was posted

I agree they could be faster to say no, but I think part of it is that the maintainers would have to agree themselves and as far as I know they are not getting together to come to consensus about random Helix PRs every day.

dcre··on Beginner-friendly, unofficial documentation for Helix text editor
Worth mentioning that while this was very nice work by a Helix enthusiast, it was proposed as a replacement for the official docs and mostly rejected, and for good reasons IMO. An instructive discussion!

https://github.com/helix-editor/helix/pull/12127#issuecommen...

It's rarely a good idea to do a bunch of work on a big change to an open source project in a direction that has not been validated by the maintainers. Or at least, if you do, do it for your own education and don't have high expectations that it will be merged. The contributor in question had a very good attitude about it.

← PreviousPage 9 of 34Next →