👋 I’m Riccardo. I am an engineer.

I joined as senior developer to help on the booking flow application: this is a high traffic, high performance application that is deployed multiple times a day and fully tested (including performance with Lighthouse) on every deployment.

In addition to working on new features and helping more junior developers, I worked as developer advocate to progress key initiatives across teams. These include: a new design system able to pull data directly from Figma, a visual regression test tool based on Backstop.js that is currently part of all our frontend applications. These improvements helped massively with developer confidence and produced more production deployments as a final result.

I am currently working on rebuilding the “Manage my bookings” application from scratch, for web and native apps.

At Viable Data I looked after a range of JavaScript applications for the Home Office, helped with technical direction for new features and mentored more junior developers.

I joined to help shape the new micro front end architecture, part of the wider re-platforming of Burberry’s ecom. During my contract I led two of our distributed teams of developers, located in Minsk and Shanghai, while working with stakeholders and designers in-house. Day to day activities with the team included working on stories, mentoring other team members, reviewing merge requests, working with the BA to review stories and prepare sprint goals and working with the designers to make sure all the edge cases were covered.

Particular focus was also put on working with across-teams to agree on high level solutions and create a consistent development workflow. Consistency and simplicity were key, to ensure that the cognitive load was kept to a minimum and the code produced would follow our standards regardless of where it was produced.

As part of my assignment, I also worked closely with the design team to help build the company’s design system: from defining the key strategy and technologies to use to building a set of design tokens to be used across web, email and native apps.

As Team Lead I focussed on Trainline’s re-platforming (going from monolithic .NET backend and React FE to .NET microservices and Node/React micro-frontends). As part of the role, I helped creating a new team, made the required hirings and worked more with POs/BAs. I kept my position strongly technical (at least 70% coding).

My impact area widened, focusing on giving the team the stability and continuity needed to deliver high-quality software respecting the company’s deadlines. Given the small size of the squad, this was achieved by wearing different hats at different times, to ensure that all the required functions were present when needed: helping with BA functions, technical recruiting and DevOps work, driving innovation to support the product (“3G days”, “No Chrome days”), mentorship and internal growth and working cross-team to exchange knowledge and drive the development forward.

I joined to help shape a better agile process, help junior developers to step up and ensure a more predictable, high-quality development process.

In pursuing the above, we stabilized the agile process by streamlining the ceremonies, hired more junior members and turned them into mid-level engineer, introduced cross-device integration tests and removed all manual QA-ing, introduced bug hunts/manual discoveries, improved the code reviewing process, allowing the developers more time to review, discuss and deliver better code.

I also worked across our projects with micro/macro refactorings to increase code quality and encourage reusability and helped the HR hiring team to create a better tech hiring process.

As Team Lead my goal was to give our UI teams a long term vision. Apart from developing (I spent at least 70% of my time developing with the team) I then invested more time on new technologies, best practices and patterns to use across our teams and improved ways of managing our workflows.

Part of the improvements put in place include:

• strict use of Git merge requests/code reviews (with auto merge request builder)
• a fully automated cloud CI for all our four environments a “dockerized” version of our apps to make it easy to test and deploy everywhere
• monthly meeting with back-end devs, tech ops and architect to give all developers a big picture of our projects.
• hosting a Js meetup (http://www.meetup.com/js-monthly-london/) in our London office

I led UI teams in our London and Madrid offices and was also involved in various social activities to bring developers together: brown bag sessions, meetups, team conference calls.

I worked on the m.lastminute.com mobile application, supported junior developers and spread the knowledge across the teams with tech meetings about good practices and new technologies to introduce in our workflow.

We worked in a Kanban environment, following a TDD/BDD approach in teams with PO, BAs, marketing people, QAs, UI designers, back end developers and front end developers. My focus was on the Backbone Mobile SPA application.

Responsible for the development and maintenance of our web applications: working closely with our team of business analysts, designers, backend developers and QAs in an Agile team. My job involved writing JavaScript libraries to be used across the apps, turning PSD designs into semantic HTML5 applications; adding complex interactions handled with the best JavaScript tools and frameworks, always creating modular and maintainable code even with tight schedules.

I improved the front end workflow by introducing an automated flow for the development: with Grunt.js, we now automate the whole process. From a morning job that takes care of updating the local repository, builds and the deploys the app; to a watcher that lints, checks the coding style with jscs, tests and concatenates + minify and deploy at every file save. I automated the documentation process creating a live styleguide with KSS.

In our Agile environment we used Jira to handle our sprints’ workflow and Jenkins to build, deploy and test our code.

I worked with KLM for the Unavolta project. Unavolta.net is a web application (both desktop and mobile versions available) designed to let people upload their travel photos (with a poetic message) in order to participate in a contest and win a flight. Additionally, every week (for eight weeks) a new video is published to inspire travellers. My responsibility for the project was to design and develop the mobile interface.

During my career at Prometeo I had the chance to work on a wide range of projects: from building a complete server rack to implementing a site crawler using the Selenium API to designing and developing web applications using multiple different technologies. My responsibilities included: gathering user requirements, choosing the right technologies to use, implementing server and client side code, testing and production deployment. I was involved in the R&D area too: building and testing new technologies for upcoming projects.