It's not easy to summarize. I really recommend reading the whole thing.
> The company was founded in Constantinople in 1623 by Avedis Zildjian, an Armenian metalsmith and alchemist.
...
> After the death of Avedis, the business, and the secret for producing the metal, was handed down to several generations of male heirs.
...
> In 1850, Avedis II built a 25-foot schooner, in order to sail cymbals produced in Constantinople to trade exhibitions such as the Great Exhibition in London, and to supply musicians in Europe.
...
> Haroutune II's son Avedis III had left Armenia for the United States in 1909, and settled in Boston, where he established a family and a confectionary business. In 1927, he received a letter from his uncle Aram, informing him that he was to become heir to the family business, and Aram came to the US.
...
> Avedis III sought out jazz drummers like Gene Krupa to understand their needs.
I'm not looking to have the same environment everywhere, I'm fine to have windows stuff optimized for windows on windows, and vice versa on Linux.
By that reasoning, I think clink is a much better option.
I’m with a provider now who is phasing them out.
I have never got to this stage. Someone is added to the team. Someone leaves the team. New team members get more knowledge. Old team members get sick or take a lot of leave. The focus of what you're working on moves from one part of the code base to another.
Every time you have to throw your velocity out the window because you're not the same team any more, and those metrics are for a different team that no longer exists.
You could argue points are useful as a discussion point to make sure there isn't some massive piece of complexity hiding in something (everyone says 3 points, the quiet person who knows the most about it says 13), but even tshirt sizing covers that imo, and regardless after that you should just throw them away.
We do T-shirt sizes mapped to numbers, because recording effort in numbers lets you get an avg etc...
If you're a Claude Code user (I assume much of HN is) some context on Letta Code: it's a fully open source coding harness (#1 model-agnostic OSS on Terminal-Bench, #4 overall).
It's specifically designed to be "memory-first" - the idea is that you use the same coding agents perpetually, and have them build learned context (memory) about you / your codebase / your org over time. There are some built-in memory tools like `/init` and `/remember` to help guide this along (if your agent does something stupid, you can 'whack it' with /remember). There's also a `/clear` command, which resets the message buffer, but keeps the learned context / memory inside the context window.
We built this for ourselves - Letta Code co-authors the majority of PRs on the letta-code GitHub repo. I personally have been the same agent for ~2+ weeks (since the latest stable build) and it's fun to see its memory become more and more valuable over time.
LMK if you have any q's! The entire thing is OSS and designed to be super hackable, and can run completely locally when combined with the Letta docker image.