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

I've worked on several projects that used "Black Chamber" development.

That is, local LAN only, with no access to the internet, and no internet-capable "personal electronic devices" or cellular phones permitted in the development area.

You had whatever paper documentation you brought yourself, what was in your head, and whatever was in the /documents directory for that project.

It's a different work mindset. I've since moved to a sysadmin position, running a closed network. When programmers decided they couldn't hack being cut off from the net, they'd quit. Dealing with vendors who signed a contract swearing their product didn't need internet access to install or function, when it won't even complete the install without internet access, is more awkward. Particularly when we call the lawyers in. Because that's why we tediously explained the while "no internet" thing in the contract. That they signed. No, not even for just a few minutes. And by the way, can you explain why your installer times out trying to contact servers in three different countries? Our network admin is curious...



I've worked in these environments before (not as a programmer though).

It definitely tests your skill and you can identify who can solve problems on their own. Hopefully you have an additional network that you can do research on.


Dropbox is literally creating a vector for copying your files to the Internet...




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

Search: