delifue

5 ms·

31.
by delifue 1y ago
Can you explain what's the same underlying principle between Jevons paradox and Braess paradox?
32.
by delifue 1y ago
I think they Y axis (async/sync) should be auto-scheduling/manual-scheduling.
33.
by delifue 1y ago
A nitpick: select doesn't declare fields for where. select declare fields for having. it's the schema that declares fields that can be used in where.
34.
by delifue 1y ago
In my opinion Zig is elegant except for one thing: cannot attach data to error. https://github.com/ziglang/zig/issues/2647 You have to workaround by things like passing into a pointer to error object.
35.
by delifue 1y ago
In my experience Gemini can one-shot go apps. Determining it requires sound eval instead of anecdotes.
36.
by delifue 1y ago
An interesting point is that if you ask AI to security audit a codebase it can find the vulnerabilities. But the AI "forget security" when writing new features. This is probably caused by training data and RL.
37.
by delifue 1y ago
Did you add the type annotation of it in code?
38.
by delifue 1y ago
Yes the simple solution is obviously not perfect in edge cases. It's a tradeoff between simplicity and edge-case-perfectness. In my opinion the higher priority task is to optimize the query in backend so that it can refresh quickly. If
39.
by delifue 1y ago
The difference between Pony and Rust is that Pony allows easy reference cycle. One of the innovative point of Pony is the iso reference. iso reference means that an object graph is accessible from only that iso reference. It avoids sharing
40.
Complexity First, Simplicity Second(twitter.com)
4 points by delifue 1y ago|0 comments
41.
by delifue 1y ago
Go with sum type: Borgo https://github.com/borgo-lang/borgo
42.
The "honeymoon" and "marriage" of AI coding(twitter.com)
3 points by delifue 1y ago|0 comments
43.
by delifue 1y ago
> for example, we used tx.update for both inserting and updating entities, but LLMs kept writing tx.create instead. Guess what: we now have tx.create, too. If a function can both insert and update, it should be called "put". Us
44.
by delifue 1y ago
> First is to assume that almost everything is an assumption. Second is to insert enough flexibility into the work so that only minimal parts of it are lost if your assumptions are wrong. That's why rigid language like Rust is suita
45.
by delifue 1y ago
The correct way of storing disjoint intervals is to key by min endpoint of each interval and use ordered querying
46.
by delifue 1y ago
Update: the paper contains fake citation. The paper is likely LLM-generated. The original repo was deleted by HonestAGI. https://github.com/HonestyAGI/LLM-Fingerprint/issues/3 Sorry for submitting without car
47.
by delifue 1y ago
This is a common example of not fixing from root cause and try to fix from "outside valiation" that has bad side effects. The correct way of fixing SQL injection is to use prepared statement and parameters. Other examples: Windows
48.
Neural Networks Want to Work(yuxi-liu-wired.github.io)
1 points by delifue 1y ago|0 comments
49.
The Utility of Futility(parallelprogrammer.substack.com)
1 points by delifue 1y ago|0 comments
50.
Huawei's Pangu Pro MoE model is likely derived from Qwen model(github.com)
3 points by delifue 1y ago|1 comments
51.
by delifue 1y ago
Its main benefit is to avoid having extra data structure (like hash map) to find the missing or duplicate, using O(n) time and O(1) space.
52.
by delifue 1y ago
Go keeps on not adding syntax sugar for if err != nil. https://go.dev/blog/error-syntax But often the problem of language can be partially solved by IDE. IDE can already generate if err != nil branches. Goland can fold
53.
by delifue 1y ago
The hardware(GPU)'s architectural limitations may slow research more than PyTorch. The hardware lottery https://hardwarelottery.github.io/
54.
LLM-Oriented API Design(twitter.com)
3 points by delifue 1y ago|0 comments
55.
Abstraction boundaries are optimization boundaries(blog.snork.dev)
62 points by delifue 1y ago|33 comments
56.
Give LLMs the option to do nothing(twitter.com)
5 points by delifue 1y ago|0 comments
57.
The collective waste caused by poor documentation(shanrauf.com)
3 points by delifue 1y ago|0 comments
58.
by delifue 1y ago
"Software 2.0" reminds me of "web 3.0".
59.
The concurrency trap: How an atomic counter stalled a pipeline(conviva.com)
96 points by delifue 1y ago|43 comments
60.
by delifue 1y ago
Vibe coding is easy. Vibe debugging is hard.

More ›