Scala Days 2014: Pitching Typesafe

  • 1,045 views
Uploaded on

Mike Kelland and the BoldRadius team lead an interactive discussion at Scala Days 2014 in Berlin on adopting the Typesafe Reactive Platform and creating change in your organization. …

Mike Kelland and the BoldRadius team lead an interactive discussion at Scala Days 2014 in Berlin on adopting the Typesafe Reactive Platform and creating change in your organization.

We explored approaches to solving the pain points that may arise, presenting tools, strategies and resources designed to help you adopt the Typesafe Reactive Platform today.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,045
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
19
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Pitching  Typesafe   An  Interac3ve  Session  on  Crea3ng   Change  in  your  Organiza3on  
  • 2. Why  Go  Typesafe?  
  • 3. Stand  up  if...   •  You're  using  Typesafe's  Reac3ve  PlaDorm  in   your  day  job   •  Your  company  is  inves3ng  in  your  learning   •  You're  using  it  on  a  personal  project   •  You've  started  learning  on  your  own   •  You're  trying  to  convince  your  team  to  try  it   •  You  have  an  interest  in  the  plaDorm  
  • 4. Green   Red   We  adopted  the   Typesafe  Reac3ve   PlaDorm  for   scalability   reasons   We  have   scalability   challenges  and   think  the   Typesafe   Reac3ve  PlaDorm   can  help  
  • 5. Green   Red   We  adopted   the  plaDorm   to  increase   produc3vity   We  have   produc3vity   challenges  and   think  the   plaDorm  can   help  
  • 6. Green   Red   We  adopted   the  plaDorm   to  improve   quality   We  need  to   improve  quality   and  think  the   plaDorm  can   help  
  • 7. Green   Red   We  built  a   strong   technical  team   on  the   plaDorm   We  have  found   it  challenging  to   build  a  technical   team  
  • 8. Green   Red   We  adopted  the   plaDorm  and   find  it  mature   enough   We're   considering  the   plaDorm  but  are   worried  about  its   maturity  level  
  • 9. Green   Red   We  have   successfully   integrated  the   plaDorm  with   enterprise  tools   We  have  tried  to   integrate  the   plaDorm  with   enterprise  tools   and  found  it   challenging  
  • 10. Green   Red   We  have   deployed   produc3on   systems  on  the   Typesafe   plaDorm   We  have  small,   non-­‐produc3on   systems,  and  are   worried  about   moving  forward  
  • 11. Green   Red   We  have   wriNen  tests   using  the   plaDorm's   libraries   We'd  like  to  use   the  plaDorm  for   automated   tes3ng  but  are   finding  it  difficult  
  • 12. Green   Red   We're   maintaining   systems  on  the   Typesafe   plaDorm   successfully   Maintaining  a   codebase  on   the  Typesafe   plaDorm  is   scary  or   challenging  
  • 13. Green   Red   We  have  used   benchmarks  to   convince  our   organiza3on  to   try  the  plaDorm   We  need   benchmarks  to   help  us   convince  our   organiza3on  
  • 14. Green   Red   We  broke   through   resistance  from   management   Convincing  our   managers  is  /   would  be  too   difficult  
  • 15. Green   Red   We  have   successfully   integrated   with  legacy   systems   Legacy  systems   and  current   infrastructure  is   blocking  us  from   trying  
  • 16. Green   Red   Our  team  is   excited  about   using  the   Typesafe   plaDorm   Our  team  is   skep3cal   about  the   benefits  of  the   plaDorm  
  • 17. Green   Red   Our  team  has   chosen  a  style   and  best   prac3ces   The  flexibility  and   diversity  of   solu3ons  for  each   problem  is   overwhelming  
  • 18. Green   Red   We  are  geUng   value  from  our   Typesafe   Developer   Subscrip3on   A  subs-­‐what?  
  • 19. Let's  con3nue  the  discussion   •  Write  your  contact  info  on  the  red  card   •  Visit  our  blog  at  www.boldradius.com  to  join   the  conversa3on