FooConf Program Committee will select the talks and elaborate the program of FooConf Second Edition. Led by Erno Kurki and Mattias Karlsson.

Mattias Karlsson
fooConf

Mattias spends his time working with software development since 1993 and leading a JUG in Stockholm, Sweden. Through the years he has gained experience from many different roles, including developer, architect, team leader, coach, manager, and teacher. Mattias also wrote a chapter in the "97 Things Every Programmer Should Know" about Code Reviews. Mattias founded Jfokus together with community friends in 2007. In his spare time, Mattias can be found snowboarding and riding his motorcycle.

Welcome and Introduction

Erno Kurki
fooConf

Multidisciplinary Technologist with 16 years worth of continuous learning on how to deliver business critical systems. Broad perspective in to the cloud industry and where the technology is heading. Experience in designing sustainable software delivery and in facilitating a globally distributed DevOps operation.

Welcome and Introduction

Aki Ristkari
Reaktor

Annie Talvasto
VSHN

Jari Timonen
Codento

Juho Vepsäläinen
Aalto University

Juho Vepsäläinen is behind the SurviveJS effort. He has been active in the open source scene since the early 2000s and participated in projects like Blender and webpack as a core team member.

Juho lives in Rautalampi, Finland, and was chosen as the Finnish Code Ambassador of 2017 by Blue Arrow Awards. He is the director of React Finland.

Maaret Pyhäjärvi
Vaisala Oyj

Maaret Pyhäjärvi is an exploratory tester extraordinaire with a day-job at Vaisala as Principal Test Engineer. She is a tester, (polyglot) programmer, speaker, author, and a community facilitator. She has been awarded prestigious testing awards, Most Influential Agile Testing Professional Person 2016 (MIATPP) and EuroSTAR Testing Excellence Award (2020), Tester Worth Appreciating (2022), and selected as Top-100 Most Influential in ICT in Finland 2019-2021.

Marcia Villalba
AWS

Matias Huhta
Simplr Oy

Matias is a enthusiastic Software Developer who loves working with developer tooling. He's an active member of Open Source communities focused on Web Components and has worked on projects like the Web Component DevTools and is currently building a Language Server for Custom Elements.

Matias aims to ease the day to day development experience of developers around the world while also making the experience as enjoyable and fun as possible.

Melissa McKay
JFrog

Melissa’s career as a developer and software engineer spans over 20 years, and her experience spans a slew of technologies and tools used in the development and operation of enterprise products and services. She is passionate about Java and DevOps, and is currently a Developer Advocate with the JFrog Developer Relations team. She is a Java Champion, Docker Captain, co-author of the book DevOps Tools for Java Developers, and an international speaker at numerous software conferences. Melissa is active in the developer community, currently serving on the Continuous Delivery Foundation TOC and as a Co-Chair of  the CDF Interoperability SIG.

Don’t Expect Developers to be Security Experts!

Developers are not security experts! I’ve heard this exclamation time and again and I wonder, why not? And should they be?

There is no denying that software teams must work to address a number of security concerns today. But we’re still learning and actively developing best practices. We’re still figuring out — sometimes through trial and error — the best way to tackle security issues that won’t negatively interfere with delivering functional (and secure) software.

When it comes to developers securing software, there is only a subset of prevention and mitigation strategies that make sense to put on a developer’s plate. Even then, an expectation that all developers by default are equipped to handle this additional workload is unreasonable.

This session is targeted toward developers and anyone wanting to improve or prevent circumstances that send many devs hurtling toward burnout. I will include explanations of security related terms and lingo that are streaming into our development environments; share typical places a developer needs to look to shore up applications including dependencies, packaging, and supply chain concerns; and discuss the plethora of scanning tools available to developers today and how they work. You will learn how to integrate a measure of security that makes sense into your already existing development processes and how to introduce a security culture to your development team in a healthy way. Leave with a better understanding of application security needed from a developer’s perspective, some stats to plead your case if needed, and a sense of empowerment.

Most importantly, don’t lose heart! We’re getting better and better at this and the future looks bright!

Read more

Mohammed Aboullaite
Spotify

Mohammed is a community catalyst, a true open source believer and has contributed to various open source projects. He currently works at  Spotify as a Backend engineer

Theresa Mammarella
Software engineer

Thomas Raehalme
Admicom Oy