Yeah, it strikes me as a very... Silicon-Valley-brained view of software development.
For example, I'm sure there's a scary-talented engineer working on fluid simulation algorithms for a major aerospace manufacturer, and they would be fired if their work-product ever left the corporate VPN. Meanwhile, their personal stuff is in a self-hosted solution.
I am of the same idea. Requiring online, public repositories, specifically in GitHub, doesn't cover all developers. It covers many of them nowadays, so there's that.
I guess at some point developers will have to prove they're serious developers by exposing their GitHub profile.
Edit: it's part of your profile already, better vibe code some random ideas to farm some GitHub dev credibility.
I don't think a github profile (or any specific activity therein) should be a prerequisite for being considered a 'serious developer'.
Yeah, it strikes me as a very... Silicon-Valley-brained view of software development.
For example, I'm sure there's a scary-talented engineer working on fluid simulation algorithms for a major aerospace manufacturer, and they would be fired if their work-product ever left the corporate VPN. Meanwhile, their personal stuff is in a self-hosted solution.
I am of the same idea. Requiring online, public repositories, specifically in GitHub, doesn't cover all developers. It covers many of them nowadays, so there's that.
It's built on laravel, email/pass/2fa/forget is all built in. GitHub auth only was a choice.
Because effective anti-spam account measures are not 1-2 prompts away.
What stops someone making GitHub spam accounts?
How about ssh public keys
It uses your GitHub public keys to authenticate so you can post from the CLI.
Maybe spam concerns, but your point remains valid.
And having those passwords leaked is probably only another 1-2 prompts away