Adele Carpenter

Adele Carpenter

Software engineer at Trifork Amsterdam

Amsterdam, The Netherlands


Adele is a software engineer at Trifork Amsterdam, where she is working on backend systems for the educational sector. Most of her work day is spent in the JVM/Spring ecosystems. Adele got the coding bug later in life but since then has been making up for lost time, going from command line noob to employed software engineer in just one year. Her experiences both in and out of tech have given her a unique perspective on the art of programming together with humans, which she hopes is useful to other humans who program with humans.


  • Most Active Speaker 2022

Area of Expertise

  • Information & Communications Technology


  • Software Engineering
  • 🙋 Soft skills for developers
  • Engineering Culture

Are Rewrites always a Bad Idea?

It’s an age-old story. Dev meets legacy code base. Dev gets frustrated. Dev embarks on rewrite. Company spends money. Rewrite fails. Legacy stays in production.

Ask most senior developers and they will tell you that a rewrite is rarely a good idea. And they’re right. But under what circumstances is a rewrite actually the best path forward?

I faced this question with my team in a recent customer project. We were responsible for running and maintaining a service written by an academic in C++. The only problem? We are neither academics nor C++ developers. With the customer keen to add features to the ageing service, we asked ourselves, do we dare to rewrite?

In this talk I will share my experiences on this project, including what it was like to take my first steps into a leadership role simply because I knew the most math.

Using this project as a backdrop, this talk will cover

- When a rewrite can be a good idea
- Choosing the tech stack
- Taking a leadership role as a junior dev
- Geeky stuff from the domain: turning academia into code

Mayday! Software lessons from aviation disasters.

What can aviation teach us about software? More acutely, what can aviation disasters teach us? Aviation is an industry that has committed to relentlessly learning from its mistakes, in the name of making the skies safer. Where the cost of the next iteration is potentially counted in human lives, then that relentlessness is not seen as a noble commitment but rather as the bare minimum. As software professionals, we have it easy. The costs of our decisions and failures are far far lower. For now.

As software permeates ever wider through our lives, the cost of failure gets higher. Societies are becoming cashless, and doctors are carrying a different kind of tablet. Smart phones have led us to smart homes. In a world where everything is connected, it’s time to learn from the industries where disasters are avoided at all costs. And in the face of disaster, instinctively running toward scrutiny rather than away from it.

This talk is not doom and gloom. It is a practical look at the methods and insights that almost 100 years of investigating commercial aviation disasters can teach us as software engineers.

A Teacher, an Economist and a Developer Walk Into a Bar

Have you ever wondered what a teacher, actor or economist could teach you about software development?

As software developers, we often lean on heuristics and truths that we collect throughout our career. For example: start small and scale up later, iterate and ship often, failure is learning, good enough is good enough. These are actually pretty powerful insights that can be applied in other areas and not just in software development.

So what about these other areas, like teaching, economics and acting? What do people in these industries and professions just “know”? And can we apply it to software development?

This talk takes a lighthearted look at several different professions and pulls these insights together to offer you a fresh perspective on your work.

Mayday Mark 2! More Software Lessons From Aviation Disasters.

What can aviation teach us about software? More specifically, what can aviation disasters teach us?

A lot actually.

In the first edition of this talk, I focused on the human factor of aviation disasters. An important element of both software engineering and aviation. But that is just the tip of the iceberg.

In this talk, I will go deeper into the technical oddities of some of the most famous aviation disasters. Buckle up for more case studies, more geeky stuff, and yeah, also some more human stuff.

We will cover
- Most common causes of aviation disasters and how that has changed over time
- Redundancy in systems
- Deadly UX
- Project failures and (wrong) incentives

Despite the subject matter, this talk is not doom and gloom. It is a practical look at the methods and insights that almost 100 years of investigating commercial aviation disasters can teach us as software engineers.

Copenhagen Developers Festival 2024 Sessionize Event Upcoming

August 2024 Copenhagen, Denmark

NDC Oslo 2024 Sessionize Event

June 2024 Oslo, Norway

Techorama 2024 Belgium Sessionize Event

May 2024 Antwerpen, Belgium

CloudBrew 2023 - A two-day Microsoft Azure event Sessionize Event

December 2023 Mechelen, Belgium

NDC Porto 2023 Sessionize Event

October 2023 Porto, Portugal

NDC Oslo 2023 Sessionize Event

May 2023 Oslo, Norway

CloudBrew 2022 - A two-day Microsoft Azure event Sessionize Event

November 2022 Mechelen, Belgium

Build Stuff 2022 Lithuania Sessionize Event

November 2022 Vilnius, Lithuania

NDC Sydney 2022 Sessionize Event

October 2022 Sydney, Australia

NDC London 2022 Sessionize Event

May 2022 London, United Kingdom

Microsoft JDConf 2022 Sessionize Event

May 2022

droidcon London 2021 Sessionize Event

October 2021 London, United Kingdom

JNation 2021 Sessionize Event

June 2021

Adele Carpenter

Software engineer at Trifork Amsterdam

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