One of the biggest hurdles to adopting a new language within an established organisation is the available tooling. Not just the open source ecosystem, but also internal tools and libraries that have been built and refined for years. While some will see this as a reason to avoid adoption, it can also be an opportunity! With no existing tooling, it’s up to you to build it. My team at Zappi came from a mature, well-standardised Ruby on Rails ecosystem. When we moved to Elixir, we had to rebuild all of our internal tooling from scratch - which eventually led to the company’s first open source project. We all learned a lot along the way, and came and better, more well-rounded engineers.
Key Takeaways:
- This talk will show that moving to a less mature ecosystem (whether internal or open source) can be a source of opportunity instead of a pain point. In fact, sometimes it’s better to build it yourself - it helps you grow, and can surface areas of unnecessary complexity or abstraction.
Target Audience:
- Software engineers, engineering managers, upper management