News for hackers. Stuff that matters.

formerjpl

Re:Startup Ideas on Friday November 17, 2017 @12:04PM (#15723752)
> Smart Bathroom

Honestly, if there was a way to attach a gas chromatograph to toilet, i’d totally buy it. It’d be nice to be warned of high mercury or lead intake. Also, if there was a way to assess the state of your gut (micro-biome, digestion issues) in real time it would be a big win. So much of my life is dictated by diet (migraines, physical performance, mood), that having additional data points to correlate with, and potentially find causations, could potentially increase my quality of life.

I'm really not understanding how someone could manipulate index futures (or options on futures, which, in the US, are subject to stock-type settlement). The "Final Settlement" on an index future is determined by the settled value of the underlying index. Any discrepency between the index future and the underlying index near expiration would result in an easy arbitrage opportunity.

Are you implying that, close to expiration, a large player would move the index, in order to move their option position in the money? In the case of ES, that would imply buying an impossibly large of amount of SP500 assets---which they would have to liquidate at some point after the ES settlement or liquidation...

Also not understanding your point on pin risk, pinning is the result of maintaining a delta neutral hedge, which is a well known strategy...

I used to work at JPL (and coincidentally was given an opportunity to work on Voyager to update some ground software, but ultimately I passed on it since I was way over committed at the time.)

JPL has a formal database that maintains all its requirements documentation. Though, it isn't very user friendly; and you generally have to know what you are looking for.

When I was there, most of the knowledge transfer happened by talking to the older folks around. As a result, I ended up developing close work relationships with people who had been there for 20-40+ years. The historical context they provided on current and past designs was incredibly useful, and not something you would find in a requirements document.

Software was a different matter. Until recently, when the internal GitHub was introduced, finding and digging through code was not as straightforward. Each team/section maintained their own repos. And there was very little consistency, some used subversion, others cvs, accurev, etc, so it made it difficult to find and read code for projects outside your purview. Naturally, this led to software fiefdoms. In contrast, I work at google now, which is the polar opposite: I can effectively read through the entirety of google3 and send a CL/patch to just about anyone.