Berlin Software Designers

We will solve this system design exercise: LeetCode

Organization:

• we read the requirements
• we do the class design individually, in 20 minutes
• we present our designs, and discuss them
• we write the pseudo code for the most important logic, individually, in 20 minutes
• we present our pseudo code
• we read the follow up questions, and discuss them together

Requirements:

• do not join if your microphone does not work
• have at least a basic understanding of one programming language, and about object oriented programming
• you are willing to commit 2 hours of your time

This meetup follows the Reddit tutorial "How to Find the Stinky Parts of Your Code" and uses its catalog of code smells as a structured learning exercise.

For the first 3 hours, participants work through a series of short rounds:

• Read a code smell individually (10 minutes)
• One participant is selected at random
• The selected participant explains the smell to the group (5 minutes)

All participants must be willing to present the code smell they have just read, as anyone may be selected during a round.

In the final hour, we will collaboratively build a Claude Code review command that uses code smells as review criteria to identify maintainability and design issues in real codebases.