Hacker News new | past | comments | ask | show | jobs | submit login

Let's not forget about what happens when a company which had been open internally starts locking things down. Suddenly, you can't get access to certain parts of the code depot, the people working on that project clam up, they stop being verbose in their code reviews lest it leak information, and they stop writing snippets about what they've done in the past week. They ask other teams for resources, but won't say why. You thought you had made it past the final wall of secrecy by being hired, but then they went and started putting up walls inside after years of having things be open. Pretty soon, instead of just one "us", there is now "us" and "the special ones who get to know".

Then they call you to the big auditorium one day for a big reveal, and you find out it's called Wave. We all know how that turned out.




Or, conversely:

Then they call you to the big auditorium one day for a big reveal, and you find out it's called iOS. We all know how that turned out.

You can't pick on secrecy just because a company made a bad product under it, just like you can't laud it just because a company made a good product under it. You have to accept it as a tool of the trade, and hope the people in charge know what they are doing.




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

Search: