Oh yeah, there are pitfalls for sure.
It's a delicate balance and reading your comment, I tend to agree I focused on the pros and less about the cons and risks.
I think there are two main routed for code to leak, one way is the case of stealing code. While there are some ways to handle that, non is 100% covered and so, we focus on recruiting to mitigate that.
The other way which in my mind, is the way more common situation, is mistakes. People play with some code on their personal code, post something as a public gist etc.
We mitigate that with with education and a tool that was built in house to monitor and alert on all public activities, for the security team, it's usually easy to review the alerts to understand if there is a data leakage going on:
https://github.com/AvnerCohen/github-public-monitor
Would love to know, if anyone knows the insides, if this is something to be reported, I just feel bad for the people backing this and are unaware of the project status.
Would love to hear other people's opinion and approachs to solving Multi-Tenant Application Configuration, solution that provides good solution to non-dev updates, cross environment replication and auditability.
Crazy. Just crazy.
Regardless if you are a fan or not, an all time top 5 player. Will always be remembered for the Kobe spirit - relentless to win and extreme hard working ethics.
R.I.P
Personally, when I was a manager and going over CV's, I liked it when a person would add a title in the form of "Looking for xyz".
Where the statement is not generic and is actually aiming at what you want to do. If there is more than one such thing you'd be happy to be hired for, put aside these statements and just updated the CV before sending it based on the specific job offer.