Speaker

Alessandro Mautone

Alessandro Mautone

Lead Android Engineer @Canyon

Amsterdam, The Netherlands

I started coding around the age of 18 and immediately fell in love with it. Since I was always passionate about mobile (first with Nokia and their Symbian and then with Android), it was natural for me to continue on that path. I started working in a small agency in South Italy where I had the opportunity to work on a lot of projects, then decided to expand my horizons and moved to Amsterdam where I started to work at WeTransfer. After almost 5 years there, I decided to pursue an industry I have at heart: bikes! And started working for Canyon.

Particular signs: I love sports in general, I am a regular runner and since love everything that flies I am a proud paraglider!

Area of Expertise

  • Information & Communications Technology

Topics

  • Android
  • Android Tools
  • Android Development
  • Automation & CI/CD
  • Automation
  • CI/CD
  • CI/CD Pipelines
  • Software Engineering
  • Soft Skills
  • DevOps

Tech scale up vs Traditional industries vs Agencies: The differences

Over my career, I had the opportunity to be exposed to many different industries and their relative behaviors. Reflecting on my previous and current professional journeys, I identified interesting patterns, often conflicting between different types of industries. In this talk we go through them and try to identify the reasons for those differences, and how to both approach and navigate them when jumping ships.

How to handle incidents at scale

In this session, I want to guide the audience into applying healthy processes to handle incidents. We have all probably been in the situation of having our apps unexpectedly crashing - either because of a bad release, because of unexpected Backend changes, etc.

In these scenarios, we usually get overwhelmed by messages from different departments (support folks, managers, and so on), this is especially true when operating at a large scale, and things can quickly get out of control.

This talk aims to propose rules that will not only mitigate the above scenarios but also improve the communication flow, give tips about how to set up alerting systems and what to measure, and talk about a "post-mortem" process.

This session mainly focuses on processes and refers to some soft tooling (chat services, simple bots, alerting systems), thus it doesn't require any particular technical skill. The preferred duration is ~20 mins and the target is mainly developers (of any platform really), DevOps and (technical) managers.

How to effectively create and review PRs

In this session I want to guide the audience in how to effectively create and review PRs. Creating them has a few tips like templates and ways of automating some tasks through GitHub.
The review part talks about how to approach a PR, how to dialog with the author keeping in mind empathy and the fact we are on the same team, and when to comment vs request changes vs approve.

This talk was presented at the droidcon Lisboa 2022 and will be presented at the Droidcon San Francisco 2022

🤖 Automating key workflows in your daily developer life!

CI/CD

In this talk, I want to guide the audience through the tools I implemented and the scripts I built over time in our CI system to automate common tasks like:
- Daily release deliveries to QA (releases run automatically only if there were any new commits since the last one)
- Automated Git(Hub) tags creation for each release
- Automated release notes included in the tags (for QA)
- Automated code formatting with standard rules automatically shared across all the members of a team

Bonus:
- How to have automated "feature resales"
- How to create those scripts in order to make them reusable across different projects.

I currently work with Bitrise, which means my example may include that tool (but the scripts are tool agnostic).

Unfortunately, the scripts I mention are not open source (yet, I have been very busy with work lately). Anyhow, that doesn't prevent me from sharing them in a live talk, and I am aiming to open-source them when time allows.

Here you can find an article I wrote a while ago about the automation of the release notes https://alessandromautone.medium.com/automated-release-notes-for-android-8e3a22d00156

And here a more recent one about how to deliver automated feature releases https://alessandromautone.medium.com/deliver-feature-and-regular-test-builds-through-the-google-play-store-5cc5d40fb3b5

Preferred format: 20 mins. But depending on how deep we go into the scripts/certain arguments it could be easily stretched to 30-40 mins.

Alessandro Mautone

Lead Android Engineer @Canyon

Amsterdam, The Netherlands

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top