avatar
Vlados0707

Following0Followers (X)737Posts56Likes82
avatar

everyone's screenshotting the same @karpathy line this week: stop using @claudeai to write code — point it at a folder, build yourself a second brain. the folder is the easy part. i had that in a day. it did almost nothing for two weeks. what makes it compound is the part nobody quotes: what gets written back, and when. → after every task, the agent appends ONE line to memory.md — a decision it made and why. not a summary of what happened. a decision. → anything it had to work out twice becomes a skill file. once it's a file, it's never re-derived again. → raw material — pdfs, transcripts, threads — goes in a dated inbox folder. the agent reads it on the next run and files what actually matters. → memory.md gets read FIRST, every single run, before it touches the task. a memory file nobody opens is just a file. → one weekly pass: delete anything in there that turned out wrong. a stale fact is worse than no fact. week 1 this feels like pure overhead. month 2 the agent stops asking you things it already learned, and the gap between "new chat" and "knows my whole setup" quietly disappears. the model stays swappable — claude, gpt, whatever wins next month. the memory and the git history of how it grew are yours. bookmark this. the "point it at a folder" posts will keep coming. this is the part they skip. #AI #ClaudeCode #AIagents

avatar

The End of Software Engineering chinese researchers published a paper titled "the end of software engineering." the argument: in agentic software, the agent is the software. code becomes ephemeral — generated, run, discarded. "what persists is the agent's capability, not its intermediate artifacts." take it seriously for a second. if the code is disposable, what's the durable asset? → the spec — the precise description of what you want, versioned → the memory — what the system learned about your domain, so it stops re-deriving it → the eval suite — how you know a new generation didn't quietly break something that's what you maintain now. the code is just the current print of it. #AI #AIagents

avatar

everyone's panicking about the wrong thing @OpenAI just cut @cursor_ai off. after @SpaceX bought it, they announced cursor loses direct model access on november 12. that post has 15 million views and the replies are devs realizing their whole workflow depends on a company that can flip a switch here's what the people who saw this coming did months ago: they stopped renting their ai leverage from one tool the setup that survives any of this, and costs nothing extra: → use an agent that isn't married to one model — @claudeai code, codex, opencode, aider all take a config swap → give it one project folder it owns: /in for sources, /out for what it produces, /skills for procedures it saves → connect your tools through mcp, not a tool's proprietary plugins — mcp moves with you → keep every model key in one env file. switching providers is a 10-second edit, not a migration → put it on a nightly job: it reads what you saved, updates /out, and leaves you a diff to approve over coffee → everything lives in git. the tool can die. your setup doesn't the point isn't which model. it's that no announcement can take your workflow away next time it's your tool getting acquired or cut off. the people with a portable setup won't even notice the news full setup below ↓ bookmark this before the feed buries it