Live data from Hacker News

Lore – Give your coding agent the decisions your team made

github.com

51–60 of 63 posts

Re: Lore – Give your coding agent the decisions your team made

#51

Earlier quoted context omitted.

Yeah every same human would use m-dashes in their sentences — it just makes sense

It's not the em dashes, it's the sentence flow and the incorrect use of terms like "load-bearing". Also this user created an even newer account at the same time as posting this to drive engagement. /tinfoil-hat off

you mean I started a newer account? This is my first time posting on HR for things… so I’m new here, play nice!

Re: Lore – Give your coding agent the decisions your team made

#53

Earlier quoted context omitted.

So rac doesn’t merge ADRs or infer that soft-deletes survive… supercession is managed by the status on one ADR saying Superseeded, and the other saying Supersedes. This is enforced by the CI pipelines you can use (GitHub, etc) I think your example is a bit more of a modelling question, and if soft-delete must outlive the uniqueness decision it should be its own requirement that’s persisted as RAC guarantees the graph…

Gooot it, I was thinking there would be some merging happening, but that would be the task for an LLM I suppose :D Mental model fixed!

No worries, clearly better documentation would help!

Re: Lore – Give your coding agent the decisions your team made

#54

Earlier quoted context omitted.

What? Em-dash is option-shift-hyphen on Mac... it's easy to use them. I used to use them. I even used to grab hair-spaces to place on either side of them, as one should (though that doesn't work on HN).

Yeah but a regular - is just a single button press, why would I learn this keyboard combination if I never learned how / when to use emdashes in the first place?

I found out one day that the keyboard combination results in an em-dash, so now I use it where I would use an em-dash. I never went out of my way to inconvenience myself learning both the keyboard combination and the knowledge of where to apply it together. I just happen to have picked up how em-dashes are used, and I just happen to have picked up the keyboard combination to produce them, and so sometimes I will produce an em-dash where one can be used. I also tend to produce en-dashes in the same way (Option-Hyphen) when I express a range, as that is a way en-dashes can be used.

These arguments are so weird. It's like you assume I set out to learn my exact workflow rather than evolving it over time. My workflow is the sum of everything I know to apply, it's not a single algorithm I set out to learn all at once. If you don't care then you don't care, I'm not trying to justify it to you, only to say I exist and that others like me might too.

Re: Lore – Give your coding agent the decisions your team made

#56

Not to be confused with: Lore - Epic Games' open source version control system designed for scalability https://news.ycombinator.com/item?id=48571081

Yeah, naming clash clearly an issue but fundamentally different products. Epic just have the recognition over someone building OSS for the first time

Re: Lore – Give your coding agent the decisions your team made

#58

Earlier quoted context omitted.

It's not the em dashes, it's the sentence flow and the incorrect use of terms like "load-bearing". Also this user created an even newer account at the same time as posting this to drive engagement. /tinfoil-hat off

you mean I started a newer account? This is my first time posting on HR for things… so I’m new here, play nice!

And uses U+2026 HORIZONTAL ELLIPSIS instead of typing three periods? Also seems like LLM tell. But could just be a very efficient typist

Re: Lore – Give your coding agent the decisions your team made

#59

Earlier quoted context omitted.

you mean I started a newer account? This is my first time posting on HR for things… so I’m new here, play nice!

And uses U+2026 HORIZONTAL ELLIPSIS instead of typing three periods? Also seems like LLM tell. But could just be a very efficient typist

that’s just autocomplete when you type using a phone? Regardless of the semantics on language though, thoughts on the actual product?

Re: Lore – Give your coding agent the decisions your team made

#60
post #9

1. Write ADRs (or get agents to write them) 2. Commit ADRs to git 3. Mention ADRs in AGENTS.md

I agree, that method might work if you are working solo or in a small team - but for organisations the ability to centrally manage and gate this sort of ruleset avoids drift.

It's a good day to work in a monorepo :)
Post reply on HN