21–30 of 67 posts
The "Try it. 10 seconds." section at the bottom of the page hijacks an existing tool (git diff) and installs a pre-commit hook. But there are no instructions for how to reverse those actions if you don't like the tool. Feels a little user-hostile to me.
I am sorry, should have put up a warning there, but You can do sem unsetup, if you go to the github, you will understand more about the way to reverse it.
$ sem impact authenticateUser ⊕ function authenticateUser (src/auth/login.ts:26) → depends on: db.findUser, rateLimiter.check ← used by: loginRoute, authMiddleware ! 42 entities transitively affected ᛋ 7 tests affected Okay that is pretty cool. I appreciate this information as a human also. I got about halfway through reinventing something like this last year (minus the git part). I was trying to make a graph of depe…
A step in the right direction, and interesting in that it layers over existing git rather than requiring a whole new (unfamiliar, untested) SCCS.
$ sem impact authenticateUser ⊕ function authenticateUser (src/auth/login.ts:26) → depends on: db.findUser, rateLimiter.check ← used by: loginRoute, authMiddleware ! 42 entities transitively affected ᛋ 7 tests affected Okay that is pretty cool. I appreciate this information as a human also. I got about halfway through reinventing something like this last year (minus the git part). I was trying to make a graph of depe…
Something like https://www.kythe.io/ ?
Earlier quoted context omitted.
Also I keep seeing solutions in this space that are doing inheritance and call stack dependency linkage, but I haven't seen the same level of exploration into data lifetime dependency. Not lifetime in the way it exists in Rust (to my knowledge), but like including when you copy data and transform that copy. The motivation is "if I change this variable, enumerate all the areas that change would propagate to". The idea…
This is a really interesting direction, you're essentially talking about data flow or taint analysis, where you track how a value propagates through copies and transformations rather than just following call edges. Honestly pure static analysis gets you partway there but it hits real limits once you run into dynamic dispatch, runtime branching, or serialization boundaries where data gets written somewhere and read ba…
I'm sorry for distracting from your engaging and thoughtful reply but I can't help but giggle at the name of this concept.
I am interested in subtle ways in which we can change how we write software to get better outcomes out of harnesses (model + tools + skills). I'm imagining that use of Sem will be more effective on code written in some shapes than others. Can you describe what ways this might be beyond just breaking up code into smaller functions? An example of this is that Models tend to create unit tests that are mostly just mock +…
What I've been more interested in lately is structural intelligence as a field in whole. Things with LLMs break because our infra was always designed for analyzing lines(tools like grep fuzzy matching) and working on quite small sections of code. LLMs struggle with this in cases when they have to analyze different parts of a codebase they either get too much context where you're throwing whole files at them, or too l…
I think this in apt and concise description of what this is trying to accomplish. I'm feeling like we had some really great gains in Model improvements both at the top end and the bottom over the last 6-7 months, but the next period is likely to be defined by harness improvements. I appreciate that your effort is being applied to this particular problem set because I think its far more fundamental to improving agentic performance in code bases than yet another memory framework.
Earlier quoted context omitted.
I am sorry, should have put up a warning there, but You can do sem unsetup, if you go to the github, you will understand more about the way to reverse it.
tone deaf comment. "read the docs to undo it" is user hostile.
Earlier quoted context omitted.
I am sorry, should have put up a warning there, but You can do sem unsetup, if you go to the github, you will understand more about the way to reverse it.
tone deaf comment. "read the docs to undo it" is user hostile.