Lexxy has received A TON improvements and fixes in recent versions. Check this:
github.com/basecamp/lexxy/releases/tag/v1.0.2
The reason: I merged 65 PRs! I captured the workflow I used in Basecamp and ran it in a card table. Instructions are in the project AGENTS.md in the Basecamp project:
public.app.basecamp.com
Reviews and steering are handled in context, in Basecamp cards.
Minimal human intervention here from my side. Side effort while at the company meetup in Chicago, where Lexxy definitely wasn't a priority for my week.
I have always been a pretty meh open source maintainer. I don't love reviewing other folks' PRs, so I always find other things I would rather do. So this is a huge improvement. I really enjoyed this process.
P.S: Thanks to @lylo for the friendly nudge that triggered this.
20 likes · 1,467 views
Hot Cell、こういうのもあるのか。
basecamp/hotcell
fizzy - Kanban tak, jak má být. Ne tak, jaký býval.
HEY も CLI とおしてエージェントから操作できるようになってる
@dhh There is also a pull request from @ZachSDaniel1 to add a reliability benchmark: once-campfire-verification#6
Rust is dropping more than 99% of messages under load, delivering fewer messages than Rails or Elixir.
143 likes · 9 reposts · 4,716 views
@bcardarella @CaesarDavid_ @dhh To be clear, I am not dismissing your overall question, which is "how well AI can do the job". That's a valid question but I am skeptical the benchmarks answer that either. Just compare the AGENTS.md files of Elixir and Go:
github.com/basecamp/once-campfire-elixir/blob/5a8…
github.com/basecamp/once-campfire-go/blob/9b0ef06…
Elixir is asked to use Rails as a reference, Go is asked to use Rust. So even if a given model knows how to improve Elixir, we are basically pruning that search space by saying "Preserve the pinned Rails reference behavior" which points to a checkout of the Rails app. And then the verifier is rejecting pull requests that try to deviate from it.
Anyway, I sent a PR to address that, we will see. No one is asking for special attention, just to be treated the same.
19 likes · 2 reposts · 679 views
Grifters gonna protect other grifters at all costs.
Here's @DHH's literal first commit to Rust rewrite repo: github.com/basecamp/once-campfire-rust/blob/f2936…
That's *before* 300+ commits to make it work.
For some reason Elixir isn't allowed to get rid of Redis and other bullshit, or have any commits t.co
36 likes · 1 repost · 1,652 views
Also extracted a separate verification project that's responsible for the benchmarking and checking of new implementations and improvements to the existing ones. The full report from the latest runs is there too. github.com/basecamp/once-campfire-verification/bl…
42 likes · 8,082 views
I'm still seething about `.dev`.
For those not in the know, Google lobbied ICANN to get the name and in their application they stated (repeatedly) that the intent was to buy it so that it could be reserved; as .dev was already used by developers and if someone bought it for commercial purposes it would harm the developer community.[0]
.... they then proceeded to start selling them.
Leading to all kinds of issues, the exact issues that they raised...
pow#397
valet#433
danielbachhuber.com
community.localwp.com
forums.theregister.com
[0]: gtldresult.icann.org
Hot Cell v1.1.0 is out with a new client class that works on legacy Ruby versions back to 1.9.3 for folks with legacy Rails apps to secure.
basecamp.github.io
This version also improves error handling, see the changelog at github.com/basecamp/hotcell/releases/tag/v1.1.0
7 likes · 2 reposts
Mentions
Lexxy has received A TON improvements and fixes in recent versions. Check this: github.com/basecamp/lexxy/releases/tag/v1.0.2 The reason: I merged 65 PRs! I captured the workflow I used in Basecamp and ran it in a card table. Instructions are in the project AGENTS.md in the Basecamp project: public.app.basecamp.com Reviews and steering are handled in context, in Basecamp cards. Minimal human intervention here from my side. Side effort while at the company meetup in Chicago, where Lexxy definitely wasn't a priority for my week. I have always been a pretty meh open source maintainer. I don't love reviewing other folks' PRs, so I always find other things I would rather do. So this is a huge improvement. I really enjoyed this process. P.S: Thanks to @lylo for the friendly nudge that triggered this.
Hot Cell、こういうのもあるのか。 basecamp/hotcell
fizzy - Kanban tak, jak má být. Ne tak, jaký býval.
HEY も CLI とおしてエージェントから操作できるようになってる
@dhh There is also a pull request from @ZachSDaniel1 to add a reliability benchmark: once-campfire-verification#6 Rust is dropping more than 99% of messages under load, delivering fewer messages than Rails or Elixir.
@bcardarella @CaesarDavid_ @dhh To be clear, I am not dismissing your overall question, which is "how well AI can do the job". That's a valid question but I am skeptical the benchmarks answer that either. Just compare the AGENTS.md files of Elixir and Go: github.com/basecamp/once-campfire-elixir/blob/5a8… github.com/basecamp/once-campfire-go/blob/9b0ef06… Elixir is asked to use Rails as a reference, Go is asked to use Rust. So even if a given model knows how to improve Elixir, we are basically pruning that search space by saying "Preserve the pinned Rails reference behavior" which points to a checkout of the Rails app. And then the verifier is rejecting pull requests that try to deviate from it. Anyway, I sent a PR to address that, we will see. No one is asking for special attention, just to be treated the same.
Grifters gonna protect other grifters at all costs. Here's @DHH's literal first commit to Rust rewrite repo: github.com/basecamp/once-campfire-rust/blob/f2936… That's *before* 300+ commits to make it work. For some reason Elixir isn't allowed to get rid of Redis and other bullshit, or have any commits t.co
Also extracted a separate verification project that's responsible for the benchmarking and checking of new implementations and improvements to the existing ones. The full report from the latest runs is there too. github.com/basecamp/once-campfire-verification/bl…
I'm still seething about `.dev`. For those not in the know, Google lobbied ICANN to get the name and in their application they stated (repeatedly) that the intent was to buy it so that it could be reserved; as .dev was already used by developers and if someone bought it for commercial purposes it would harm the developer community.[0] .... they then proceeded to start selling them. Leading to all kinds of issues, the exact issues that they raised... pow#397 valet#433 danielbachhuber.com community.localwp.com forums.theregister.com [0]: gtldresult.icann.org
Hot Cell v1.1.0 is out with a new client class that works on legacy Ruby versions back to 1.9.3 for folks with legacy Rails apps to secure. basecamp.github.io This version also improves error handling, see the changelog at github.com/basecamp/hotcell/releases/tag/v1.1.0