1st1

8 ms·

1.
by 1st1 6mo ago
potentially. I'm toying with the idea of distributed lat ;)
2.
by 1st1 6mo ago
- makes agent manage it for you in a controlled way - gives agent tools to search and traverse the graph, better than they can with grep - ability to have semantic links into your code and back etc, see the README
3.
by 1st1 6mo ago
Not really. > Having a CI job that identifies places where the docs have drifted from the implementation seems pretty valuable. Testing with lat isn't about ensuring consistency of code with public API documentation. It is about: *
4.
by 1st1 6mo ago
can you tell me more about what you mean by generative tests for spec conformance?
5.
by 1st1 6mo ago
Docs typically focus on the public api, lat focuses on both public and private impl detail
6.
by 1st1 6mo ago
I don't think this is related in any way.
7.
by 1st1 6mo ago
Read this section, I've just updated it to be more clear, hopefully will answer your question: https://github.com/1st1/lat.md?tab=readme-ov-file#the-idea
8.
by 1st1 6mo ago
One anecdote: I added lat to quickjs codebase and asked questions like "how does quickjs gc circular object graphs" and was able to get an answer in 12 seconds vs 2 minutes without lat. But take this with a grain of salt, I need b
9.
by 1st1 6mo ago
I'm working on a blog post and on benchmarks. Here [1] Armin suggested I take something like quickjs, built lat base for it, and compare side by side how, say, claude code works with lat vs. without. I'm very early into this and n
10.
by 1st1 6mo ago
++ > I suspect there's ways to shrink that context even more. Yeah, I'm experimenting with some ideas on that, like adding `lat agent` command to act as a subagent to search through lat and summarize related knowledge without p
11.
by 1st1 6mo ago
I think you can have your workflow with lat and it might make it even nicer. Would love feedback from you.
12.
by 1st1 6mo ago
I think it's a great idea and I'm considering building this in lat too. Code embedding models can definitely speed up grepping further, but they still wouldn't help much when you have a business logic detail encoded across mu
13.
by 1st1 6mo ago
Because lat gives agents more tools and enforces the workflow. Unlike obsidian, lat allows markdown files link into functions/structs/classes/etc too. This saves agents time on grepping but also allows you to build better wor
14.
by 1st1 6mo ago
I'm working on making lat hierarchical, e.g. - lat.md # high-level description of the project - frontend/lat.md # frontend-related knowledge - backend/lat.md # details about your backend
15.
by 1st1 6mo ago
Fixed
16.
by 1st1 6mo ago
Good idea. :) https://github.com/1st1/lat.md/commit/da819ddc9bf8f1a44f67f0...
17.
by 1st1 6mo ago
> My concern is scale though. Once you have thousands of nodes the Markdown files themselves become a mess to navigate The agent will update the graph. If you have thousands of nodes in md it means you have a highly non-trivial large cod
18.
by 1st1 6mo ago
The problem is that for any non-trivial question agents have to grep A LOT to understand the high-level logic expressed in code. In big projects grepping can take minutes some times. Lat short-circuits grepping significantly with `lat searc
19.
by 1st1 6mo ago
I'm working on a blog post about lat, stay tuned. Yes, it does work and I continue improving it.
20.
by 1st1 6mo ago
The graph can be human-maintained, but the preferred flow is to let agents update it.
21.
by 1st1 6mo ago
Adding a command to bootstrap lat for an existing code base is a good idea, I'll work on it. Other than that the goal of lat is to make the agent use it and update it and it has tools to enforce that.
22.
by 1st1 6mo ago
This is what lat is doing. `lat init` would install hooks to double check that Claude/Codex/OpenCode update lat.md when they finish the work.
23.
by 1st1 6mo ago
Creator of lat.md here. There are two videos with me talking about lat in more detail [1] and less detail [2]. But I'm also working on a blog post exploring lat and its potential, stay tuned. AMA :) [1] https://x.com/mi
24.
Show HN: PEP 827 – TS-like type manipulation in Python(peps.python.org)
7 points by 1st1 7mo ago|0 comments
25.
by 1st1 1y ago
FWIW polymorphic schema and queries are trivial in Gel https://docs.geldata.com/reference/edgeql/select#polymorphic...
26.
by 1st1 1y ago
geldata.com
27.
Hey Drizzle, please help – we want to speak SQL(geldata.com)
2 points by 1st1 1y ago|0 comments
28.
by 1st1 2y ago
Gel (ex EdgeDB) | SREs / Infrastructure Engineers | Full-time | Remote | https://www.geldata.com/ Gel is an open-source data platform built on top of Postgres. It’s designed to give developers a better end-to-end user
29.
by 1st1 2y ago
> Godot is a game engine. https://godotengine.org Yeah, I knew that, and precisely because of that I assumed it's a typo :) We have a native Python client. We can take a look if it works from Godot. Do you know if this i
30.
by 1st1 2y ago
Sorry, divan, for causing pain. This wasn't an easy decision. FWIW we're still strict about backwards compat and all you stuff should continue working.

More ›