@nateberkopec.bsky.social
I'm constantly thinking about and auditing my own moral life. I think it's our duty as human beings, but particularly as technologists and wielders of capital.
But I don't the solution is ever to pull back; to withdraw. Exclusion is ineffective as a means of creating change. It admits defeat.
But I don't the solution is ever to pull back; to withdraw. Exclusion is ineffective as a means of creating change. It admits defeat.
November 9, 2025 at 11:01 PM
I'm constantly thinking about and auditing my own moral life. I think it's our duty as human beings, but particularly as technologists and wielders of capital.
But I don't the solution is ever to pull back; to withdraw. Exclusion is ineffective as a means of creating change. It admits defeat.
But I don't the solution is ever to pull back; to withdraw. Exclusion is ineffective as a means of creating change. It admits defeat.
Welcome aboard Joshua Young to the Puma maintainers team 🫡
November 6, 2025 at 4:59 PM
Welcome aboard Joshua Young to the Puma maintainers team 🫡
What's the state of the art for OSS merch? We want to print some Puma stuff to hand out at conferences.
November 5, 2025 at 5:03 PM
What's the state of the art for OSS merch? We want to print some Puma stuff to hand out at conferences.
Useful OSS work that doesn't show up as a GH contribution:
This person quickly prototyped a pure-Ruby HTTP parser, just to give us some ballpark of performance. We said "interesting, the results show this isn't great, thank you!"
github.com/puma/puma/p...
This person quickly prototyped a pure-Ruby HTTP parser, just to give us some ballpark of performance. We said "interesting, the results show this isn't great, thank you!"
github.com/puma/puma/p...
[Experiment] Pure ruby parser by swebb · Pull Request #3660 · puma/puma
Description
As an experiment/learning exercise I decided to try implementing a HTTP parser in pure ruby. See #1889. I did this purely as an exercise and not in an attempt to get it merged. I&#...
github.com
October 30, 2025 at 4:58 PM
Useful OSS work that doesn't show up as a GH contribution:
This person quickly prototyped a pure-Ruby HTTP parser, just to give us some ballpark of performance. We said "interesting, the results show this isn't great, thank you!"
github.com/puma/puma/p...
This person quickly prototyped a pure-Ruby HTTP parser, just to give us some ballpark of performance. We said "interesting, the results show this isn't great, thank you!"
github.com/puma/puma/p...
I need a macOS desktop app for monitoring GH actions runs across multiple repositories, and get system notifications when they either pass or fail. Anyone also have this workflow?
October 29, 2025 at 10:26 PM
I need a macOS desktop app for monitoring GH actions runs across multiple repositories, and get system notifications when they either pass or fail. Anyone also have this workflow?
Prosopite + LLMs create a powerful workflow automation where you can get a PR fixing an N+1 with zero humans writing code
October 29, 2025 at 5:03 PM
Prosopite + LLMs create a powerful workflow automation where you can get a PR fixing an N+1 with zero humans writing code
Reposted
If you want to make change or add new feature to Ruby, I suggest to read www.a-k-r.org/pub/howto-pe...
Ruby's decision-making process isn't democratic or based on voting. It's more like a game of persuading Matz and Module maintainers.
Ruby's decision-making process isn't democratic or based on voting. It's more like a game of persuading Matz and Module maintainers.
www.a-k-r.org
October 28, 2025 at 9:56 PM
If you want to make change or add new feature to Ruby, I suggest to read www.a-k-r.org/pub/howto-pe...
Ruby's decision-making process isn't democratic or based on voting. It's more like a game of persuading Matz and Module maintainers.
Ruby's decision-making process isn't democratic or based on voting. It's more like a game of persuading Matz and Module maintainers.
Vibe check: I use LLMs for about 80% of my coding work now. That work is done with Claude Code, in the terminal. I run 1 to 2 agents at a time, dangerous mode. I rarely edit the code directly, but instead talk to the LLM until I get what I want, or write code/rules to corral it.
October 28, 2025 at 5:02 PM
Vibe check: I use LLMs for about 80% of my coding work now. That work is done with Claude Code, in the terminal. I run 1 to 2 agents at a time, dangerous mode. I rarely edit the code directly, but instead talk to the LLM until I get what I want, or write code/rules to corral it.
If you have any control over it, you should be running your CI with NVMe/attached storage. 10-30% faster tests vs network-attached block storage (i.e. EBS) for about ~2% more expensive instances. Test suites are highly bottlenecked on disk.
October 27, 2025 at 4:58 PM
If you have any control over it, you should be running your CI with NVMe/attached storage. 10-30% faster tests vs network-attached block storage (i.e. EBS) for about ~2% more expensive instances. Test suites are highly bottlenecked on disk.
Bloomberg terminal, but for AWS spot instance pricing in multiple regions
October 24, 2025 at 4:58 PM
Bloomberg terminal, but for AWS spot instance pricing in multiple regions
Using coding agents effectively is about brute-forcing.
Your task is turn tedious coding tasks into something than be brute-forced by $5 worth of GPU time.
You are setting up a loop which an agent can pass/fail itself against, and churn the loop until it passes.
Your task is turn tedious coding tasks into something than be brute-forced by $5 worth of GPU time.
You are setting up a loop which an agent can pass/fail itself against, and churn the loop until it passes.
October 23, 2025 at 4:57 PM
Using coding agents effectively is about brute-forcing.
Your task is turn tedious coding tasks into something than be brute-forced by $5 worth of GPU time.
You are setting up a loop which an agent can pass/fail itself against, and churn the loop until it passes.
Your task is turn tedious coding tasks into something than be brute-forced by $5 worth of GPU time.
You are setting up a loop which an agent can pass/fail itself against, and churn the loop until it passes.
Unsurprisingly, every "AI" product I've ever used is extremely buggy. Because, of course, they're building it "with AI".
October 22, 2025 at 4:57 PM
Unsurprisingly, every "AI" product I've ever used is extremely buggy. Because, of course, they're building it "with AI".
Rails "DIYstack" (kamal, hetzner, etc) hasn't yet solved reliability and trust for the data layer.
People running a business on Rails want backups, push-button recovery, zero-config HA (like Heroku PG premium). You can do a managed DB but you're stuck on hyperscalers then.
People running a business on Rails want backups, push-button recovery, zero-config HA (like Heroku PG premium). You can do a managed DB but you're stuck on hyperscalers then.
October 21, 2025 at 5:02 PM
Rails "DIYstack" (kamal, hetzner, etc) hasn't yet solved reliability and trust for the data layer.
People running a business on Rails want backups, push-button recovery, zero-config HA (like Heroku PG premium). You can do a managed DB but you're stuck on hyperscalers then.
People running a business on Rails want backups, push-button recovery, zero-config HA (like Heroku PG premium). You can do a managed DB but you're stuck on hyperscalers then.
@mikemcquaid.com why does brew bundle check take so long? on a scale of 1 to 10 spitballing how hard do you think it would be to make it faster?
October 21, 2025 at 2:34 AM
@mikemcquaid.com why does brew bundle check take so long? on a scale of 1 to 10 spitballing how hard do you think it would be to make it faster?
Frostpunk 2 is a must-play for fans of citybuilders. The mechanics are solid but the cinematic presentation is the best the genre has ever seen.
October 20, 2025 at 11:23 AM
Frostpunk 2 is a must-play for fans of citybuilders. The mechanics are solid but the cinematic presentation is the best the genre has ever seen.
If we learn anything from all this, I hope it's that governance of an OSS project doesn't need to be complicated, process-heavy or even democratic at all, but it does need to be written down.
Governance != RFCs, 5000+ words of Markdown. It always exists, just write it down.
Governance != RFCs, 5000+ words of Markdown. It always exists, just write it down.
October 17, 2025 at 11:47 PM
If we learn anything from all this, I hope it's that governance of an OSS project doesn't need to be complicated, process-heavy or even democratic at all, but it does need to be written down.
Governance != RFCs, 5000+ words of Markdown. It always exists, just write it down.
Governance != RFCs, 5000+ words of Markdown. It always exists, just write it down.
If I'm following RC correctly:
1) RC Did Nothing Wrong b/c it always had the right to the GH org, RC always owned Rubygems; Bundler merged into Rubygems, so they own Bundler too.
2) But, we're gonna hand it back to Ruby core.
3) Nobody has to sign a CLA
So what was the point?
1) RC Did Nothing Wrong b/c it always had the right to the GH org, RC always owned Rubygems; Bundler merged into Rubygems, so they own Bundler too.
2) But, we're gonna hand it back to Ruby core.
3) Nobody has to sign a CLA
So what was the point?
October 17, 2025 at 11:32 PM
If I'm following RC correctly:
1) RC Did Nothing Wrong b/c it always had the right to the GH org, RC always owned Rubygems; Bundler merged into Rubygems, so they own Bundler too.
2) But, we're gonna hand it back to Ruby core.
3) Nobody has to sign a CLA
So what was the point?
1) RC Did Nothing Wrong b/c it always had the right to the GH org, RC always owned Rubygems; Bundler merged into Rubygems, so they own Bundler too.
2) But, we're gonna hand it back to Ruby core.
3) Nobody has to sign a CLA
So what was the point?
The problem with scaling based on utilization is that no one knows what a good number is. "Will our customers be happy if we use our machines at 80% or 40%" is an unanswerable question. Queue times make the impact on customers clear: "will my users accept +200ms of latency?"
October 16, 2025 at 5:00 PM
The problem with scaling based on utilization is that no one knows what a good number is. "Will our customers be happy if we use our machines at 80% or 40%" is an unanswerable question. Queue times make the impact on customers clear: "will my users accept +200ms of latency?"
OSS codes of conduct should be:
1. Shorter
2. More focus on "do"s rather than "don't"s
3. Less faux-legalistic
4. Allow more discretion to moderators
5. Be tools of building culture
6. Be unique to the project (because all communities are unique), not copy-pasted
1. Shorter
2. More focus on "do"s rather than "don't"s
3. Less faux-legalistic
4. Allow more discretion to moderators
5. Be tools of building culture
6. Be unique to the project (because all communities are unique), not copy-pasted
October 12, 2025 at 11:22 PM
OSS codes of conduct should be:
1. Shorter
2. More focus on "do"s rather than "don't"s
3. Less faux-legalistic
4. Allow more discretion to moderators
5. Be tools of building culture
6. Be unique to the project (because all communities are unique), not copy-pasted
1. Shorter
2. More focus on "do"s rather than "don't"s
3. Less faux-legalistic
4. Allow more discretion to moderators
5. Be tools of building culture
6. Be unique to the project (because all communities are unique), not copy-pasted
Ah yes, another slow day moderating /r/ruby
October 9, 2025 at 8:00 PM
Ah yes, another slow day moderating /r/ruby
Anybody use a hardware firewall at home? Specifically I'm considering Netgate/pfSense or Ubiquiti, would be interested in anyone else who's done it.
October 8, 2025 at 5:02 PM
Anybody use a hardware firewall at home? Specifically I'm considering Netgate/pfSense or Ubiquiti, would be interested in anyone else who's done it.
you either die a hero or your react app becomes big enough that you need to virtualize your tables
October 7, 2025 at 4:57 PM
you either die a hero or your react app becomes big enough that you need to virtualize your tables
VCR, but for your database state in your tests
October 6, 2025 at 5:02 PM
VCR, but for your database state in your tests
A generational fumble by Ruby Central is now complete.
Anyway, I'm happy that the people who disagreed decided to get up and Do Something By Coding. I love to see that and can 100% get behind it 👍
Anyway, I'm happy that the people who disagreed decided to get up and Do Something By Coding. I love to see that and can 100% get behind it 👍
announcing a new community-focused gem server from the team previously behind rubygems: gem.coop. join us and start using it today!
October 6, 2025 at 5:03 AM
A generational fumble by Ruby Central is now complete.
Anyway, I'm happy that the people who disagreed decided to get up and Do Something By Coding. I love to see that and can 100% get behind it 👍
Anyway, I'm happy that the people who disagreed decided to get up and Do Something By Coding. I love to see that and can 100% get behind it 👍