For what it's worth, a big part of this is slowly winding down earlier commitments over time. I joined TAG a couple years ago, and decided not to run again this year because I had largely achieved my original goals of changing the composition and mission of the TAG, and others can carry the torch forward. I also retired from the Rails team this year after a somewhat-long period of inactivity (from day-to-day decisionmaking) for similar reasons.
The closest I can get to a single "secret" is aggressively delegating. What I mean by this is delegating before you feel comfortable delegating. The only way I know of to get everything done that I want to get done is to set the vision for something, do some initial implementation work, and find people who share the vision to help as early as possible. The primary reason I end up working on so many things is that things are way more connected than you might expect, and the full picture of something like Ember involves both day-to-day work on Ember and advocacy around a whole host of related technologies. I'm very grateful for the number of groups that have welcomed my participation.
I got involved in Rust largely because it was the shortest path to a low-overhead, non-crashy agent for Skylight, even counting the work we had to do to keep up with ongoing development over the past year. When getting involved in a technology so early, I tend to get really invested, and try to find holes that I know how to fill and fill them. That's what happened with Cargo and a whole bunch of other areas in Rust.
The closest I can get to a single "secret" is aggressively delegating. What I mean by this is delegating before you feel comfortable delegating. The only way I know of to get everything done that I want to get done is to set the vision for something, do some initial implementation work, and find people who share the vision to help as early as possible. The primary reason I end up working on so many things is that things are way more connected than you might expect, and the full picture of something like Ember involves both day-to-day work on Ember and advocacy around a whole host of related technologies. I'm very grateful for the number of groups that have welcomed my participation.
I got involved in Rust largely because it was the shortest path to a low-overhead, non-crashy agent for Skylight, even counting the work we had to do to keep up with ongoing development over the past year. When getting involved in a technology so early, I tend to get really invested, and try to find holes that I know how to fill and fill them. That's what happened with Cargo and a whole bunch of other areas in Rust.