About us
Welcome to Berlin Software Design — a community for engineers and architects who want to sharpen their software design and architecture skills through practice, discussion, and collaboration.
We focus on learning by doing: software architecture katas, design challenges, system walkthroughs, and peer feedback sessions. Each meetup is a chance to tackle real-world design problems, share approaches, and improve how we think and communicate about architecture.
Whether you're an experienced architect or a developer curious about system design, join us to grow your skills, exchange ideas, and connect with like-minded tech professionals in Berlin.
Upcoming events
3
![[pair programming] code review random Golang repositories](https://secure.meetupstatic.com/photos/event/6/f/7/a/highres_531028538.jpeg)
[pair programming] code review random Golang repositories
·OnlineOnlineWe read small github repositories, and try to understand the code and what design decisions were behind it.
Here is a list of such small Golang apps, you can add your own to it:
- https://github.com/chinmay-sawant/gopdfsuit
- https://github.com/bevane/repocheck
- https://github.com/saravanasai/goqueue
- https://github.com/golang/groupcache
- https://github.com/olric-data/olric
- https://github.com/hashicorp/memberlist
- https://github.com/dgryski/go-shardedkv/tree/master
- https://github.com/dgraph-io/ristretto
Together, we’ll:
- Read and understand the code
- Discuss the architectural decisions/its design
- Write some Architecture Decision Records (ADRs)
- Draw a class diagram and a C4 diargram
- Decide what testing strategy the repo should have
- Discuss pros and cons of the current implementation
It’s a great way to sharpen your architecture skills and see how others design and structure their systems.
No prep needed — just bring your curiosity and your intuition.
25 attendees![[system design] Tinder](https://secure.meetupstatic.com/photos/event/7/6/9/7/highres_530850359.jpeg)
[system design] Tinder
·OnlineOnlineWe will solve this system design exercise: Tinder
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
30 attendees[system design] LeetCode
·OnlineOnlineWe 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
30 attendees
Past events
55
![[face to face] professional communication exercise](https://secure.meetupstatic.com/photos/event/2/4/d/highres_531120589.jpeg)
