pull down to refresh

I think they are going great! I still need to automate some of it, or have processes for it or something, but people are contributing enthusiastically and new contributors keeping showing up.
Return on investment is fantastic strictly on a LoC/$. But it's especially good when we account for the opportunity cost we'd pay if ek and I weren't working on longer term priorities. Not to mention the value of all the fresh, relatively driveby takes we get.
(I also have some kind of an internal scorecard for it being good for bitcoin, other devs, etc. As a commons nerd, it's also just a really fun experiment.)
I meant to reply to this but forgot...
I wondered how you guys were handling the influx of PRs, balancing that with your ongoing work. I can see how it is nice to let other folks worry about smaller chunks of work, allowing you to focus on longer-running items. But I also know that context switching can be hard, especially if you're doing a lot of code review and actually checking out other people's code, running locally, etc.
reply
100 sats \ 0 replies \ @k00b OP 2 May
It works best when I chunk off code review to 1-2 days/week. If there’s enough work to review, it can be like merging in 1 week of work in 1-2 days.
reply