At Thinksurance, we build technology solutions helping distributors and insurers to fully digitize the distribution journey to save valuable time and increase productivity. For our partners to be able to use our technology simply and easily, we need a user-friendly interface. That’s why we have a team of highly qualified developers on board. One of them is Dragan Lalos. He is the technical lead of our frontend team at Thinksurance. Today we’ve asked Dragan some either or questions. Let’s see which technical tools he prefers.

Dragan is an expert in advanced development methodologies, tools, and processes contributing to the design and rollout of cutting-edge software applications. The innovative software engineer with over ten years of experience in the full software development lifecycle is the Technical Lead at Thinksurance. Dragan is responsible for the frontend development team, separating the frontend into the SPA and providing a new architecture for React applications with the new design system.

Dragan, in your opinion, what is cooler: Frontend or backend development?

I have to say frontend because this is what I’m passionate about, haha. But from day one on, I have been working very closely with the backend developers. At the beginning of my career, I was a backend developer, but at the time backend and frontend were actually one, a so-called monolithic application. Then IT architecture started to change and was split into frontend and backend. I joined Thinksurance to follow this change in IT structure and to build a frontend team from the ground. Now we’re five people in the frontend team and still growing.

And I, personally, love frontend development because the work is very creative, and has a huge communication part. The reason for that: We work closely together with other colleagues who are not necessarily in IT to create the best and most suitable end product for our partners and users. I enjoy this interaction and exchange a lot.

What is your favorite kind of architecture in frontend: Monolith or Micro Frontend?

At Thinksurance, for frontend architecture, we use Micro Frontend architecture. But as we always want to use the newest and best tools, we have gone one step further. For example, we work with module federation to reuse as much code as possible to be able to build our applications rapidly.

This is what I really love about the company. We from the IT department have the freedom to work independently. When there is a problem, of course, we discuss what’s the best solution. But, in the end, we are free to choose how to solve the issue. Our team really trusts us, we’re seen as the real experts. In this way, we have the full freedom to express ourselves and also grow personally.

To sum it up: Here at Thinksurance, we are real engineers and create things that have never been done before. That’s what I love about working here. Plus, in our daily work, there are a lot of challenges – it never gets boring and we’re always challenged.

Which framework tool do you use: React or Angular?

React! In frontend development, we work with React, because it’s a library. With this tool, we have more freedom and flexibility to choose other libraries which we would like to work with and can then include. There are millions of combinations to implement. Besides, there is a strong community behind it that is active and loves to cooperate regularly. So, it’s easier to find solutions for problems and to discuss and share opinions. The idea of React gives us more freedom and options in the composition of our teams. For example, we can easily set up a small team for a sprint. With Angular, on the other hand, it requires teams with more colleagues, because it is a framework. So, we are also more agile in our work here.

Developer-Drink-Question: Mate or coffee?

Definitely Mate because I, personally, don’t drink coffee. But, in general, we in the IT field are often really addicted to energy drinks I think, haha.

Please answer: "I love working at Thinksurance because …"

… we develop crazy new stuff. All we need, we develop ourselves and we always think in new ways. This is what I love about our team. We are no followers, we are creators and problem-solvers and I guess this makes us all kind of cool, right?