Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
elijahbenizzy
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
elijahbenizzy
2y ago
There are a whole bunch of assumptions here. But sure, if you view the world as a closed system, then you have a decision as a function of inputs: 1. The world around you 2. The experiences within your (really, the past view of the world ar
32.
▲
by
elijahbenizzy
2y ago
This is humorous (and well-written), but I think its more than that. I'm always making the joke (observation) that ML (AI) is just curve-fitting. Whether "just curve-fitting" is enough to produce something "intelligent&q
33.
▲
by
elijahbenizzy
2y ago
I'm really curious to see how this will work with async. There's a natural barrier (I/O versus CPU-bound code), which isn't always a perfect distinction. I'd love to see a more fluid model between the two -- E.G. if
34.
▲
by
elijahbenizzy
2y ago
The title display is very clever but I really wonder if it would have as much of a punch if they displayed that one extra line on the "m"
35.
▲
by
elijahbenizzy
2y ago
Hey folks! Wrote a post on using Hamilton's async integration to build lightweight, scalable, and self-documenting LLM pipelines in python. Would love feedback/interest!
36.
▲
Async Dataflows in Hamilton
(blog.dagworks.io)
1 points
by
elijahbenizzy
2y ago
|
1 comments
37.
▲
Streaming Chatbot with Burr, FastAPI, and React
(blog.dagworks.io)
1 points
by
elijahbenizzy
2y ago
|
0 comments
38.
▲
Streaming Chatbot with Burr, FastAPI, and React
(blog.dagworks.io)
2 points
by
elijahbenizzy
2y ago
|
1 comments
39.
▲
by
elijahbenizzy
2y ago
Hey folks -- enjoyed writing this how-to on using SSEs to stream text back. The technologies are fairly specific but the components can easily be used individually.
40.
▲
Rewriting Wren AI LLM Service for 1500 Concurrent Users
(blog.getwren.ai)
5 points
by
elijahbenizzy
2y ago
|
0 comments
41.
▲
by
elijahbenizzy
2y ago
There's an interesting debate here -- see this tweet. https://x.com/ylecun/status/1769137037959913690 . Cool to see an actual article on it as opposed to speculation from personal experience. Now for some spec
42.
▲
by
elijahbenizzy
2y ago
heh, me guarding my area I wrote my name in heavily for a bit
43.
▲
by
elijahbenizzy
2y ago
It's really fascinating that most things in the US economy inflate (commodities, services, housing, etc...), but some things just inevitably deflate (TVs).
44.
▲
by
elijahbenizzy
2y ago
100% team rebase -- I think the fear comes from "rewriting history", which sounds scary until you realize that git is entirely immutable data store (through the API at least). Blockchain for the win! I find merging to be extremely
45.
▲
by
elijahbenizzy
2y ago
Agreed — also I’m generally against prototyping stuff and then entirely rewriting it for production as the default approach. It’s a nice idea but nobody ever actually rewrites it (or they do and it’s exceedingly painful). In true research i
46.
▲
by
elijahbenizzy
2y ago
I really like the idea of "good" and "bad" abstractions. I have absolutely built both. This sentiment is echoed in this comment in reddit comment as well: https://www.reddit.com/r/LocalLLaMA/com
47.
▲
by
elijahbenizzy
2y ago
Oh my god I barely even remembered this until the sound + the name popped right back. Wow!
48.
▲
Burr: Build AI Applications as State Machines
(burr.dagworks.io)
3 points
by
elijahbenizzy
2y ago
|
0 comments
49.
▲
by
elijahbenizzy
2y ago
This is delightful. I think that the hardest part (that, honestly, he absolutely nailed) is defining "rare" and "move" -- not only did he come up with reasonably satisfactory definitions, but he also was able to walk us
50.
▲
by
elijahbenizzy
2y ago
Backpropogration is just an application of the chain rule -- cool that we all learned it in high school!
51.
▲
by
elijahbenizzy
2y ago
Nice! These can make code a ton simpler. Also no python dependencies, which is a requirement for me adopting. Would love to see this brought into the standard lib at some point.
52.
▲
by
elijahbenizzy
2y ago
You’re telling me god didn’t cut corners? /s Yeah, reacting to so much perceived information being represented in such little code. Versus billions/trillions of weights in LLMs…
53.
▲
by
elijahbenizzy
2y ago
Fair enough. More reacting to the concept of a blockchain which is like old news and an extremely inefficient way to do 90% of what people are (we’re) trying to do with it. Will read!
54.
▲
by
elijahbenizzy
2y ago
Yeah so I’m lucky that I work in/adjacent to the space so it doesn’t get buried. Otherwise I think it’s near impossible to retain learning without practice.
55.
▲
by
elijahbenizzy
2y ago
Meh I don’t (they’re clearly imperfect) but I’m more wondering if we’re leaving lots of efficiency on the table in approaches to modeling the world.
56.
▲
by
elijahbenizzy
2y ago
that’s spectacular — the information density we perceive is off he charts for such a small amount of code. Makes me wonder if LLMs aren’t the best way to model the world at all…
57.
▲
by
elijahbenizzy
2y ago
I think the opposite. There is value in intelligent software, but IMO we’re a long way from AGI. So lots of grifting but some gold along the way. And it’s intellectually interesting/nuanced (cool math, interesting infra), unlike crypto
58.
▲
by
elijahbenizzy
2y ago
What's cool (and tough to keep up with) with this wave of tech is just how quickly it moves. On the plus side there's a lot of interesting things and it is generally easy to follow/figure out what they did. On the minus side
59.
▲
Tools can multiply or divide productivity
(blog.dagworks.io)
1 points
by
elijahbenizzy
2y ago
|
0 comments
60.
▲
by
elijahbenizzy
2y ago
“Peak baby” is an objectively bad thing
More ›