I am almost exclusively a Principal author of my work; with dozens of repos, and six figures of LoC (probably seven figures, if we include the code not available in public repos). I think I may have one forked repo; an embedded Web server library that I needed to tweak a bit to make work for my ffmpeg wrapper project.
This is not necessarily a good thing. By authoring my own code, I limit my scope. People who rely heavily on dependencies can have awesome results.
But they need to be very careful about the provenance and quality of these dependencies.
Dependency discovery is an important part of the vetting process. If we have choices, we don’t need to settle for second-best.
Also, I know that, for many folks, learning is a driver for repo discovery.
A lot of forks can indicate an inquisitive and open-minded approach to software development.
I do support it; but it is not how I work.
The projects can have interesting code to read or just show off a cool idea or a different way of implementing something than I'm used to.
Disclaimer: Just a happy sourcegraph user.
[1]: https://code.visualstudio.com/updates/v1_11#_text-search-imp...
But that's just it. It's a bit of limelight. I'm thankful for the interest I've received, but that's all it is, really; it's validation from fellow programmers. It furthers your career in one or two aspects, just like Instagram fuels your self image, or prospects of influencing. But like Instagram, one can chase the limelight their whole life. Ego stroking is addictive. I urge those who come into a bit of limelight to enjoy it, but to stay humble and focus on delivering what you set out to do, not to bask in your temporory moment of glory.