dgb23

5 ms·

31.
by dgb23 6mo ago
The code looks nice, but when I read GUI, I want to see screenshots of GUIs. Apparently a major dependency is "Fyne", which does show some screenshots on their page: https://fyne.io/
32.
by dgb23 6mo ago
It's an interesting problem for small businesses that want to sell stuff that will be used and relied on for a very long time. In a sense, they have to make themselves obsolete. Either by making sure they are a part of a larger network
33.
by dgb23 6mo ago
I think the explanation comes later in the article: "It is graph-native - not a vector database with graph features bolted on, not a document store with a graph view, but a graph at it's core - because the multi-hop question intel
34.
by dgb23 6mo ago
Familiarity matters to some degree. But there are diminishing returns I think. Stability, consistency and simplicity are much more important than this notion of familiarity (there's lots of code to train on) as long as the corpus is su
35.
by dgb23 6mo ago
> Then before you know it, the devops folks have decided that they need to put a gazillion other services and an entire software-defined networking layer on top of it. I'm not familiar with kubernetes, but doesn't it already do
36.
by dgb23 6mo ago
You can still do that. Not every business needs to be a hyperscaling startup.
37.
by dgb23 6mo ago
Both will likely happen to some degree. As for the average quality: it’s unclear. My intuition is that agents lift up the floor to some degree, but at the same time will lead to more software being produced that’s of mediocre quality, with
38.
by dgb23 6mo ago
Have you looked at their latest report? They are only profitable because of subsidies. Pretty much 1:1.
39.
by dgb23 6mo ago
If you are looking at open models, check out Pi, as its very extensible and comes with a sane default. Maybe even roll your own. Most harnesses (claude, codex, opencode etc.) assume that you use a cloud model. There’s no sense of optimizati
40.
by dgb23 6mo ago
> In many cases, simpler code is faster, and fast code makes for simpler systems. (...) I wholeheartedly agree with you here. You mentioned a few architectural/backend issues that emerge from bad performance and introduce unnecessar
41.
by dgb23 6mo ago
I like this collection. It's nicely presented and at least at a glance it adds some useful context to each item. While browsing it, I of course found one that I disagree with: Testing Pyramid: https://lawsofsoftwareengineeri
42.
by dgb23 6mo ago
It really depends on what you‘re trying to do and what your skillset is. But if you go information architecture first and have that codified in some way (espescially if you already have the templates), then you can nudge any agent to go str
43.
by dgb23 6mo ago
What is needed there are custom harnesses that don’t let the LLM decide what to do when. Use their power of pattern matching on data, not on decision transcriptions.
44.
by dgb23 6mo ago
I think the opposite is the case. We increasingly need to care more about performance and know how to leverage hardware better. The market is telling us that through increased hardware prices. LLMs being very powerful means that we need to
45.
by dgb23 6mo ago
Thank you for saying this. I hear it all the time in the recent two years: web development is apparently dead now, because anyone can just slap together a web site or build a dashboard in minutes etc. because of LLMs. But that has been true
46.
by dgb23 6mo ago
When I was younger this actually irked me a bit. I wasn't familiar with either, so it felt burdensome to me. The tooling also wasn't as good as it is now. However there's no doubt that this is one of the primary reasons why C
47.
by dgb23 6mo ago
Here's some hope: You will figure it out. You are already a person who is very curious, competent and experienced with making stuff.
48.
by dgb23 6mo ago
PHP's performance can be significantly lower than JS, because it doesn't have application state (in a standard runtime/setup) and needs to re-run the entire application for every request. Now there are a whole bunch of tricks
49.
by dgb23 6mo ago
OK so you're saying the gibberish is a feature and not a bug so to speak? So the thinking output can be understood as coughing and mumbling noises that help the model get into the right paths?
50.
by dgb23 6mo ago
Didn't you notice that the stream is not coherent or noisy? Sometimes it goes from thought A to thought B then action C, but A was entirely unnecessary noise that had nothing to do with B and C. I also sometimes had signals in the thin
51.
by dgb23 6mo ago
Don't look at "thinking" tokens. LLMs sometimes produce thinking tokens that are only vaguely related to the task if at all, then do the correct thing anyways.
52.
by dgb23 6mo ago
I agree with you here. I think this is for product placement for Mythos.
53.
by dgb23 6mo ago
This is funny on so many levels.
54.
by dgb23 6mo ago
It's certainly interesting that they provide an email service now. In their documentation/blog recommendations they switched their recommended approach twice or three times already. If they establish a solid email solution I will
55.
by dgb23 6mo ago
Do I expect the same memory footprint from an N active parameters as from simply N total parameters?
56.
by dgb23 6mo ago
Isn’t that security by obscurity?
57.
by dgb23 6mo ago
The future of harnesses cannot be „resend the whole history on every step“ or whatever this terrible compaction is. Most of the context is unstructured fluff, much of it is distracting or even plain wrong. Especially the „thinking“ tokens a
58.
by dgb23 6mo ago
Clojure and Go are similar to this from my experience.
59.
by dgb23 6mo ago
The last paragraph might be the most important one: > There's one other reason you should be interested in giving jj a try: it has a git compatible backend, and so you can use jj on your own, without requiring anyone else you'r
60.
by dgb23 6mo ago
Also it’s the wrong tool for this kind of work. Claude, opencode etc. Are brute force coding harnesses that literally use bash tools plus a whole bunch of vague prompting (skills, AGENT.md, MCP and all that stuff) to nudge them probabilisti

More ›