
![[pair programming] code review random Java git repositories64335941046529120](https://secure.meetupstatic.com/photos/event/6/f/7/a/highres_531028538.jpeg)
We read small github repositories, and try to understand the code and what design decisions were behind it. Here is a list of such small Java apps, you can add your own to it: \- https://gitlab\.com/burak\-dev/url\-shortener \- https://github\.com/harismuneer/Library\-Management\-System\-JAVA \- https://github\.com/ebarlas/microhttp \- https://github\.com/bowbahdoe/json \- https://github\.com/bowbahdoe/regex\-router \- https://github\.com/joel\-jeremy/externalized\-properties \- https://github\.com/joel\-jeremy/deezpatch 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.
