![]() Elixir lays claim to all of these features and I’ve seen teams ramp up on Elixir with astonishing speed, delivering robust, high-value projects to their organizations in record time. So, as a technical leader you don’t just select a language or a framework based on its technical capabilities and how suited it is for the problems you need to solve, you also try to optimize for the skills your team already has, for a robust ecosystem surrounding that language, for strong community support, and so much more. A language is only the right tool for the job if your engineers can wield it well. How the language design, the principles, and the philosophy is extremely well aligned with teams wanting wanting to punch well above their weight to deliver their best work.Īdopting a new language is more than just a technical journey. We’ll be talking about how Elixir is foundational to this endeavour. We are convinced that to remain focussed on our huge social impact ambition, we must remain small. Soon the registrations will be open for those of 35 years and above and we’re expecting many millions of registrations to occur within a few days. The South African National Department of Health launched the national Covid-19 vaccine registration programme on Turn.io a few weeks ago and the first million registrations have completed for those of ages 50 and older. Now, in 2021, 3 of the 4 worlds’ largest and most impactful social impact Covid-19 services on WhatsApp in the world are powered by Elixir using Turn.io. We were complete Elixir beginners when we launched the WHO Covid-19 service in 2020. There’s a commit in our Git repository from the 8th of January 2018 with the message “Backend in Elixir, Maybe? □♂️”. ![]() Why is it that the smaller teams seem to be able to effect change and retain focus in ways that larger teams struggle to do? What technology choices, cultural decisions, principles, and values allow for an environment where great small teams thrive? This phenomenon is especially true for teams able to harness software technology in ways that multiply and accelerate their efforts. The kind of team that leaves observers asking “how do you even?”. Teams whose impact is far greater than just the efforts of the individual members. There’s something magical about small teams that is hard to put words to. And then we’ll all write a little less Javascript. At the end I hope that you’ll create a new frontier with your own LiveView app. ![]() Along the way we’ll see how LiveComponent and Surface are driving the edges of what’s possible. We’ll look at code samples, best practices, and worst practices. This talk will examine our architecture, approach, and lessons learned. As a bonus, our SPA is embedded in third-party websites, so we had to deal with Javascript sourcing, third-party cookies, and security concerns as well.Īlthough we had a JS pro on our team, we all preferred writing Elixir. We had an ambitious project to roll our entire product into one LiveView app, which meant we needed authentication, routing, a navigation stack, state-dependent validation and progressions, asynchronous communication with our backend, and per-customer skinning. Most LiveView projects are small or feature-oriented: a table that sorts without reloading the page, a real-time analytics dashboard, or perhaps a chess game between friends. Want to know how we did it? Come to this talk! ![]() The title says it all- we wrote an entire SPA in LiveView! And it was great. In this talk, Veeps CTO Vinnie Franco and DockYard Senior Software Engineer Mike Binns discuss this process: the initial pains felt on the legacy app, the decision to bring in DockYard to help, the process improvements that Veeps and DockYard put in place, and the decision to rewrite the Veeps app in Elixir. Veeps decided it was time to take the next step, and brought in DockYard to help. Bottlenecks in the Rails app caused headaches, as the demand for their platform outpaced the platform’s ability to keep up. Veeps succeeded in bringing to market a platform that provided what was wanted: a livestream experience that both the artists and fans enjoyed. These needs require changes in communication, planning, development, and deployment practices - a shift from a startup mindset to an enterprise mindset. Startups that find success, however, reach an inflection point where customers rely on their service, so it needs to be dependable and scalable to retain customers. This often involves taking on technical debt to survive. Startup engineering teams have to be agile, responding quickly to customer needs and shipping them in days or weeks, not months. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |