Yep. And that was on top of the fact that they didn't give him a proper specification for the system he built, telling him only generic things (because they didn't want to say, "hey, can you build us software for controlling a dinosaur park?"), and then once the system was running, it didn't work properly, which Hammond et al. blamed on him. The same pattern continues with Hammond ignoring his chief scientist (Wu), his ranger (Muldoon), and his systems engineer (Arnold). Whenever there's a technical problem, it is always reflected on that this is something that was anticipated during earlier construction, but budget or PR required such-and-so, so it wasn't addressed. Profit over good design and engineering, from start to finish.Guardsman Bass wrote:Nedry's betrayal was more understandable in the book, too. The film mentions that he has financial issues and that Hammond "got cheap on him", but the novel outright says that InGen demanded a ton of last-minute revisions that required a lot more work by his team, but refused to pay extra for them (forcing Nedry to eat the costs). To make matters worse, they combined that demand with hinted blackmail by threatening his reputation back at the university he was based from IIRC.
I'm ~70% through the novel now. Malcolm is on morphine and dying, and there's an ongoing meta-debate between him and Arnold, the systems engineer, about stability/instability in mechanical and living systems. Arnold holds that the instability which Malcolm predicted is inherent to living systems, and can be taken into account when performing proper design, while Malcolm holds that the underlying instability will inevitably result in an accelerating out-of-control scenario, regardless of the safety margins and engineering work.
Still nothing about "irreducible complexity of the eye." Malcolm does rant a bit about "science can tell us how to build a nuclear reactor, but it can't tell us not to build one. It can tell us how to make pesticide, but cannot tell us not use it."