Every Friday at 3:30pm, we stop client work.
The whole team jumps on a call.
And for 90 minutes, we learn from each other.
Here's how it works:
Each developer presents something they learned that week.
→ A new technique they discovered → A tricky bug they solved → A tool they tried → A pattern they implemented
No slides required. Just screen sharing and discussion.
Last Friday's session:
Sarah showed us a debugging technique using Laravel Telescope that saved her 3 hours.
Marcus explained how he optimized a database query from 8 seconds to 200ms.
And I shared a new approach to API versioning I found in a blog post.
Three developers, three takeaways.
Next week, someone else will use Sarah's debugging trick.
Marcus's optimization approach will show up in another project.
And the API pattern will become part of how we do things.
Knowledge spreads horizontally.
Without this ritual, each developer would stay in their project silo.
Great solutions would be locked in one person's head.
Now they're team knowledge.
It creates a culture where curiosity is rewarded.
Developers experiment more because they know they'll have a platform to share what they find.
They dig deeper into problems because explaining it to the team forces clarity.
The rule: no judgment, only questions.
Someone shares something basic? Great, someone else learned.
Someone shares something complex? Even better, we all grow.
This single 90-minute ritual does more for our team's growth than any training budget.
Because it's consistent, practical, and peer-driven.
And it costs us nothing but time.
How does your team share knowledge?
#SoftwareDevelopment #TeamLearning #DeveloperCulture #ContinuousImprovement #KnowledgeSharing
→ scopeforged.com
Philip Rehberger Founder, ScopeForged scopeforged.com
