[deleted]
Agents that run while I sleep
421–430 of 532 posts
Re: Agents that run while I sleep
#422[dead]
Re: Agents that run while I sleep
#423Earlier quoted context omitted.
Sounds interesting, would like to learn more about this. How do you imokement the scoring layer and when and how is it invoked?
The scoring layer sits between ingestion and storage. Incoming items get evaluated on a few axes: source reliability (did the agent observe this directly or was it told?), semantic distance from existing memories, and recency weighting for time-sensitive facts. Contradiction detection runs as a separate step - we embed the incoming memory, similarity-search against existing ones, and score the pair for logical consis…
Thanks for that. I'm new to the applied AI / ML world.
What's your stack and infra setup? Mainly Python, AWS, Databricks?
-
PS. previous comment typo: 'imokement' should have read 'implement'
Re: Agents that run while I sleep
#424Remember this, guys? https://agilemanifesto.org/
Re: Agents that run while I sleep
#425This _all_ (waves hands around) sounds like alot of work and expense for something that is meant to make programming easier and cheaper. Writing _all_ (waves hands around various llm wrapper git repos) these frameworks and harnesses, built on top of ever changing models sure doesn't feel sensible. I don't know what the best way of using these things is, but from my personal experience, the defaults get me a looong wa…
> like using PHP
lmao, chuckled
Re: Agents that run while I sleep
#426Earlier quoted context omitted.
> we’re finally admitting that all of that leetcode screening and engineer quality gating was a farce, or it wasn’t, and you’re wrong We’re admitting a bit of both. Offshoring just became more instantaneous, secure and efficient. There will still be folks who overplay their hand. Macroeconomically speaking, I don’t see why we need more software engineers in the future than we have today, and that’s probably a conserv…
> Macroeconomically speaking, I don’t see why we need more software engineers in the future than we have today, and that’s probably a conservative estimate. Why? Is the argument that there’s a finite amount of software that the world needs, and therefore we will more quickly reach that finite amount? Seems more likely to me that if LLMs are a force multiplier for software then more software engineers will exist. Or,…
> instead of “software engineers”, call them “people who create software” (even with the assistance of LLMs)
I think this is my hypothesis. A lot more people with a lot less training will create vastly more software. As a consequence, the trade sort of dissolves at the edges as something that pays a premium. Instead, other competencies become the differentiators.
Re: Agents that run while I sleep
#427Earlier quoted context omitted.
Your tests are an assertion that 'no matter what this will never change'. If your interface can change then you are testing implementation details instead of the behavior users care about. the above is really hard. A lot of tdd 'experts' don't understand is and teach fragile tests that are not worth having.
> Your tests are an assertion that 'no matter what this will never change'. That's a strange definition. A lot of software should change in order to adapt to emerging requirements. Refactorings are often needed to make those changes easier, or to improve the codebase in ways that are transparent to users. This doesn't mean that the interfaces remain static. > If your interface can change then you are testing implemen…
> A lot of software should change in order to adapt to emerging requirements.
True, but your tests should still aim to be testing the type of thing that will never change unless a customer requirement is changed, not because you want to refactor something.
This is of course impossible, but it should still be your goal.
>Your APIs also have users
Exactly - so test those APIs that have users, not the internal implementation details. If an API has users it quickly becomes an Augean Stables problem to change them and so you won't touch that API if you can at all help it (you may add a new/better way and slowly convert everyone, but it will be a decade before you can get rid of the old one)
> To other programmers, the implementation of a library, module, or even a single function can be a detail
other programmers are sometimes customers/users. If you are writing a logging system (what I happen to be working on today) your end users may never be allowed to see anything related to your system, but you expect to quickly have so many people calling Log() that you can't change the interface. By contrast you may be able to log to a file or a network socket - test those two backends by calling log() like your end users would and not be calling whatever the interface between the frontend (that selects which backend to use) and the backend is.
Again, the goal is to never update tests once written. I'm under no illusions you will (or even should) achieve this, but it is the goal.
Re: Agents that run while I sleep
#428Earlier quoted context omitted.
> sounds like alot of work and expense for something that is meant to make programming easier and cheaper. Not if you are an AI gold rush shovel salesman. From the article: > I've run Claude Code workshops for over 100 engineers in the last six months
Yeah, my colleague recently said "hey I've burnt through $200 in Claude in 3 days". And he was prompting. Max 8hrs/day Imagine what would happen if AI was prompting. As I like this allegory really much, AI is (or should be) like and exoskeleton, should help people do things. If you step out of your car putting it first in drive mode, and going to sleep, next day it will be farther, but the question is, is it still on…
[dead]
Re: Agents that run while I sleep
#429[flagged]
Re: Agents that run while I sleep
#430I tried getting the ai to write the tests. It created placeholders that contained no code but returned a success.
Seems like QA is the new prompt engineering