The point about code reviews teaching the why, not just the what, is the part that stuck with me. It is easy to copy a working solution; it is much harder to learn why one approach was chosen over another, and that reasoning is exactly what a good review passes on.
I also liked the distinction between communities built around chatting and communities built around shipping together. The Roburna Builders model you describe — project discovery, teams, and demo days — gives people a reason to keep showing up beyond the conversation itself, and that is where the learning actually happens.
The line that you do not need to be an expert or have a finished project to join lowers the barrier in the right place. A community becomes valuable through participation, not before it, and the visibility you mention comes from sharing work in progress rather than waiting for a finished launch. A good reminder to build connections alongside skills.