This very issue (the soon-to-be-reality of computer systems that can and do claim copyright on their output) is why I called on the authors of GPL v3 to include provision for a "Greater GPL". They summarily dismissed the proposal and said such application of copyright is impossible. They were and are quite wrong about that. http://pagesmiths.com/blog/C1602834558/E1763876253/index.html

Whatever Phipps' experience (of which I have no knowledge), he clearly doesn't comprehend Java security. The whole key to safe code in networked environments is the use of security policies. That includes, in addition to "fine grained" access control over OS operations, the ability to restrict access to classes in the classloader mechanism. This is the same stuff that happens whether you're doing applets in a web browser or a servlet in a web application container (including Sun's Glassfish).

Your ideas are being stolen. Not only don't tell anyone what they are, don't even think about them. Hidden in the walls of your dorm are dream snatchers which are recording and patenting every thought you have. Don't think this is a joke or you will regret not taking this extremely important advice.

The original Pragmatic Programmer book is excellent I think.
http://pragprog.com/the-pragmatic-programmer
And since I also think an "agile" approach to managing software development projects is essential for most companies (certainly for any web-oriented development), I'm planning to check out their Practices of an Agile Developer book.
http://www.pragprog.com/titles/pad/practices-of-an-agile-developer
Jim