On a similar note, 37Signals has just released their book Remote<http://37signals.com/remote/>which talks about the benefits and some best practices for remote working.
I've read about half of it so far and like Rework, it doesn't go into a lot of detail (and spends a lot of time on the benefits of remote working) but is definitely useful as a catalog of best practices. -Toby On Tue, Nov 26, 2013 at 10:12 PM, Erik Moeller <[email protected]> wrote: > A bit dated, but still an interesting read: > http://dt.deviantart.com/journal/We-re-all-remote-220038037 > > In particular, I like this idea: > > - - - > > Reactor > > We do have one long-running project team called Reactor. Its role is > to fix bugs that aren't related to other active projects, and to > implement features that aren't large enough to warrant spinning up a > separate project. It's also where we assign all new hires initially, > so its lead developer gets to mentor them and introduce them to our > codebase. Reactor makes a good training ground since it's guaranteed > to drag developers through disparate areas of deviantART. > > -- > Erik Möller > VP of Engineering and Product Development, Wikimedia Foundation > > _______________________________________________ > teampractices mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/teampractices >
_______________________________________________ teampractices mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/teampractices
