Every monday, wednesday and friday, Michael and Cameron get together after work in a pub a couple streets from DFS. Pretending to be a classmate from Michael's highschool, I asked the bartender what they do here all these days. He said they talk about creating their own logistics company, using their experiences at DFS. Afterwards, they play a game of snooker.
So today, I "ran into" them at the pub and invited them to a friendly game of snooker (and lost on purpose). We had a couple drinks.
Michael talked about his Supplies module in the spacestation. The entire thing is automated. Once the space station is complete, his module will take care of the automatic docking of cargo-ships and unload their cargo. Each cargo ship communicates its cargo-list to the space station, where the supplies module compiles that list into a lowlevel firmware batch for the onboard robots. The entire thing is written in perl.
Cameron, who operates both the factory and the export modules of the space station, is apparently a genius.
Since everyone at DFS is aware of that, noone asks questions about what he really does. He told me he plays angry birds all day long and boasts that he can finish programming his module in under 24 hours if needed. With his strong mathematical background, he bases his entire security on SSL certificates. All it does right now, is connect to a local service on port 21122, to log in and invoke a password recovery tool.
Then Michael and Cameron got in an argument about port 2112 and port 21122, which is an item on the agenda of the next team meeting (they can't decide what port the service should be on). Cameron admits that at the moment, his recovery service runs on port 2112 and his cronjob connects to ports 21122, 21123, 21124 and 21125, but said it's no problem since he uses SSL and the cronjob verifies the issued server certificate.