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,
“How long will this take?”. How many times have you been asked this question? In this article I will try to help you thinking on this from a different perspective.
The Kanban method has become a key part of eDreams ODIGEO because of its evolutionary change approach. Kanban manages change by following these three principles: “Start with what you do now”, “Agree to pursue improvement through evolutionary change” and “Encourage acts of leadership at every level”. In this article I’ll introduce how we are doing this at eDreams ODIGEO.
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.
This year, eDreams ODIGEO had the pleasure of participating, encouraging and supporting some of the most exciting, well-known tech events in Europe: AppsWorld London, Productized Lisbon, Codemotion Madrid, Devoxx Antwerp to name just a few. Apart from that, locally, at our HQ in Barcelona, we have been facilitating several meetups for the local tech community.
The main goal of the OneCMS team in Alicante is to migrate the existing OdigeO CMS called ONECMS, which is developed using #NET, to the IT common, that means using Java and the jBoss platform. We call it jCMS. I would like to share the OneCMS team’s experience with Specification by example (SBE). After assisting
The Barcelona Java User Group (JUG) is a very active community and we are lucky to have among us one of their founders (David Villacampa) and one their core members and organizers (Adela Tort). The jBCNConf (http://www.jbcnconf.com/2016/) is the conference organized by the Barcelona JUG and this year was held on 16th to 18th of