Alex started out on the YoppWorks team right from Carleton University, in January 2020. He’s extremely eager to learn and spent a couple of months taking Lightbend courses and Martin Odersky’s Coursera course. He quickly joined in on a project and now six months in, he’s already on his third project with us. He works on both back-end Scala and front-end ReactJS, and humbles us by saying, “I get to end each day with the satisfaction of having built a piece of something great with a great team!”
- What is the biggest misconception of a reactive architecture system?
The biggest misconception of a reactive architecture system is that having many microservices is worse than having all your code in one place. In reality, it helps with deployment and resilience to have microservices.
- What are the advantages of using OSS (open source software)?
The main advantage of using OSS is not having to worry about paying for anything, but depending on how popular an OSS library is it can also have the advantage of more frequent and robust releases with various alternate libraries for different use cases.
- What would you say is the number 1 business value gain from moving to a reactive architecture?
The number 1 business value gain from moving to a reactive architecture is reactivity. You get responsiveness and resilience in one package – what’s not to love?
- What would you say are your top 5 benefits of an agile environment?
- Flexibility – agile environments let development teams have more flexibility in deciding what to work on. While business concerns are always important, it is also important for the developers to be able to pivot to tech debt items when necessary, and to be able to work on small tasks when they are overwhelmed with the big ones
- Delivery – agile environments allow for quicker delivery through a principle of breaking down large tasks into smaller, more manageable portions
- Team Cohesion – standups are a great way to make the team feel involved in each others’ work, and to let people who have been working on their own on a story to inform the team on their progress
- Retrospective – by having a retrospective meeting every Friday we are able to more accurately assess our progress, and it gives us an opportunity to discuss issues or blind spots that the team is be dealing with
- Collaboration – while it is not an element of every agile team, collaboration among developers can really help the whole process come together. It is important for the team to utilize each others’ strengths and expertise to more efficiently tackle stories and bugs
- What is one thing you are most excited about in the tech industry for the near future?
Chatbots, especially in the field of mental health. While they are still far from ready for the task of administering mental health analysis and advice I believe that a chatbot that could replace a therapist and/or psychiatrist would revolutionize the industry, mostly in terms of access.
- What do you like about working at YoppWorks?
The best thing about working at YoppWorks is the team. Everyone is easy to approach and work with, everyone is highly skilled, and we have a lot of fun!