Skip to main content

1Q84 - The Complete Trilogy - Haruki Murakami - my thoughts

  • This is my first Murakami book. 
  • The story revolves around two characters Aomame and Tengo Kwana
  • Aomame is a  Instructor at a sports club and has a dark side to her life
  • Tengo Kwana works as a maths teacher at a Cram School and aspires to be a writer
  • The story slowly gains pace and i found the narration to be quite gripping
  • I wondered at times what made Murakami think of a story like this
  • As the story progresses, the reader realizes that the lives of the two characters are closely interwined and what the two set out to do are in its own way quite dangerous
  • I found the pace to be slacking a bit towards the end, when the reader can anticipate the end
  • I also felt that some of the narration was a bit redundant, as when it comes to describing the character 'Ushikawa'
  • The story could also have been better edited for the above mentioned reason
  • But i believe the above should not stop anyone from reading the book
  • it is brilliant and i haven't read anything like this before
  • Highly recommended
  • A suggestion: If you can read it in e-book format, it is better because at 1200 plus pages, it is not just a literal heavy weight
  • Read May/June 2013 


  1. Well I sincerely enjoyed studying it. This subject offered by you is very effective for good planning,hard work and a great team always make a spotless work..i read your article and find that you make nice point on the service..thanks Regards:- software engineering programs

  2. Wonderful post however I was wondering if you could write
    a litte more on this subject? I'd be very thankful if you
    could elaborate a little bit further. Many thanks!

    Feel free to surf to my web blog; Dog Wind Chimes

  3. Ι'm really enjoying the design and layout of your blog.

    It's а νerу еasу on
    the eyes whiсh makes it muh more enjoyable for mеto coime here and visit more οften.
    Did yοu hiire out a developer to create your theme?
    Superb ωork!

    my ωеb-ѕitе :: prolexin deer antler


Post a Comment

Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …