7 Tips to Pimp Your Git History by Roland Weisleder

Software often lasts longer than expected. Software is also changing more often than expected. At some point, there comes a moment where a developer looks at the code and asks: “How is this piece of code supposed to work?” A look into the git history is also not very helpful with messages like "fixed some bugs". This session will show some tips on how to create a comprehensible git history and what the benefits are. After this session, participants will know what to look for in their daily work with Git, and how they should use Git, so that changes to the code are still comprehensible months or years later. Roland Weisleder is a software engineer and architect working at data experts in Berlin. His focus is on creating and maintaining long-living enterprise applications in the Java ecosystem. As head of the company's technology board, he also advises the individual project teams on current technologies, techniques and trends.