TrailheaDX is the Salesforce developer conference. It was held in San Francisco on the 28th and 29th of June, in the Moscone West Center. The number of attendees has quadrupled from last year, with people coming from all around the world, as my colleague and myself traveled from Málaga (Spain).
This conference was born after the demands from Salesforce developers of having their own event. It is true that there is a zone at Dreamforce for developers, but that was not enough for us, and finally our demands were listened to and Salesforce created this amazing conference.
One thing to note about TrailheaDX is that the people giving the talks are product managers, directors or engineers working directly with the products, so you have first hand information.
There were more than 180 sessions to cover multiple and diverse topics. 3 key areas led the whole conference and were highlighted during the opening keynote with amazing demos run by Leah McGowen-Hare (Director of employee and Trailhead content strategy) and Sarah Joyce Franklin (SVP Dev Relations & DM Trailhead). The demos are already online, check this powerful demo of Einstein and this one about Salesforce DX both run by Leah McGowen-Hare, and also this one about Platform Events run by Sarah Franklin.
If you have ever worked with a team of UX Designers, I’m sure you have heard about the term Persona. A Persona is simply a semi-fictional character that stereotypes your user. It doesn’t sound that useful, does it? Indeed, personas are fairly irrelevant but we still need to talk about them because they are the perfect excuse to drive effective User Research.
At Ebury we use Personas not just to understand how our current users are, but also to create solutions for the potential customer. This is why we take advantage of the Persona modelling process, as it gives us a better understanding of our customers’ needs.
At Ebury, we use Salesforce as our CRM but also as a reconciliation platform for our lending business; to manage our credit line requests, our margin calls, and our onboarding (KYC, AML) processes. But since standard functionality is not enough for us, we have a dedicated team specialised in force.com that builds customisation and applications for our different teams within the company. Our goal is to use this versatile framework to build features that make our sales process quick and effective, and to help our Operation teams to be focused on what is really important for us, our clients, and let the system take care of the rest.
We applied to be one of the lucky members to be part of the Salesforce DX Pilot and we were selected! Salesforce DX Pilot started on the 22nd of February and it is still going on, but I wanted to share with you my impressions so far.
Recently, we have built out a cool interactive map displaying the payments and capabilities coverage of Ebury for our corporate website using CARTO.
We will walk you through all the stages of development that we made and point you at the source code of our project GitHub.
By applying the micro-services philosophy, we decided to develop it in a separate project, so we began to analyse the tech stack to be used.
We took a look at tools like Google Maps or Leaflet, which are great for displaying maps, but it was not easy to display the data in the way we wanted. We then played around with D3.js, a great library for visualising data. However, it was not straightforward to implement a map with standard controls such as zoom or the drag feature.
Finally, we found CARTO that offered the best functions out of all of the options which made it super easy to create this map.
This week we completed the second edition of the Malaga Agile Meetup. This time, we held a Lean Coffee meeting. Once again, the attendance was incredible; the 30 available seats were filled in a short time and the waiting list was growing right up until the day of the event. Our agile community continues to grow – currently, we have 141 enthusiasts.
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.