Do yourself a favor and look up eBPF - it's incredibly powerful and cool tech. Basically lets you write scripts that run inside the kernel
At least they clarified they are in a yard rather than a lab.
It's the second sentence of the blog post.
Site is broken: "Error establishing a database connection"
What would it mean for codex to "implement LSPs"
errgroup has a SetLimit function to control the max number of concurrent go routines running at once.
> Like who really runs frontier LLMs at `max`? Umm what? Lots of people do
But how else am I supposed to know when we've reached AGI, until I see an absolutely flawless pelican? All of the pelicans so far have had really weird flaws / quirks so I am always a little interested to see how well…
You can also build your own harness for Claude, right? I think that's not against their ToS? Not saying it's ideal, just saying it's an option
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.
Do yourself a favor and look up eBPF - it's incredibly powerful and cool tech. Basically lets you write scripts that run inside the kernel
At least they clarified they are in a yard rather than a lab.
It's the second sentence of the blog post.
Site is broken: "Error establishing a database connection"
What would it mean for codex to "implement LSPs"
errgroup has a SetLimit function to control the max number of concurrent go routines running at once.
> Like who really runs frontier LLMs at `max`? Umm what? Lots of people do
But how else am I supposed to know when we've reached AGI, until I see an absolutely flawless pelican? All of the pelicans so far have had really weird flaws / quirks so I am always a little interested to see how well…
You can also build your own harness for Claude, right? I think that's not against their ToS? Not saying it's ideal, just saying it's an option
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.