Downloaded 25 times
Uploaded byBoldRadius Solutions
Scala Days 2014: Pitching Typesafe
The document outlines a session about adopting the Typesafe reactive platform to drive organizational change. It highlights reasons for using the platform, such as scalability, productivity, and quality improvements, while also addressing concerns like maturity and integration challenges. The session encourages participation and discussion, inviting attendees to share their contact information and visit a blog for further conversation.
More Related Content
Scala Days 2014: Pitching Typesafe
- 1. Pitching Typesafe An Interac3ve Session on Crea3ng Change in your Organiza3on
- 2.
- 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