15 of 16 people found the following review helpful
I would avoid as there are better books out there!,
Amazon Verified Purchase(What is this?)
This review is from: Objects First with Java: A Practical Introduction Using BlueJ (Paperback)
I am a university graduate, graduating in computer science with a 2.1 with honours.
Our course relied heavily on programming and Java was the language of choice.
Objects First with BlueJ was an essential read and the use of the BlueJ IDE was expected from all students.
Now after graduating I have read additional books on Java as to me some concepts remained unclear and so I wished to brush up on them.
Only after reading 'Head First Java' did I realise how poorly written 'Objects First' (using BlueJ) actually is. I found the book to be a very dry read and easy to forget in comparision to the layout and structure of that in the Heads First range.
Programming should be fun (if it is not then it may not be for you). It was through using Head First Java that I was able to understand complex concepts of programming while not getting bored of page after page of text.
I wll say however I found the BlueJ IDE a good learning tool to understand class relations and how objects act within a program.
If you are new to programming I would give you this advice (which I wish someone would have told me before I started my course).
Make sure you have a good understanding on the foundations of programming before attempting more complex areas. What I mean by this is truly understand objects and classes and how objects initiante an instance of a class and how those objects can be used with other objects of different classes to carry our tasks. It is through having a good understanding of the concepts of programming (in how OO works) that you can build greater knowledge on programming and it also makes the use of concepts like RMI and I/O using Sockets far easier to understand.
My second tip is to make sure you PROGRAM! It is all well and good to read but it is equally (if not more) important to write code and see how the code works. It is through experiencing problems that I would say I learnt the most.
My third and final tip is to make sure you test yourself. I know university is demanding in terms of multiple modules being taught at the same time but it is through time managment and using your free time wisely that will help you in the later stages of your course. During summer you have lots of free time so use that time in writting a program (maybe a veteneriam program or somthing similar) to gain knowledge in GUI's, Collections, Inheritance etc.
If I was you and being asked to buy this Objects First book I would also fork out and buy Heads First Java also. I used the BlueJ IDE with the Heads First book and found that the IDE gave a good visual on the inner workings of my code where as the Head First book gave a better understanding on the concepts of programming.
Hope this review was of some help and best of luck in your learning.
BTW: my next port of call would be to learn design patterns after grasping the ideas of Java. I have finished my Java book and am now looking into design patterns which give great ideas in how to write your code correctly and efficiently. The book I am reading describes the non-use of design patterns similar to reinventing the wheel. Programmers out there have already spent time in working out complex design issues and it is through these design patterns that you can learn how to overcome issues with your code (for example programs evolve in time).
Sort: Oldest first | Newest first
Showing 1-2 of 2 posts in this discussion
Initial post: 28 May 2012 18:31:25 BDT
I still think the book is great. I used it to teach a pre-university course on Java. The students loved it and progressed very well. It is not all "dry" to read. It is extremely practical. "objects first" it is indeed, unlike so many other "beginner" Java books. I can't comment on post-graduate level, but the book is a superb start to Java and I have not seen anything nearly as good!
Posted on 15 Sep 2012 19:50:48 BDT
Last edited by the author on 15 Sep 2012 19:51:37 BDT
D. Murphy says:
YOu have made some good comments but I would caveat what you say as follows:
1). The dryness or otherwise of a book is essentially a personal decision. I like the book and don't find it too dry. each to their own eh?
2). re the head first books - like the dummies books, I find them irritating to read. Again, personal preferences.
I would say my tastes in technical books are pretty close to the polar oposite to yours. It doesn't make you wrong or me wrong, just different.
the key point about the book is how accurate it is and how much it can help.
Good luck with your career, I have been in the IT business for 30+ years and it is equally fascinating and infuriating :)
‹ Previous 1 Next ›