Consider your naming schemes - a cautionary tale
Recently we had a contract for a large company that required the code be put in escrow. This isn't unusual, we're in an industry where if you have fewer than 10,000 employees you're regarded as small and a risky proposition. We have succeeded despite that perception because we're very good at what we do. So an agent for the appointed escrow company comes in to vet the software, check that we can do a full and complete build from the source provided, and then are about to take away the copy to put in safe storage. It'll never be seen again unless we fail to meet our (fairly reasonable) obligations. Then the agent doing the vetting asks for a break. He goes away and makes a phone call. Then another. Then another. Finally he comes back and says that he has a legal responsibility to report us to the authorities. Why? We use a package called "upskirt" - https://github.com/tanoku/upskirt - and
Why it failed
Recently we had a contract for a large company that required the code be put in escrow. This isn't unusual, we're in an industry where if you have fewer than 10,000 employees you're regarded as small and a risky proposition. We have succeeded despite that perception because we're
- Kind
- startup
- Status
- Shut down
- Inventor
- ColinWright
- Ended
- 2011
- Source
- hackernews