First 5 Favourite computer books

These books helps me a lot when i face difficulties in my projects and improves my solving skills as well which i will like to share with anyone.

Book 1 : The algorithm Design Manual by Steven S. Skiena.

Very good book to learn more details to tackle algorithm problems. It is very technical but after re-read many times, i came to understand at least 70% of it’s contents. When i was in computer science major, i suffer a lot to understand most part of the algorithms, which i was wondering why at that time none of my lecturers or tutors ever suggest this book to learm algorithms. What a shame!

Book 2 : Design Pattern, Elements of Reusable Object-Oriented Software by the Famour four gang.

Well, another important and must have for every software engineer.  I once found it difficult to learn, because lack of object-oriented design experienced. Instead, I started reading this book first : Book 3 : Head First : Design Pattern and then come back to previous book. Head First : Design pattern are so easy and fun to read. I understand a lot of design pattern and how to use it in my projects after reading combination of these two books.

Book 4 : Don’t make me think! A common sense approach to Web Usability by Steven Krug.

If you’re web designer, developer or software developer, and you don’t have this book, you should really really get this book immediately.  This book change the way i think when designing the graphical user interface for every projects that i had worked on. When we tend to design any sort of GUI, we tend to perceived and imagined how this or that GUI should work based on our mental model, and forgot who is the real person using the GUI. But, we never though about the user side mental model. This book give me a lot of ideas and hints of do and don’t when comes to usability.

For example, my last project was to design and mobile application for vision-impaired users. I actually had to understand how vision-impaired person use their mobile devices using Text-to speech software such as Nuance Talks. Indeed, it was very hard for me even i am the person and my team who design the software. We actually had to shift our’s mental model to vision-impaired ones’ and of course frequent communication and user acceptance testing help us a lot dealing with those difficulties.

Book 5 : Beautiful Code, Leading programmers explain how their think by Andy Oram (Editor) and Greg Wilson (Editor.

I love to re-factoring my code every times i had finish the main coding. I tend to make it clean, efficient and readable to any users as much as possible.  This book teach and guide us, way to produce good quality and maintainable code. Most of the sections, are very useful except chapter 10, 16, and 23 because these chapters more on low level and very technical stuff such as Linux Kernel and Google Reduce Maps.

For my own opinion, to become a good software developer, not only you need excellent solving skills, communications, written, technicals, and more which i can go long for the whole days;however be able to write something that can let people impress like “Wow”, is quite hard.

There are another 5 more books which i will post on the next post. These book includes (Oreilly Regular Expression, Code Complete, Writing Secure Code 2nd, Oreilly Algorithm in a Nutshell, and Think Recursively).

Book Review (September/2008)

Recently i had finish 2 very interesting books. The book is fictional novel call “Kite Runner” by Khaled Hosseini. Wow!, it was really a good and a sad book to read. The reason why i think it is the best fiction book that i ever read this year because :

1. The contents and the words that the author used, were not very depth and complex. It is easy to understand unlike others’ novel. (Hey, i’m not going to pick every single words that i do not know and refer to dictionary. That’s the point why i read novel to release my stress and frustration).

2. The author kept remind the reader what was happened before, so that the reader can kept track the important point while you reach end of each chapters.

3.Ah!!Like the book mention, irony.

4.Sad content and a bit of romance. Nice!!

The second book will be techinal book which is “The Practice of Programming” by Brian W. Kernigham and Rob Pike. I WISH i had known this book when i started programming in 1st year of my Comp Science. Very interesting and useful for any level of programmers. This book manly focus on c,c++ and Java programming languages. But, the thing is, it is not programming languages that the reader should concerned. You can apply the way their teach in any programming language.

I will totally kept one of my list books around me when i do programming. One of the book that wannabe “Good” programmer should have.

Book review #4

[Follow-up from previous post]

Finished Reading
Book Version : The Painted Veil
Movie Version : The Painted Veil

Author by : W. Somerset Maugham (Wikipedia)

This book was fantastic and sad. I don’t know how to describe it, i am not going to be a spoiler to tell the storyline (This post were will be very short because i really^2 do not wish become a spolier before you read it).

I really recommend this novel for person who are in Romance genres. But i think it is better to read the book first then only watch the movie.

Happy reading. 🙂

Book review #3

[Follow-up from previous post]

Technical Book

JavaScrip Bible

JavaScrip Bible

Javascript Bible Six Edition

Comment : This book is a MUST have for web developers. It made several important improvements over 4 edition. Example provided were very details and specifics. Ajax were covered as well.
The book is very thick like 6-9cm. Very good for beginner and amateur programmers.

Book review #2

[Follow-up from previous post]

Technical Book

Web Services : Author by Gustavo Alonso, Fabio Casati, Harumi Kuno, and Vijay Machiraju.

Comment : This book is really good for people who are new to web services and references as well. It explain the history of System architecture to current web services. Since this book is kind like a bit extreme technical like RFC specification and no practical solution at all. It introduce SOAP, WSDL, UDDI, 1 to N tier architecture, web service compsition, BPEL, WS-Security, WS-transaction, WS-routing, and more ws-*.

The first 1-4 chapters were about the enterprise system era before web services was introduced. You can got a big picture why integration and interoperability was so hard at that era.
Chapter 5-6, slowly walk through the needs of web services and chapter 7-9 were mainly about web service composition and BPEL was introduced.

Although i finish reading this book, i only get half of its content because this book was too technical for beginner. You had to understand each design behind the system before proceed to the next chapters. If you want to learn web services and don’t know where to start, then this book might help you.