tladeras’s avatartladeras’s Twitter Archive—№ 2,712

        1. @heatherklus and @jyotsna_sai talking about how to talk so engineers will listen. #cascadiaRconf
          oh my god twitter doesn’t include alt text from images in their API
      1. …in reply to @tladeras
        @heatherklus @jyotsna_sai Use machine learning to improve customer experience at @TMobile. Need to prepare customer care agent before the first response from customer. What impacts the customer, show status so agent can be more effective and helpful. #cascadiarconf
    1. …in reply to @tladeras
      @heatherklus @jyotsna_sai @TMobile Expert assistant: get conversation topic, aggregate customer data, pull up relevant documentation as fast as possible. This runs is real time. Wow. #cascadiarconf
  1. …in reply to @tladeras
    @heatherklus @jyotsna_sai @TMobile Used by 600 t-mobile messaging agents, 5 million hits/a week. Help care representative to help solve problems faster. #cascadiarconf
    1. …in reply to @tladeras
      @heatherklus @jyotsna_sai @TMobile Started out small. Data engineer/Data science language issues. How can you speak better to engineers as a data scientist? #cascadiarconf
      1. …in reply to @tladeras
        @heatherklus @jyotsna_sai @TMobile What are the words can you use across data sci/engineer teams? Talk about your feelings, and understand value conflicts. #cascadiarconf
        1. …in reply to @tladeras
          @heatherklus @jyotsna_sai @TMobile Values are different btw data engineers/scientists. Engineers value performance/scalability, Scientists value accurate insights. #cascadiarconf
          1. …in reply to @tladeras
            @heatherklus @jyotsna_sai @TMobile Try sharing incremental results, rather than hoarding results until the end. Definition of done - what do you need to consider a task done? Can help reduce ambiguity and friction. #cascadiarconf
            1. …in reply to @tladeras
              @heatherklus @jyotsna_sai @TMobile Share initial working version of model, so engineers can work on getting it into production. #cascadiarconf
              1. …in reply to @tladeras
                @heatherklus @jyotsna_sai @TMobile How do we measure success? Varies between scientists/engineers. Scientists: understand patterns in data, Engineers: value code working. What are dependencies of model? #cascadiarconf
                1. …in reply to @tladeras
                  @heatherklus @jyotsna_sai @TMobile Understand each other's needs. Not just results, but also the inputs and requirements for a model. #cascadiarconf
                  1. …in reply to @tladeras
                    Documentation that is useful for both scientists/engineers is important. What it does, rather than talking just about process. Ask what the other team is looking for #cascadiarconf
                    1. …in reply to @tladeras
                      Shortcuts: convince one engineer that your idea is important, they can convince other engineers your idea is great. #cascadiarconf
                      1. …in reply to @tladeras
                        Establish communication rituals, such as disciplines. Groups meet every week - product, engineering, data science, architecture. Knowledge transfer sessions to share knowledge and work. #cascadiarconf
                        1. …in reply to @tladeras
                          Informal sessions to talk are important. Collaborative environment and co-location of all groups important. Talk to each other! Treat each other with respect. Data scientists/engineers are each other's customers. #cascadiarconf
                          1. …in reply to @tladeras
                            In conclusion:
                            oh my god twitter doesn’t include alt text from images in their API
                            1. …in reply to @tladeras
                              Talk here: Http://bit.ly/r-cascadia-tmo #cascadiaRconf