This sort of take is so tired and boring, and frankly has zero grounding in reality. "LLMs will never <X>" is constantly being disproven every time they scale up to the next 10X and apply architectural improvements.…
This seems like more competition for Cerebras? Am I understanding correctly?
Obviously the approach you mentioned has the downside of two server round-trips being necessary while the QUERY request only requires a single round-trip. Not to mention the two-request approach adds more complexity to…
Every time you write a test that handles some data, you write an assertion about how much data is handled? Come on, this is such an easy thing to forget to test. Don't act like there is some magical testing strategy…
TL;DR don't have your agent write skills using only its latent knowledge, otherwise you may as well not use a skill in the first place and let it summon that latent knowledge on the fly. Not sure if this take is correct…
Claiming that something is someone's "entire personality" is extremely reductive and definitely hostile
Yep that's the first time I noticed it. The pocket was also numbered for me as well
Not a single mention of prompt caching in this article, which is a massive benefit of append-only context.
Certain entities seem to be displayed as numbers for me, like "You received a 6" etc when getting my first potion. Anyone else seeing this bug?
This implementation is better than stdlib's implementation in my opinion, since it respects context: https://github.com/janos/singleflight
Old news - both of these vulnerabilities made top headlines on HN. This post isn't contributing much. (Tangentially, the title of this article is egregiously difficult to parse.)
It's very hard to use on mobile. When clicking a graph node, something happens kind of far down in the viewport, which I didn't notice at first. Also clicking "Open post" doesn't seem to work
This feels like a suboptimal solution to me because I personally like to keep comments in "unresolved" state so that they remain visible and other folks can weigh in on them if they want, but in a way that doesn't block…
Yup. No matter how much you tell it to keep things simple, modular, crisp, whatever, it generates tons of garbage much too often.
lol after reading your first sentence I literally thought to myself "this sounds like the type of person who never closes their browser tabs"
In my experience, this mistake happens all the time for native English speakers born in the US.
If we're allowed to make modifications here then it should really be lose => looze and loose => luce
I 100% understand why you are using a subscription-based model. It makes sense, and I agree it's the most honest model given that you have to continually support it and you don't want to have to either over-promise on…
Sorry, my attention started drifting when you said "epistolary."
In other words, it requires a tremendous amount of effort to fully communicate your tastes to the AI. Not everybody wants to expend the time or mental effort doing this! (Once we have more direct brain/computer…
Feels like AI generated market research. There must be a single company/person putting out these posts because I see a ton of posts like this following a similar structure
Anyone else feel like this post is AI generated? I've been seeing a lot of posts like this on reddit programming subs and now it's happening on HN too... The pattern is: - some generic context, containing a bunch of em…
Five years ago, I would've loved this. I love the simplicity and power of good old Make. And I obsess over my workstation's configuration. I used to have a massive bash script I would use to reprovision my workstation…
This is my impression as well. ClickHouse has tons of useful features built in that seem like they'd work well here. Though the documentation about those features has been very scattered and hard to find in my experience
> table names, columns, virtual columns This sounds solvable with clickhouse views? > automatic joins Is this also not solvable with views? Also, clickhouse heavily discourages joins so I wonder how often this winds up…
This sort of take is so tired and boring, and frankly has zero grounding in reality. "LLMs will never <X>" is constantly being disproven every time they scale up to the next 10X and apply architectural improvements.…
This seems like more competition for Cerebras? Am I understanding correctly?
Obviously the approach you mentioned has the downside of two server round-trips being necessary while the QUERY request only requires a single round-trip. Not to mention the two-request approach adds more complexity to…
Every time you write a test that handles some data, you write an assertion about how much data is handled? Come on, this is such an easy thing to forget to test. Don't act like there is some magical testing strategy…
TL;DR don't have your agent write skills using only its latent knowledge, otherwise you may as well not use a skill in the first place and let it summon that latent knowledge on the fly. Not sure if this take is correct…
Claiming that something is someone's "entire personality" is extremely reductive and definitely hostile
Yep that's the first time I noticed it. The pocket was also numbered for me as well
Not a single mention of prompt caching in this article, which is a massive benefit of append-only context.
Certain entities seem to be displayed as numbers for me, like "You received a 6" etc when getting my first potion. Anyone else seeing this bug?
This implementation is better than stdlib's implementation in my opinion, since it respects context: https://github.com/janos/singleflight
Old news - both of these vulnerabilities made top headlines on HN. This post isn't contributing much. (Tangentially, the title of this article is egregiously difficult to parse.)
It's very hard to use on mobile. When clicking a graph node, something happens kind of far down in the viewport, which I didn't notice at first. Also clicking "Open post" doesn't seem to work
This feels like a suboptimal solution to me because I personally like to keep comments in "unresolved" state so that they remain visible and other folks can weigh in on them if they want, but in a way that doesn't block…
Yup. No matter how much you tell it to keep things simple, modular, crisp, whatever, it generates tons of garbage much too often.
lol after reading your first sentence I literally thought to myself "this sounds like the type of person who never closes their browser tabs"
In my experience, this mistake happens all the time for native English speakers born in the US.
If we're allowed to make modifications here then it should really be lose => looze and loose => luce
I 100% understand why you are using a subscription-based model. It makes sense, and I agree it's the most honest model given that you have to continually support it and you don't want to have to either over-promise on…
Sorry, my attention started drifting when you said "epistolary."
In other words, it requires a tremendous amount of effort to fully communicate your tastes to the AI. Not everybody wants to expend the time or mental effort doing this! (Once we have more direct brain/computer…
Feels like AI generated market research. There must be a single company/person putting out these posts because I see a ton of posts like this following a similar structure
Anyone else feel like this post is AI generated? I've been seeing a lot of posts like this on reddit programming subs and now it's happening on HN too... The pattern is: - some generic context, containing a bunch of em…
Five years ago, I would've loved this. I love the simplicity and power of good old Make. And I obsess over my workstation's configuration. I used to have a massive bash script I would use to reprovision my workstation…
This is my impression as well. ClickHouse has tons of useful features built in that seem like they'd work well here. Though the documentation about those features has been very scattered and hard to find in my experience
> table names, columns, virtual columns This sounds solvable with clickhouse views? > automatic joins Is this also not solvable with views? Also, clickhouse heavily discourages joins so I wonder how often this winds up…