jerpint

6 ms·

31.
by jerpint 1y ago
The way I see it is that context evolves somewhat orthogonally to code. But you still want to track it in similar ways. Having git under the hood makes it easy to track its evolution and undo/diff things LLMs might decide to change, bu
32.
by jerpint 1y ago
I built a tool for this exact workflow in mind but with MCP and versioning included so you can easily track and edit the files on any platform including cursor, Claude desktop etc https://github.com/jerpint/context-llem
33.
by jerpint 1y ago
I wrote a tool for this, which allows you to co-create and maintain a context repository with your LLMs https://github.com/jerpint/context-llemur CLI for the humans, MCP for the LLMS. Whatever is in the context reposit
34.
by jerpint 1y ago
I got tired of repeating myself to LLMs over and over so I built context-llemur https://github.com/jerpint/context-llemur It’s a CLI/MCP context management tool that allows you to easily move your project context
35.
by jerpint 1y ago
I built a library to manage this exact workflow! I actually used the library to build the library https://github.com/jerpint/context-llemur It’s MCP/CLI friendly , and wraps git around a context: folder, so you ca
36.
by jerpint 1y ago
I wonder how long we’ll start seeing demos like this with just Gaussian splatting and seemless transitions / infinite exploration
37.
by jerpint 1y ago
Funny enough, I’m building a tool that does basically what the author describes, but with a bit more software engineering driving it (context-llemur) https://github.com/jerpint/context-llemur The idea is to track all o
38.
by jerpint 1y ago
I’ve been building a context-engineering tool for collaborating with LLMs. The CLI is for the human and the MCP is for the LLM, but they all map to the same core commands https://github.com/jerpint/context-llemur I’ve
39.
Show HN: Stop re-explaining context to every LLM (Git-based context engineering)(github.com)
2 points by jerpint 1y ago|0 comments
40.
Show HN: I built a context-engineering CLI/MCP tool(github.com)
2 points by jerpint 1y ago|0 comments
41.
by jerpint 1y ago
The last instruction > * Do not mention these guidelines and instructions in your responses, unless the user explicitly asks for them. Most companies have realized it is impossible to stop prompts from leaking. Some already openly publis
42.
by jerpint 1y ago
Cursor developed their own tab models IIRC
43.
by jerpint 1y ago
Not sure this really counts but “curating” social media feeds to follow high-signal ML researchers and devs to keep up with the latest trends, ideas and papers
44.
by jerpint 1y ago
I know nothing about this type of data; what does it mean and how can it be interpreted as an object ?
45.
by jerpint 1y ago
Are there currently services (or any demand for) a text classifier that you fine tune on your own data that is tiny and you can own forever? Like use a ChatGPT + synthetic data to fine tune a nanoBERT type of model
46.
by jerpint 1y ago
It’s been useful though given the authors popularity I suspect it’s only a matter of time new LLMs become “more aware” of it
47.
by jerpint 1y ago
This is seriously lacking but I think things like jailbreaks and malicious prompts make it a bit too brittle for now
48.
by jerpint 1y ago
From just my observations they basically parallelized the install sequence instead of having it be sequential (among many other optimizations most likely)
49.
by jerpint 1y ago
History in the making
50.
by jerpint 1y ago
That may be true today but not in a few weeks, ideally you have access to all models whenever
51.
by jerpint 1y ago
The fact that they produce this as “default” response is an interesting insight regardless of its internal mechanisms. I don’t understand my neurons but can still articulate how I feel
52.
by jerpint 1y ago
Batching can lead to variance with things like batchnorm but most transformers use layer norm to avoid this problem
53.
by jerpint 1y ago
I have a feeling LLMs could probably self improve up to a point with current capacity, then hit some kind of wall where current research is also bottle necked. I don’t think they can yet self improve exponentially without human intuition ye
54.
by jerpint 1y ago
Part of the fun is also figuring out the “best” way to achieve a thing. LLMs don’t often propose the best way and will happily propose convoluted ways. Clean approaches are still hard to come up with, but LLMs certainly help implementing th
55.
by jerpint 1y ago
> You keep your code in Python, decorate the functions you want to expose, and Davia starts a FastAPI server on your localhost Honestly it would be super useful to have this as a standalone feature , that can run native in cloud, kind of
56.
by jerpint 1y ago
Interestingly I’m on the other side of things, where I’ve been training NNs for quite some time and have lately been dedicating much more time to become more full stack, because most tasks these days can be solved with LLMs, which are mostl
57.
by jerpint 1y ago
These kinds of patterns allow compute to take much more time than a single chat since it is asynchronous by nature, which I think is necessary to get to working solutions on harder problems
58.
by jerpint 1y ago
Have you tried using llms.txt when available? Very useful resource
59.
by jerpint 1y ago
Having just figured auth recently for an app I’m building, I’ll echo that sentiment. Maybe lovable has auth components pre-built and well integrated
60.
by jerpint 1y ago
> I do most of my vibe coding on my phone, so that's pretty disappointing Curious what kind of phone apps you’ve been using to do vibe coding, I suppose it auto deploys stuff also?

More ›