Karsten Nowak
Preparing for the First Regular Best Practices Code Sprint
Monday morning, just before 11:00. The daily stand-up is done, and the day’s tasks are manageable. Good, because today marks the first of the Best Practices Team’s regular remote code sprints. A quick check — Slack, IDE, internet? All set. We’re online Let’s go!
Eike and I were well-prepared and on time for the Slack huddle of the Best Practices Team. Oli and Daniel were already there, in a great mood and motivated — just like us. Unfortunately, it was only the four of us, but finding time for these events isn’t always easy. So, we got started right away.
Kicking Off the Sprint: Tasks, Tools, and Teamwork
After a quick round of updates on Oli and Daniel had already set up a GitHub board with all the tasks clearly listed. I was shocked to realize that I still had an open pull request from last year — so I felt an urgent need to tackle this as my first task. I quickly incorporated Oli's comments and the pull request was merged. A nice win to start the day — motivating, for sure! Eike also had a lingering task to complete from last year which he quickly completed as well.
We then worked on an important ticket together as a team, also from last year, about automated testing in Gitlab and Github environments. Everyone was delighted that we were able to close this ticket and that the issue was finally resolved and tests could run again in full.
Collaborative Problem-Solving and Key Achievements
As always, Oli and Daniel focussed more their time on answering our questions and providing us with help and advice. Thanks to Slack, everything went smoothly. You always learn something new at a sprint like this, which is one of the main reasons I try to participate whenever I can. By the end of the day, we had merged 17 commits/pull requests and closed 8 tickets.
Appreciation for Support During the Sprint
At around 16:45, we met again in the huddle to review the day. I’d like to take this opportunity to thank our employer, undkonsorten – Die TYPO3 Agentur, whose management always supports us in participating in events like this during working hours. Thank you for that!
Join Us for Future Best Practices Code Sprints
Finally, I encourage others to join these code sprints. They’re not always just about programming – there are plenty of tasks where you can contribute. In fact, it is often a great advantage to have people in the sprint who don't have a lot of experience or knowledge. It helps to see, for example, whether the documentation is sufficient and everything is explained clearly. So, don’t hesitate — join us!
If you’re interested, you can find everything you need to prepare for a remote sprint here: Regular remote day
And don’t forget — the next Best Practices Team remote code sprint is on Monday, 7 April 2025. Find all the details in the #best-practices-team Slack channel. Hope to see you there.