…Or how to deal with code quality through Game of Thrones On 11th July we congregated to enjoy the last talk of the summer, from the BADG (Barcelona Android Developer Group) meetup in our eDreams ODIGEO canteen. Even though this Meetup group is Android-oriented, our last talk was more about how to deal with code
Some of us Java-users within eDO had the chance to attend to the latest edition of BCN Java Conf and now it’s time to reflect on our experience. The event was divided into three key areas: Methodologies and processes Cloud and microservices Java world novelties I have to admit straight up – after several years
Some context before we begin. At eDreams ODIGEO, the iOS team is fully committed to testing and making the clean architecture of our iOS apps. We use VIPER architecture because it perfectly fits our needs. We are quite a big team, and with this architecture we are able to reach a homogeneous codebase, being able
So let’s talk about a sensitive subject… What’s the point of WIP (work in progress) limits? More precisely why do we have WIP limits on our Kanban boards? Surely we should be able to work on the tickets that are most important and be “flexible” enough to switch our focus should we need to.
We all know that writing good software is tough and difficult, it’s not only about functional requirements, but also about robustness, maintainability, scalability and testability. In the android native team at eDreams ODIGEO, we researched about which architecture could be the best to solve our problems and to help us deliver quality software. Here is
Building top-tier software is a must at eDreams ODIGEO (eDO henceforth). Thus, in our strive to reach the highest quality for end-users, we try to apply top standards in our product. This effort is coal-and-ice in every single area of our development process, but there is a special section where it stands out even more,
Tests are key to deliver good quality to the customer, which of course is one of our main focuses. But testing this by hand usually takes too much time, time in which the customer is not benefiting from your feature. In this article we explain how we automated most of our tests of the Front-end with the help of Selenium, Cucumber and NodeJS among other technologies, which gave us the ability to speed up a lot the number of releases and time to market.
We are excited to release TableViewKit 1.0 – an open source framework which is a core part of our apps: eDreams, Opodo, GO Voyages (and soon Travellink). The framework allowed the eDreams ODIGEO iOS mobile team to set up a complex layout easily, while improving the modularity of our codebase. History TableViewKit was developed to
Concepts like continuous delivery, time to market or innovation are very important at eDreams ODIGEO (eDO). Working on a product like ours makes us focus on the customer. This means that we want to bring the features to them as soon as we can. The present article covers how we manage each release in the front end team and the challenges we face to take decisions around it.
