Title: The road to ruin is paved with 21 days of technical jargon..
Product review: The author(s) start off simply enough. The first 14 days are pretty much the standard fare of all the other Java books I've tried. "Here's an applet, here's an application, here's the difference, arrays, variables, pointers, etc.". But once you hit day 14, look out. The easygoing methodology is gone and you get a freight train of programming jargon right in the face. By day 18, I was digging around for a C++ dictionary to see if maybe that would help. Day 19...I just stopped trying.Frequent errors exist in the coding syntax of thesamples, leading beginners down a road of complete frustration.If you're looking for something more useful, go online and find the "Brewing Java" homepage. Or, pick up "Teach Yourself Java in 24 hours".By the way, there's no way you'll complete some sections of "...Java in 21 days" in a day. Some sections take 3-4 days to swim through the muck of programming jargon.
Would you say this review depicts the product in a flattering or unflattering light?
