Have a look at our ground breaking conference presentation here.
The HashCode challenge, a team-based programming competition organised by Google where people from Europe, the Middle-East and Africa try to solve a problem proposed by the company, took place during during the evening on the 23rd February, and Ebury was there to cover such an awesome event.
Our Malaga office was open for those who wanted to join us and have some fun between code lines, flowcharts, loops, and all things on which coding freaks like me enjoy spending time.
This time, Google asked us to create a solution to improve the performance of the way a video streaming platform delivers its videos to the end users: we were provided with several cache servers that were accessible from certain endpoints and we were able to improve the load time of a specific video if using them. In any one video, we have a file detailing how many end users are trying to watch it, how much time the platform takes to load that video (latency), what cache servers can their endpoints access, and what is the latency of each one (read the complete problem here).
After our agile adventure in Vitoria (CAS2016) we come back empowered and with a lot of energy to create an agile community in Málaga. Using this wave of power we decided to create the first Malaga Agile Meetup.
Our main objective with the meetup is to collect all the agile enthusiasts in Málaga with energy to meet frequently for talking about agile methodologies, team dynamics, and kaizen philosophy. We want to create an open space for everyone with inquietude to continue growing and learning new tools, concepts, and experiences.
The acceptance has been incredible. We currently have 103 members in the group, with only a few existence weeks.
The post is the second part of the Unit test execution (part 1) blog post published in October 2016. This time we will explain how to run Python tests with coverage using a distributed architecture to ensure things don’t take too long! We will describe step by step how and what we set up to achieve this. But first of all lets quickly define what we mean by test coverage.
We would like to share with you what we have learnt and to do that, we have created a presentation in HTML, CSS and JS using all the new and cool techniques that were presented in the conference!
On 30th November we had our latest agile adventure in Vitoria, Spain. We arrived there to attend the Agile Spanish Conference (CAS 2016) taking place on 1st and 2nd December. CAS is one of the biggest and most important meetings in Spain. This particular event gathered together many qualified professionals from the tech sector. We had the opportunity and also pleasure to meet them and to share our knowledge and personal experiences. The ‘sharing part’ is what we valued the most.
From the beginning of the times humanity has been able to do awesome things that made a big difference to the world: the discovery of fire, language, wheel, electricity, penicillin examples of the most important ones. These discoveries were made possible by people with a strong motivation.
Unless you’ve been in a cave for the last year, you may have noticed how “Serverless” is the new sticky word in the dev community and it’s like we’ve not had time to get used to the “Microservices” buzz. But don’t go crazy just yet, it’s not the time throw away your “still hot” blueprint of your architecture because a new trending topic has arrived. We decided to keep it cool and just experiment a little bit.
This blog describes how we used AWS Lambda and overcame some of its current limitations to solve a typical data processing pipeline problem.
Machine learning based lead generation, modelling stress scenarios through multi-correlated GBMs and Brownian bridges, forecasting credit defaults using random forests… I never expected our first Data Science post to be about measuring the weight of babies!
When we talk about Unit Tests we generally mean tests for individual units of source code as created as an outcome of Test Driven Development. But how can we apply this when we’re developing against areas of our code base that don’t have unit tests to start with, that is essentially Legacy code?
This post describes how we approached this problem in three phases.