Karoline is a full-stack software engineer at Multiverse, building an outstanding alternative to university and corporate training. After working as a civil engineer for 5 years and using Python for data analysis, in early 2022 she decided to take a leap into the world of software development, and hasn’t looked back since.
She has used Elixir, Phoenix and LiveView for just over a year, and is constantly looking for ways to expand her knowledge and learn new tech. On a day-to-day basis she is building the Multiverse Platform, enabling candidates to research, apply, and get hired for world-class tech apprenticeships. She is passionate about improving diversity and equality of opportunity in the tech sector.
Karoline is from Norway but is currently based in London. She enjoys the outdoors and will (hopefully) be running the London marathon 2 days after ElixirConf EU!
Have you dabbled with Phoenix LiveView, but sometimes hit roadblocks that made you think it couldn’t do what you wanted? How come Chris McCord makes it look so easy, and when you try it yourself it’s so hard? As a new Elixir dev working on my first LiveView feature, that’s how I felt.
The first LiveView feature I built was an interview availability scheduler. That is, a form where a user can add, delete and edit timeslots for which hiring managers are available for interviews. It’s been done many times before, right? Shouldn’t be that hard, right?
In this session I will talk about the problems I faced building this feature, and what my team and I did to overcome them. It took multiple PRs, fruitless experimentation with JS hooks, and a team-wide hackathon - but we got there in the end! These are my key takeaways for those who want to take advantage of all the great features LiveView has to offer, and build some really cool and complex stuff.