This is very cool.
Is there a compound skill.md that lets agents use the CLI in the right way, with some examples?
Sem: New primitive for code understanding – not LSPs, but entities on top of Git
61–67 of 67 posts
Re: Sem: New primitive for code understanding – not LSPs, but entities on top of Git
#62The "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.
Uninstalling a git hook isn't exactly rocket science. If you consider this user-hostile, you must have a terrible time using git in general, since it's not exactly the most noob friendly vcs.
Re: Sem: New primitive for code understanding – not LSPs, but entities on top of Git
#63This is very cool. Is there a compound skill.md that lets agents use the CLI in the right way, with some examples?
There is a skill.md for the agent to know about the cli, I can make update the same with more examples.
Re: Sem: New primitive for code understanding – not LSPs, but entities on top of Git
#64Earlier quoted context omitted.
There is still no good "data diff" tool that I can run on, say, a big pile of CSV or Parquet. Something with DVC integration would be especially welcome.
I would imagine because at scales where most folks use parquet files, you’re generally no longer really thinking in terms of individual diffs to your data (and also does imply some level of batch processing, vs e.g. a DB). We have some custom data diff tools at my ultracorp that provide a browsable interface, but the customer tends to be more operations folk than engineers or DS etc who would be more familiar with ac…
Sorta? Maybe I'm weird. I tend to use Parquet files inside my project instead of reading directly from and writing directly to our data warehouse. That lets me cut out a lot of overhead spent on just waiting for data to flow over the network, and also as a side benefit lets me track everything with DVC, which itself has a lot of benefits like being able to summon all project data with `dvc pull`.
I consider that a completely distinct use case from, say, Iceberg tables in S3.
Re: Sem: New primitive for code understanding – not LSPs, but entities on top of Git
#65This seems incredibly useful, but it's somewhat a shame you can't just organically grow language support through LSPs.
Re: Sem: New primitive for code understanding – not LSPs, but entities on top of Git
#66A step in the right direction, and interesting in that it layers over existing git rather than requiring a whole new (unfamiliar, untested) SCCS.
git is actually great, and there are not much of the issues as the world says about it, and the best is to build complimentary layers that makes it even stronger is the best bet I guess.
Not sure I'd go with "great" but it's what we have.
Re: Sem: New primitive for code understanding – not LSPs, but entities on top of Git
#67This seems incredibly useful, but it's somewhat a shame you can't just organically grow language support through LSPs.
I mean we are trying to be faster than LSPs, LSPs are a little slow for enterprise grade codebases