
Sign up to save your podcasts
Or


In der Software-Entwicklung sind zahlreiche Gruppen unterrepräsentiert. Bei diesem Panel wollen wir diskutieren, wie Diversity erhöht werden kann.
Diversity mit Lars Hupel, Lena Kraaz und Aminata Sidibe
Die Klima-Katastrophe ist eine der wichtigsten Herausforderungen, denen wir uns stellen müssen. Dieses Panel diskutiert, was Software-Entwicklung dazu beitragen kann.
Links
SoftAWERE: Tools and Labels for Energy-efficient Software Applications scaph repl schnittstelle
Scaphandre: metrology agent dedicated to electrical power consumption metrics
Intel RAPL
Intel: Running Average Power Limit Energy Reporting
Stackoverflow: How does Intel’s RAPL estimate the power consumption?
Reading RAPL energy measurements from Linux
Intel Open Source Blog zu RAPL
EET: A Device to Support the Measurement of Software Consumption
Buch: Software Sustainability mit einem Kapitel von Jutta
Umweltbundesamt: KPI4DCE: Das ressourceneffiziente Rechenzentrum – Kennzahlen und Indikatoren
Umweltbundesamt zu KPI3DCE 2.0
Open Source Library für das Messen von Strom/Embedded CO2 einer Server-Side Software Anwendung von Max
Code Repository
Blog
The Hippocratic License Hippocratic - An Ethical License for Open Source Projects
Developers for Future
Artikel in der c’t zum Thema
Episode zu Klimawandel & Software Architektur mit Martin Lippert und Stefan Roock
Resiliente Organisation und resiliente Software-Architektur: Die Organisation hat großen Einfluss auf die Architektur. Wie kann man sich diesen Zusammenhang zu Nutze machen?
Links
Daten beispielsweise lokal zu kopieren, um offline zu arbeiten, ist eine Herausforderung. Wir diskutieren, wie man sie meistern kann.
Links
Wir kennen alle DevOps - aber was ist DevSecOps und warum gehört ausgerechnet Sicherheit dazu?#
Thoughtworks Technology Radar
Technical debt is a well-known concept - but data can also cause technical debt.
Links
Data Technical Debt
Refactoring Databases
Agile Data Homepage
Testing alone is not enough - the alternative is quality engineering.
Links
Software is developed in teams so design decision must be done collaboratively.
Links
Book: Jitske Kramer - Jam Cultures: About Inclusion; Joining in the Action, Conversation and Decisions
Book: Sam Kaner - Facilitator’s Guide to Participatory Decision-Making
Book: Thomas Wedell-Wedellsborg - What’s Your Problem?: To Solve Your Toughest Problems, Change the Problems You Solve
Blog: Rebecca Wirfs-Brock: Architecture Decisions Should Be Made At the Last Responsible Moment
Sketchnote: Dale Carnegie: How to Win Friends and Influence People
The SOLID principles are well-established as the foundation of object-oriented systems. However, after more than 20 years it is time to see whether the principles still apply and whether other concepts might be a better alternative. Daniel Terhorst-North is well known for concepts like behavior-driven development or deliberate discovery. He came up with the CUPID principles. In this episode, we will discuss SOLID and CUPID - and why Daniel thinks CUPID makes more sense.
Links
Slides for Daniel’s presentation “Why Every Element of Solid is Wrong”
Slides for Daniel’s presentation “CUPID for Joyful Coding”
Daniel’s Homepage
CUPID - the Back Story
Advent of Code
Kevlin Henney’s talk “SOLID Deconstruction”
Daniel’s talk “Decisions, Decisions
Daniel’s talk “Decisions, Decisions at InfoQ
Book How Google Tests Software
Many teams work on monolithic applications but want to migrate to a modern, shiny microservices architecture. Sam Newman is the author of the most popular book about microservices and has recently published a new book about the migration from monolith to microservices. We will talk about how to migrate to microservices - and why microservices should often only be used as a last resort.
Links
From the publisher's feed

9 Listeners

223 Listeners

8 Listeners

3 Listeners

6 Listeners

2 Listeners

1 Listeners

181 Listeners

3 Listeners

6 Listeners

17 Listeners

319 Listeners

20 Listeners

3 Listeners

8 Listeners