What I’m more worried about is feature identification and how to monitor them. How can you get the product to the next level?
Honestly I’m not worried about code anymore in my codebase I’ve not had bug problems for a while and incidents get fixed automatically.
I monitor new features with an agent who checks recordings.
Most actually good features need still 20-30 iterations to design the userflow to actually be interactive, but then there is also another challenge to translate usage patterns into features and how to present functionality with the least amount of friction as possible.
How to efficiently run monitors without wasting your token spends. A best 'monitor' best practice would be nice.
Still this article was very helpful and gave me a lot of new ideas.
I mean i’m solodeving and on my github 30 commits a day is light green. Record probably was 280/day, but I’m not sure if every commit is merge to them. or if they just count PRs
I think they’re over reading code, but this almost sounds like they dont even read features/changes anymore. In theory I can imagine it. You have an agent to optimize a certain feature, you have an agent to clean up, you have an agent to develop a support strategy and so on.
They all would analyze data and suggest apple changes themselves.
Do you guys think that’s how it works? Is anybody already operating at that scale, how do you even validate stuff.
Like I think I could run my whole software now only on agents, but not sure how it would turn out.
I'm not the person to whom you're replying, but I just tried one of mine:
"I'm interested in understanding the rate of VOC dissipation from fresh oil paint on a surface versus the ventilation rate in the room in ACH. I would prefer solid academic studies of this, followed by analytical evaluation, followed by references to non-quantitative sources. Tell me what's known about this."
that I had run in ChatGPT earlier this week. (Yes, we just had our bedroom repainted, and it's TERRIBLE and I hate it, why do you ask? :-).
I didn't try it first in Gemini Flash, but I did try it in whatever model is used for Gemini Live and the answers were terrible. The ChatGPT answer (I think on medium) was pretty good but it threw in extraneous formulae that weren't actually germane to the analysis. The Argon 4 query I just ran was honestly the best of the answers I've gotten -- it was clear and really well-structured from the perspective of "here are the three big phases that researchers break down paint drying into and what the differing effects of ACH are on those phases".
I'm totally going to give this one a try, after basically giving up on 3.8 flash for most things despite having a free $20 pro subscription (from buying a phone).
I‘ve been on both camps and been critized for it (see my comments), and now I think these are some of the most useless disussions on HN, as they are heavily skewed by all of our life situations.
Hmm... interesting opinion. I disagree, and will insult you for it. With any luck, this comment chain will devolve into a thread of unsubstantiated opinions and ad hominems.
kalshi is to tough to be a market maker they have a 2% fee, PM doesnt have any. However MM is way more complicated than it looks like. There are very few small safe windows and informed traders are not stupid either.
I mean this sentence is just wrong. Coin Flips are 50/50 and I assume most decisions are not 50/50 and coding agents dont use high temperature so they don’t even very so much anymore. This sentence is a sentence to me that discredits a whole article because it’s just wrong.
Also practically it’s not a good way of seeing it. It would aim for the average solution of the problem which might not what you need, but its not a coin flip.
Honestly I’m not worried about code anymore in my codebase I’ve not had bug problems for a while and incidents get fixed automatically.
I monitor new features with an agent who checks recordings.
Most actually good features need still 20-30 iterations to design the userflow to actually be interactive, but then there is also another challenge to translate usage patterns into features and how to present functionality with the least amount of friction as possible.
How to efficiently run monitors without wasting your token spends. A best 'monitor' best practice would be nice.
Still this article was very helpful and gave me a lot of new ideas.
reply