zknill

7 ms·

61.
by zknill 8mo ago
I also thought this was going to be about folks who'd migrated off AWS ECS.
62.
If code is cheap, intent is the currency(zknill.io)
3 points by zknill 8mo ago|0 comments
63.
If code is cheap, intent is the currency(zknill.io)
2 points by zknill 8mo ago|0 comments
64.
If code is cheap, intent is the currency(zknill.io)
1 points by zknill 8mo ago|0 comments
65.
by zknill 8mo ago
Assuming the traditional stateless routing of requests, say round robin from load balancers; how do you make sure the returning UI client ends up on the same backend server replica that's hosting the conversation? Or is it that all you
66.
by zknill 8mo ago
There's two parts to this article. The scheduler/preemption, and the transport over the network. The article is absolutely right that long-lived request/response over HTTP connections with SSE streamed responses suck. The art
67.
A chatbot's worst enemy is page refresh(zknill.io)
84 points by zknill 8mo ago|25 comments
68.
by zknill 8mo ago
presumably a dupe of: https://news.ycombinator.com/item?id=47046068
69.
A chatbot's worst enemy is page refresh(zknill.io)
1 points by zknill 8mo ago|0 comments
70.
Only use agents for tasks you know how to do(zknill.io)
1 points by zknill 8mo ago|0 comments
71.
A chatbot's worst enemy is page refresh(zknill.io)
2 points by zknill 8mo ago|1 comments
72.
A chatbot's worst enemy is page refresh(zknill.io)
2 points by zknill 8mo ago|1 comments
73.
Only use agents for tasks you know how to do(zknill.io)
1 points by zknill 8mo ago|0 comments
74.
A chatbot's worst enemy is page refresh(zknill.io)
2 points by zknill 8mo ago|0 comments
75.
A chatbot's worst enemy is page refresh(zknill.io)
1 points by zknill 8mo ago|0 comments
76.
Rule #1 for coding with AI agents(zknill.io)
1 points by zknill 8mo ago|0 comments
77.
Rule #1 for coding with AI agents(zknill.io)
1 points by zknill 8mo ago|0 comments
78.
SSE sucks for transporting LLM tokens(zknill.io)
38 points by zknill 10mo ago|45 comments
79.
SSE sucks for transporting LLM tokens(zknill.io)
6 points by zknill 11mo ago|1 comments
80.
SSE sucks for transporting LLM tokens(zknill.io)
3 points by zknill 11mo ago|0 comments
81.
by zknill 11mo ago
It seems like this post is a response to the discussion on this previous HN post[0]. There are two main criticisms of "Event [sourcing|driven]" patterns. First, that storing a full history of events becomes a backwards-compatible
82.
SSE sucks for transporting LLM tokens(zknill.io)
2 points by zknill 11mo ago|1 comments
83.
So you want to build AI agent group chat?(zknill.io)
1 points by zknill 11mo ago|0 comments
84.
by zknill 11mo ago
I recently had a brief brainstorming with someone building an AI data enrichment tool. I found myself suggesting the 'entities' in the tool would just be semi-structured json blobs; instead of normalising the data into some relati
85.
by zknill 11mo ago
This will work, so long as people trust the results are not (too) skewed by paid ads. I recently used Claude and ChatGPT for exactly one of the examples; comparing different bikes to buy. They could both look up the bike specs and geometry
86.
by zknill 11mo ago
I think you might struggle to "scale the read and write sides independently". It's a real stretch to be describing a postgres view as CQRS
87.
by zknill 11mo ago
> You can't blame event sourcing for people not doing it correctly, though. Perhaps not, but you can criticise articles like this that suggest that CQRS will solve many problems for you, without touching on _any_ of its difficulties
88.
by zknill 11mo ago
Please explain how you intend to use different models for reading and writing without there being some temporal separation between the two? Most all CQRS designs have some read view or projection built off consuming the write side. If this
89.
by zknill 11mo ago
Anyone who's built, run, evolved, and operated any reasonably sized event sourced system will know it's a total nightmare. Immutable history sounds like a good idea, until you're writing code to support every event schema you
90.
by zknill 11mo ago
It's rare that you come across a product where everything you use works so well for you. The kagi AI search results triggered with "?" and the Kimi K2 model from assistant are both excellent in helping find what I actually wa

More ›