Matteo Emili
Director of Software Engineering @ Avanade UK & Ireland
London, United Kingdom
Matteo Emili is a Director of Software Engineering at Avanade UK and Ireland, leading the talent in Software Engineering and always looking at new ways of applying technology to solve business problems.
He is a passionate Agile advocate and a technologist at heart, a Cloud Architect who is always driven by using technology as a vehicle for change and continuous improvement.
A Microsoft MVP since 2010 (currently in the Azure DevOps and GitHub category), he enjoys sharing back as much as he can with the worldwide technical communities – especially about Agile and DevOps.
He founded several User Groups around Europe and he is a regular speaker at meetups and conferences.
Awards
Area of Expertise
Topics
Easy feature flags with Azure App Configuration
I am sure you hear it all the time - Continuous Deployment to production, silent releases, etc. However you never managed to do it, and you don't want to get onto yet another tool. How about an Azure native product? Let's have a look at Azure App Configuration and how it can help you deploying that first Feature Flag!
What did it mean bringing Inner Source in an Enterprise?
So many know the drill - a centre of excellence is stood up, some code and recommendations come out of it, nobody really uses it, back to the usual in a year or so. It happens very often in large enterprises trying to reinvent the engineering function
With this session though I am not here to complain or talk about failed attempts - I want to talk about an actual success story which absorbed over a year of my life (and it's still ongoing!), which led to a well-oiled Inner Source product in a large enterprise as well as a number of examples of collaborative development in a non-IT organisation.
It's been a journey, long and with mistakes, however successful in the end! Let's see how.
It's not my code! Secure software supply chain in practice
We think too often about 'secure code' being only about our code. Dependencies are the most common vehicle for attacks in enterprise systems, however it doesn't end there...there is so much more that we consume, and we usually just trust without questions!
Let's take a look at how we can secure our software supply chain, and prevent what could easily turn into disaster.
GitHub Advanced Security for Azure DevOps - better together
Secret scanning? Check. Dependency Management? Check. Static Code Analysis? Check. You manage your secure software development platform, right?
If you are an organisation using Azure DevOps is highly likely that you either have a mash-up of tools making up your development platform, or you are shortly going to look at one, because you know how important it is. It is however quite tricky to get right and there are a number of pitfalls in successfully setting up one, given the lack of standard offerings.
Microsoft recently announced the long-awaited release of GitHub Advanced Security for Azure DevOps, bridging a long-time gap of the platform. Let's have a look at how this changes the game in the secure DevOps space!
DevSecOps...do you really need DevSecOps?!
It’s all about labels these days – AI, Containers, DevSecOps. Many people claim to ‘do it’, very few *actually* do. And unfortunately, organisations suffer about this label-driven development.
Take DevSecOps for example: on face value it’s about adding Security practices to DevOps. But how do you measure the value derived from it? And also – how do you make sure you are not disrupting your team in the process? And if you already have an established DevOps practice, what's going to change?
In this session we will see why you don’t need a label to add these practices, and how to introduce sustainable solutions to implement in your build and release pipelines in order to achieve a higher security standard across your projects without hampering your teams.
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