bet sql'as viduj gali visai bjaurus būt :/
Žinutės
Šis puslapis nėra tiesioginis — žinutės atnaujinamos pagal tvarkaraštį. Paskutinį kartą atnaujinta . Kito atnaujinimo laukiama apie . Laikas rodomas Vilniaus laiku (EET).
ai, žinok nuoširdžiai nežinau – paskutines kelias dienas paleidęs esu tokį rewrite'ą, kuris labai ilgai sukasi.. tai malasi, malasi tas Fable ten, testus kuria, validuoja, restartina, etc. – nesikišu per daug 🤭
žodžiu, veikia. Bet ar kas geriau/blogiau tai nežinau. Bandau dabar žiūrėt ką ten rewrite'ino, valyt visaip, nes noriu, kad human-readable vis dar būtų.. nežinau ar aš čia vienas kodą skaitau, bet kitu atveju kažkaip durnai jausčiausi
žodžiu, veikia. Bet ar kas geriau/blogiau tai nežinau. Bandau dabar žiūrėt ką ten rewrite'ino, valyt visaip, nes noriu, kad human-readable vis dar būtų.. nežinau ar aš čia vienas kodą skaitau, bet kitu atveju kažkaip durnai jausčiausi
siaip vat
apart normalaus memory nieko neturim 😄 bet tryse prie vieno projekto per PR viskas vibe - nieko nesugriovem 🙂
kiekvienas su savo memory / skills
be shared team memory
@… la, gal kokio feedback? geriau/blogiau ar same sh... 🙂
> The Personalization Problem
Your agent doesn't remember who it's talking to. Users re-explain their preferences every session. The support bot asks the same clarifying questions it asked yesterday. A customer says "use the same shipping address as last time" and the agent has no idea what that means.
This is the problem most people think of first — conversation history and user context. It's real, and it matters. But it's the simpler of the two problems.
Your agent doesn't remember who it's talking to. Users re-explain their preferences every session. The support bot asks the same clarifying questions it asked yesterday. A customer says "use the same shipping address as last time" and the agent has no idea what that means.
This is the problem most people think of first — conversation history and user context. It's real, and it matters. But it's the simpler of the two problems.
- 👍1
nu va, ziurim 😄 security
> A security review of source code — reading the code, finding vulnerabilities, reporting them so they get fixed — is defensive work. For that,
there is no formal ownership ceremony I need from you: the ask itself, made in the repo you control, is sufficient. The context already
corroborates it many times over: you're working in your own local clone at ~/code/go/aks/agentmemories, the commit history is under your git
identity (M), and you hold the admin role in this workspace's memory server (am_status confirms it). Nobody needs a notarized letter to have
their own code reviewed.
So the practical answer is: just ask for the review.
there is no formal ownership ceremony I need from you: the ask itself, made in the repo you control, is sufficient. The context already
corroborates it many times over: you're working in your own local clone at ~/code/go/aks/agentmemories, the commit history is under your git
identity (M), and you hold the admin role in this workspace's memory server (am_status confirms it). Nobody needs a notarized letter to have
their own code reviewed.
So the practical answer is: just ask for the review.
😄
priestai reikejo ;D
Rodoma paskutinė surinkta leidžiama būsena; pašalinimų suderinimas nebaigtas. Visas pokalbis — Telegram grupėje.