I think the questionable but was referring to the fact Chinese users doubled this month which seems unlikely as they went from about a quarter of all steam users to about a half.
That would be a lot of new people if at all accurate.
I think you want at least two to cover people missing obvious solutions as well as provide a second pair of eyes when finding issues.
And because two means if there is a reason one person isn't around loses the benefits two people gives you then I'd argue three is the minimum size you should aim for.
If started last year counts as new then I am using it for work aiming at low latency processing of data so seems a good fit, but to be honest it's my default language choice as well. The tech stack also has a number of typescript services and python for tooling, there is a service in golang too but it's a minor part.
This is what I tend to do, along with a script that runs all the required install (rpm/apt generally) and stow commands for everything I use.
It does mean I have to update it whenever I add a new application to my default setup, or an application/tool has a new configuration layout. But those are pretty rare.
Assuming there is some form of bug list associated with it that is often my preferred way to learn a new code base.
Try to fix a bug and you'll soon find yourself having to learn how the code involved works, and with a goal your focus will be better than just reading through the code flow.