@nateberkopec.bsky.social
narrator: neither would, in fact, happen in 2022
September 12, 2026 at 4:32 AM
narrator: neither would, in fact, happen in 2022
NixOS' community is so incredibly disorganized and full of infighting and the DHH/omarchy steamroller is so sufficiently funded and enthusiastic that they could conceivably just hard fork it and in 5 years the omarchy fork of nix just "is" nix as we understand it
September 9, 2026 at 9:58 PM
NixOS' community is so incredibly disorganized and full of infighting and the DHH/omarchy steamroller is so sufficiently funded and enthusiastic that they could conceivably just hard fork it and in 5 years the omarchy fork of nix just "is" nix as we understand it
Reposted
Another great reason to have a read replica AI can query is you can make informed data-driven decisions. And then share with the team via github issue comment or whatever. This image is an example of analyzing image upload dimensions to optimize for rendering.
September 6, 2026 at 6:36 PM
Another great reason to have a read replica AI can query is you can make informed data-driven decisions. And then share with the team via github issue comment or whatever. This image is an example of analyzing image upload dimensions to optimize for rendering.
LLM driven dev has completely changed my opinions on BDD
August 27, 2026 at 4:09 AM
LLM driven dev has completely changed my opinions on BDD
Reposted
August 17, 2026 at 10:53 PM
Reposted
say what you want about ai but pre ai i wasn’t able to do database performance work while sitting on my balcony at 3pm in the sun drinking a claw
August 18, 2026 at 10:50 PM
say what you want about ai but pre ai i wasn’t able to do database performance work while sitting on my balcony at 3pm in the sun drinking a claw
Puma 8.0 "Into The Arena" has been released!
1. Framework/lib authors can move threads into a special "high IO" pool
2. single/cluster DSL hooks for easier config
3. API for adjusting threadpool size at runtime (who would want to that? stay tuned...)
1. Framework/lib authors can move threads into a special "high IO" pool
2. single/cluster DSL hooks for easier config
3. API for adjusting threadpool size at runtime (who would want to that? stay tuned...)
April 9, 2026 at 12:46 AM
Puma 8.0 "Into The Arena" has been released!
1. Framework/lib authors can move threads into a special "high IO" pool
2. single/cluster DSL hooks for easier config
3. API for adjusting threadpool size at runtime (who would want to that? stay tuned...)
1. Framework/lib authors can move threads into a special "high IO" pool
2. single/cluster DSL hooks for easier config
3. API for adjusting threadpool size at runtime (who would want to that? stay tuned...)
Re: Axios - so I guess if you're an OSS maintainer, your threat model is now: "I may be targeted by a state-sponsored hacking group at any time."
April 3, 2026 at 5:03 PM
Re: Axios - so I guess if you're an OSS maintainer, your threat model is now: "I may be targeted by a state-sponsored hacking group at any time."
1 process per pod was a LIE that you were sold by BIG SRE and people who don't understand the oldhead technology of PRE-FORKING SERVERS.
We went from 1 Puma proc per pod to 4 and HALVED RESPONSE TIMES and dropped queue time to ZERO, for the same CPU/memory alloc.
We went from 1 Puma proc per pod to 4 and HALVED RESPONSE TIMES and dropped queue time to ZERO, for the same CPU/memory alloc.
March 26, 2026 at 10:43 PM
1 process per pod was a LIE that you were sold by BIG SRE and people who don't understand the oldhead technology of PRE-FORKING SERVERS.
We went from 1 Puma proc per pod to 4 and HALVED RESPONSE TIMES and dropped queue time to ZERO, for the same CPU/memory alloc.
We went from 1 Puma proc per pod to 4 and HALVED RESPONSE TIMES and dropped queue time to ZERO, for the same CPU/memory alloc.
Has anyone applied an autoresearch loop (successfully or not) to a Ruby project outside of Shopify yet? I would like to cover it in my RubyKaigi talk.
March 25, 2026 at 4:59 PM
Has anyone applied an autoresearch loop (successfully or not) to a Ruby project outside of Shopify yet? I would like to cover it in my RubyKaigi talk.
@simonwillison.net maybe you're used to this level of notability now, but I noticed Jensen Huang explicitly referencing the Lethal Trifecta a few times at GDC, although I noticed he said "it's fine as long as you only have two [legs of the trifecta]"
March 22, 2026 at 6:30 AM
@simonwillison.net maybe you're used to this level of notability now, but I noticed Jensen Huang explicitly referencing the Lethal Trifecta a few times at GDC, although I noticed he said "it's fine as long as you only have two [legs of the trifecta]"
The #1 most important performance work in almost any web app is converting full navigations into SPA/route changes/Turbo Drive clicks. You are converting a ~4 second experience into a 400ms experience every single time. Nothing else comes close.
March 19, 2026 at 4:59 PM
The #1 most important performance work in almost any web app is converting full navigations into SPA/route changes/Turbo Drive clicks. You are converting a ~4 second experience into a 400ms experience every single time. Nothing else comes close.
Super common mistake I see in Ruby setups: don't allocate more than 1 CPU core to background job containers. You're only running one process in there (usually) so there's no reason to allocate > 1 core.
March 18, 2026 at 5:02 PM
Super common mistake I see in Ruby setups: don't allocate more than 1 CPU core to background job containers. You're only running one process in there (usually) so there's no reason to allocate > 1 core.
After ~9 months of experimentation (synthetic and in prod), I can say definitively that MALLOC_CONF has no measurable effect on any Ruby workload that I've seen. Don't bother.
March 17, 2026 at 4:56 PM
After ~9 months of experimentation (synthetic and in prod), I can say definitively that MALLOC_CONF has no measurable effect on any Ruby workload that I've seen. Don't bother.
50% of what I'm doing at clients these days is addressing unclear expectations of what queue latencies are allowed to be in background work. Almost no one has the proper suite of alerts and observability, queues routinely ballooning without anyone realizing.
March 16, 2026 at 4:59 PM
50% of what I'm doing at clients these days is addressing unclear expectations of what queue latencies are allowed to be in background work. Almost no one has the proper suite of alerts and observability, queues routinely ballooning without anyone realizing.
It's pretty rare these days to be on a version this old, but if you're still running Ruby 3.1 in production: it's worth upgrading to 3.2+ purely to get YJIT.
March 13, 2026 at 4:56 PM
It's pretty rare these days to be on a version this old, but if you're still running Ruby 3.1 in production: it's worth upgrading to 3.2+ purely to get YJIT.
LCP is not a good top-level frontend metric to base your entire frontend perf efforts around _unless_ you are specifically targeting search rankings. LCP is not captured on route change/SPA nav or on Safari at all, which means ~50%+ of clicks go unmeasured.
March 12, 2026 at 4:58 PM
LCP is not a good top-level frontend metric to base your entire frontend perf efforts around _unless_ you are specifically targeting search rankings. LCP is not captured on route change/SPA nav or on Safari at all, which means ~50%+ of clicks go unmeasured.
Datadog's continuous profiling product is now best-in-class. Took them a while but Ivo Anjo has really put in a ton of work here for Ruby and the profiles you get now are so, so good. Being able to see gc activity (as well as the reason!) for GC is so cool.
March 11, 2026 at 5:00 PM
Datadog's continuous profiling product is now best-in-class. Took them a while but Ivo Anjo has really put in a ton of work here for Ruby and the profiles you get now are so, so good. Being able to see gc activity (as well as the reason!) for GC is so cool.
Seen in a Shopify project README. TIL RSpec is deprecated at Shopify.
February 27, 2026 at 4:59 PM
Seen in a Shopify project README. TIL RSpec is deprecated at Shopify.
LLM slopcannons are putting pressure on top of already broken software dev team cultures. The problem isn't the slop generator, so much as your process was only handling low volumes of human-generated slop until now.
February 26, 2026 at 4:59 PM
LLM slopcannons are putting pressure on top of already broken software dev team cultures. The problem isn't the slop generator, so much as your process was only handling low volumes of human-generated slop until now.
A pattern I am seeing: "Generate a 10 question quiz on how this PR works to test my understanding." Do not allow merge until someone passes the quiz.
Gusto did this years ago but with humans writing the questions for certain types of PRs.
Gusto did this years ago but with humans writing the questions for certain types of PRs.
February 25, 2026 at 5:00 PM
A pattern I am seeing: "Generate a 10 question quiz on how this PR works to test my understanding." Do not allow merge until someone passes the quiz.
Gusto did this years ago but with humans writing the questions for certain types of PRs.
Gusto did this years ago but with humans writing the questions for certain types of PRs.
You are probably not using LLMs enough to generate non-code artifacts. "Review this PR and then generate an interactive HTML website to explain it. Turn this state machine into a mermaid diagram. Generate a 10,000 word deep research report on the state of the art of CSRF protection."
February 24, 2026 at 4:56 PM
You are probably not using LLMs enough to generate non-code artifacts. "Review this PR and then generate an interactive HTML website to explain it. Turn this state machine into a mermaid diagram. Generate a 10,000 word deep research report on the state of the art of CSRF protection."
LLMs are (not _just_) autocomplete. They will tend to do MORE, tend to katamari. The dangers of shipping more code and never shipping less still apply.
February 23, 2026 at 4:56 PM
LLMs are (not _just_) autocomplete. They will tend to do MORE, tend to katamari. The dangers of shipping more code and never shipping less still apply.
Your prior at this point needs to be "if LLMs are breaking my SDE lifecycle, the problem is the lifecycle or how we are using the LLM, not the capabilities of the model". You can make models generate anything now. The problem is how you move them through the latent space.
February 20, 2026 at 4:58 PM
Your prior at this point needs to be "if LLMs are breaking my SDE lifecycle, the problem is the lifecycle or how we are using the LLM, not the capabilities of the model". You can make models generate anything now. The problem is how you move them through the latent space.
The only code review agent I have ever seen be even remotely good is just Codex xhigh. All the review services (and I've seen at least a dozen at this point) suck so bad that I'm not sure how they make any money at all.
February 19, 2026 at 4:57 PM
The only code review agent I have ever seen be even remotely good is just Codex xhigh. All the review services (and I've seen at least a dozen at this point) suck so bad that I'm not sure how they make any money at all.