buster
Joined 17 years ago
Joined 17 years ago
From your screenshot alone I can tell that those are not architecture decision records on the left side.
Ask yourself the question for each: is this truly an architecture decision or merely some design decision or requirement that now got some option a/b/c slapped onto it?
In the end you will just have a repo with hundreds of meaningless ADRs that your agent has to wade through.
Would you mind, if you could suddenly, over night, be a carpenter, a watch maker or glassblower?
I think it's most fair to compare the plain token pricing that is used by everyone.
This is just an assumption and the whole article falls flat if this turns out to be wrong. In my limited (as everyone else's) experience, working with agentic AI needs good documentation, good specification (spec driven, you know it's all the hype nowadays). Those alone lead to much improvement. Now take into account that probably your senior dev also has more time to think about the big picture, to improve all those little things that were a nuisance in the past but now are a mere "Claude, fix that" in a worktree away.. I would not bet on the assumption of this article.
For example, this issue aside, I'd rather split such a workload into multiple smaller instances, naturally. Because the impact of a crash on this single node, heavy load, many cores, many clients scenario would be huge.
Indeed, the acronym ADR is extremely confusing for everyone knowing Architecture Decision Records. Obviously i (and many others) misunderstood and so, my comment is moot.