Throughout two weeks, we will address the question of how resource-efficient software engineering works. At the end of each week, you will get the chance to test your knowledge gathered in the course with the help of self-tests and homework.

Week 1: In the first week, we will see what the ecological footprint of digitization is. We'll discuss how digitization helps to save CO2, and also also see where IT causes CO2. Next, we will take a closer look at the roles that commonly exist in the IT industry (e. g. developer, IT architect, leader) to identify which opportunities for resource-efficient actions exist in each role.

Topics:

• CO2 savings with IT, CO2 consumption caused by IT
• Basic concepts
• Perspectives of different roles: users, architects, developers, leaders, regulatory framework

Week 2: Based on the fundamentals learned in week 1, we'll discuss which barriers exist that hinder us from acting more ecologically in the process of software development. Then we'll see how we can overcome these barriers and find solutions. The main part of the second week covers solutions, i. e. examples to show what a developer in particular can do in the development of his software to act in the most climate-friendly way possible.

Topics:

• Barriers and solution strategies for sustainable digitalization
• Choice of technology
• Software & system architecture
• Computational complexity
• Data structures
• Storage and network
• Caching

Key data on the course:

• Required skills: general IT knowledge, solid mathematical knowledge, basic knowledge of programming in Python. By the way, we use Python in the course not because it's particulary efficient, but because many people know it.
• Course level: Basic, but the course also goes in-depth
• Target group: Everyone interested in sustainable software engineering
• Effort: 3-6 hours per course week