My First Day on the Frontline — Report From a Best Practice Remote Code Sprint
With the new year just around the corner, I attended a Remote Code Sprint of the Best Practices Team for the very first time ever.
And I survived!
Getting Started: First Hello
The start of the remote code sprint is well organized and nicely structured — the day begins with everyone introducing themselves, and I immediately felt included. It’s also totally manageable for anyone who’s a bit shy, because there’s a facilitator guiding everyone through the agenda.
And there’s always room for questions!
It also wasn’t a problem at all that I’m still quite inexperienced with TYPO3. I was assigned a ticket right away and paired with an old hand who walked me through the project setup after the meeting.
So within just 20 minutes of the Remote Code Sprint, I had already learned new things about DDEV and Composer — and so it went the whole day.
Result of My Day (It Worked — Yay!)
By the end of the day, I had actually managed to solve a ticket — a small but very satisfying first success!
For anyone who wants to code in a friendly yet truly educational team environment — I can absolutely recommend it! And I believe this will have a positive impact on my job too.
Save the Date: On-Location Sprint 2026
If you’ve read this far (and I hope a few of you have!), here’s a final bit of news:
Coming up soon, there will be an on-location sprint in Bonn, Germany, 26–28 March 2026 (Thursday through Saturday).
Start planning if you’d like to attend. Travel and accommodation costs can usually be reimbursed from the Best Practices Team's budget, so participation is affordable.
See You Next Time!
The next Remote Code Sprint for the Best Practices Team will take place every first Monday of the month. Next dates — 2 March 2026 and 6 April 2026, starting as always at 11:00 CET.
Have a successful day, and see you there!
