Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You're talking about credentials. Secrets are often credentials, but more generally refer to anything confidential.


Code doesn’t necessarily have to be confidential. “Secret recipe” algorithms, maybe.

It’s about trade-offs. If you must have “trade secrets” amongst your code, perhaps you can keep that code available only to whom you trust will follow your wishes with it, and have separate repos to share wherein you do not care as much about collaborators “stealing” the code.

As soon as you let someone into your codebase, almost anything can happen, right?

There are cases where it would make sense to sacrifice risks related to code-copying in order to have faster/better development.

Also, what’s stopping anyone working at ANY company from taking the company code and doing whatever they want?

Code is seldom everything.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: