Wide Teams

Episode #51: Lonocloud

Listen Later

In this episode, Aaron Brooks, Chris Houser, and Alan Dipert, of Lonocloud, share their distributed team’s hiring strategy, topic-oriented versus individual-oriented meetings, and yours/mine protocol while pairing.

Show Notes:

Lonocloud

Aaron Brooks (twitter github blog)
Chris Houser (twitter github blog)
Alan Dipert (twitter github blog)

00:47 – Introduction & background

[unordered_list style=”bullet”]

  • Aaron Brooks: Engineer #2 at Lonocloud
  • Chris Howser: Working remotely for 2 jobs; at Lonocloud for 1 year,
  • Alan Dipert: Programmer at Lonocloud, no prior distributed team experience

    [/unordered_list]

    02:27 – Location

    [unordered_list style=”bullet”]

    • Every time zone in the US is represented
    • Development team is fully distributed
    • 10-15 range

      • [/unordered_list]

      03:41 – History of distributed team

      [unordered_list style=”bullet”]

      • Hired remotely to be able to access different people
      • Lonocloud builds next generation multi-cloud federating infrastructure platforms
      • Emphasis on dynamic information policies
      • Distributed team working on distributed applications

        • [/unordered_list]

        06:40 – Hiring developers

        [unordered_list style=”bullet”]

        • Some people worked together previously and became available at the same time
        • Closure language community

          • [/unordered_list]

          08:16 – Difference between remote work and fully distributed work

          [unordered_list style=”bullet”]

          • Effort between teams with a central office/being fully distributed
          • Separate cliques between in-office and out-of-office groups
          • Fully distributed teams are all working towards the same goal
          • Shared pain of being fully remote
          • Unify around benefits of working from home

            • [/unordered_list]

            12:08 – A day in the life of Lonocloud

            [unordered_list style=”bullet”]

            • Daily developer call
            • Central server to log in remotely
            • Own development environment on their own screen; but can step in to see others work
            • Ad hoc pairing and splitting
            • More minds usefully contributing more quickly to a problem
            • Pairing, tripling as needed

              [/unordered_list]

              17:22 – Topic-oriented meetings versus individual-oriented

              [unordered_list style=”bullet”]

              • People can chime in with input if they want, but donâ€t have to
              • Google Doc for daily agenda
              • Not ticket-driven

                [/unordered_list]

                19:34 – Tools

                [unordered_list style=”bullet”]

                • HipChat
                • SIP service phones
                • Video sharing while pairing

                  [/unordered_list]

                  26:05 – Yours/Mine protocol while pairing

                  [unordered_list style=”bullet”]

                  • Context
                  • Vocalized

                    [/unordered_list]

                    28:38 – Splitting up work

                    [unordered_list style=”bullet”]

                    • Obvious fits
                    • Dynamic
                    • See what makes sense
                    • Key person help sessions
                    • People normally step up without obligation

                      [/unordered_list]

                      ...more
                      View all episodesView all episodes
                      Download on the App Store
                      Wide TeamsBy Avdi Grimm
                      • 4.6
                      • 4.6
                      • 4.6
                      • 4.6
                      • 4.6

                      4.6

                      10 ratings