Digital Fortress or Digital Disaster?

I just got done with reading 'Digital Fortress' by Dan Brown. Picked it up with huge expectations after reading The Da Vinci Code, only to be extremely disappointed.

The end was the most tortuous, imagine the top guys at the NSA (supposedly the accumulation of the brightest minds on the planet, according to the novel), not knowing their seventh standard chemistry. I'd expect them to figure out the difference between the isotopes of Uranium, an element we hear and read more than we do about others, O2 for example.

If you're reading this book, be ready to be told the "very basic" facts of cryptography, in a way so as to demo the "superlative" cryptography knowledge of the lead characters.

The Da Vinci Code was good. Digital Fortress isn't.

Comments

Ankan said…

The absolute last para is a totally wicked idea. About crypto in the book, yea, it is remarkably short of details...but you don't expect the average reader to get engrosed hearing term like stream and block ciphers and the details of polymorphic code do you? The topic in Da Vinci Code is much more "mythical" and hence has an easier "aura" around itself, making it more perceivable.

2:12 AM

Gmail Chat Disabled

The fact that it happened does not surprise me but that it took so long for our network administrators to figure it out does. And if you are wondering how do you disable Gmail's chat features on your network, you only need locking DNS lookups to chatenabled.mail.google.com , by returning 127.0.0.1 .

Advertising Billboards as Rain Covers

Advertising billboards are put to use as Pakistani refugees, left homeless after the October 8 earthquake, set up their tents in Muzaffarabad, Pakistan. [via SFGate ] Technorati Tags: Pakistan Earthquake

Community effort to create a single persistence model for the Java community

A community effort led by Sun Microsystems is aiming to create a single 'Plain Old Java Object' persistence model to provide a single object/relational mapping facility for Java app developers in J2SE and J2EE. Paul Krill writes In a letter to the “Java Technology Community” on Friday, specification leads on Java Specification Request (JSR) 220, which is the proposal for Enterprise JavaBeans 3.0, and JSR-243, for Java Data Objects, state that the two technologies feature divergent persistence models. “This divergence has caused confusion and debates among Java developers, and is not in the best of interest of the Java community,” said JSR-220 leader Linda DeMichiel who also is a Sun employee, and Craig Russell, a staff engineer at Sun who leads JSR-243. “In response to these requests [for an end to the unwanted divide], Sun Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community,” the letter said.

enginerd

Search This Blog