Everyone learns on their own island

In a remote team, everyone learns on their own island.

Someone builds something really clever in the afternoon, solves a problem that used to cost days. And then? Mostly it stays right there. On the island.

That isn’t unwillingness. Nobody holds back what they know on purpose. For me, in the evening, it was simply energy. After a good day’s work I never had the strength left to turn it into something visible. By the next morning it was just gone.

For a long time I thought that was a discipline problem. It isn’t. It’s friction.

So I built myself a small Claude skill that goes through my commits across all repos in the evening and tells me: this one would be worth mentioning. No finished text, just the raw topic. I still say yes or no, and the rest lands in a shared channel for the team.

The machine does the legwork of remembering. The decision about what matters stays with a person.

And suddenly the island isn’t an island any more.

How does your remote team share the small stuff that would otherwise vanish in the evening?