81–90 of 93 posts
I'll let them (ai companies) figure it out while i keep coding manually. I'll wait for the day they will release a js library to programmatically do all this llm context juggling, instead of using a UI, and then I will adopt it by doing what I do now, writting code. I will write code that orchestrates llms for writting code. Edit: This is obviously a joke... but is it really a joke?
Earlier quoted context omitted.
It may be harsh but the reality is, if you have to ask you’re likely not a viable candidate. The leading AI companies have the kind of capital to be able to hire the very best of the industry. If you’re only just starting now and even worse yet need your hand held to do so you’re totally out of the running…
so what would be wise to do in this situation? leave the hope and surrender or completely start out and work in a nascent field?
You're basically like a junior dev trying to apply to be a lead dev for a team at Google
I want to really get into anthropic. For context: I have background in CV and ML in general. Currently reviewing and revising RL. Any idea how I can get into RL? I have 3 years of industry/research experience. Whenever I see post like this, it triggers a massive fomo creating a scene of urgency on I should work in these problems. Not being able to work here is making be anxious. what does it take for someone in Non-U…
Earlier quoted context omitted.
/compact does most of that, for me at least /compact we will now work on x, discard y, keep z
the trouble with compact is that no one really knows how it works and what it does. hence, for me at least, there is just no way I would ever allow my context to get there. you should seriously reconsider ever using compact (I mean this literally) - the quality of CC at that point is order of magnitute significantly worse that you are doing yourself significant disservice
Outside of context manipulation, it'd also be nice to standardize a format to label sections of the context and later append keywords to the context to ignore / unignore those sections (or refer back to them, emphasize them, whatever). With that, I imagine we'd be able to have a pretty good set of standard LoRA adapters that enable all LLMs to be controlled in the same fashion. That way agents will be able to manipulate LLMs in a standard way, without having to rewrite context itself.
I wish every instruction and response had a enable/disable checkbox so that I can disable parts of the conversation in such a way that it is excluded from the context. Let's say I submit or let it create a piece of code, and we're working on improving it. At some point I want to consider the piece of code to be significantly better that what I had initially, so all those initial interactions containing old code could…
There are 3rd-party chat interfaces out there that have much better context controls if it matters enough for you that you're willing to resort to direct API usage.
I wish every instruction and response had a enable/disable checkbox so that I can disable parts of the conversation in such a way that it is excluded from the context. Let's say I submit or let it create a piece of code, and we're working on improving it. At some point I want to consider the piece of code to be significantly better that what I had initially, so all those initial interactions containing old code could…
I exit and restart CC all the time to get a “Fresh perspective on the universe as it now is”.
Each new prompt involves asking Claude to read CURRENT.md for additional context.
I'm not sure if I should move this to CLAUDE.md but the stuff in CURRENT.md are very short term information that gets useless after a while.
---
There is one time where Claude entirely messed up the directory when moving things around and it sort of stuck in a weird "panic" loop in chat for quite a while (involving oh no / oh dear in chat), nothing git can't fix, but I suspect is due to the directory info in CLAUDE.md getting stale. Ever since then I moved things that might get stale to a separate file and frequently keep it updated/trimmed as needed.
I wish every instruction and response had a enable/disable checkbox so that I can disable parts of the conversation in such a way that it is excluded from the context. Let's say I submit or let it create a piece of code, and we're working on improving it. At some point I want to consider the piece of code to be significantly better that what I had initially, so all those initial interactions containing old code could…
Its faster and cheaper (in most cases) to leave the history as is and hit the cache.
Would this mean cursor and cline don’t have to do context management? Their value is much more just in the ui now?