#self refelection

[tumorsandmusic]

Starting over, or am I?

Tomorrow I start my new life.  And I know every change I've been through has started my new life, but this is the start of a very real very new part of my life that until recently I never thought could happen.  And so I've been reflecting.

Every change I've been through I've seen as a chance to start over and erase everything I wanted to forget.  And I was always so happy to let my past slip away to what I thought was oblivion.  But the truth is it would always come back. Just when I thought I could shut the door forever, it would slip back into my life and torture me.  So this time will be different.

This time, I'm not starting over, just moving forward.  I can keep those things with me and let them shape me.  Like they should.  I can't hide from my past or the things I'm scared of anymore.  Just like I've learned to accept my mouth and everything that came with that, my past and the person I was are things that I need to keep with me.  They can be private, I can keep them to myself, but I can't let them go completely.  

So tomorrow I won't be a brand new, shiny Robin. Just the same Robin that has decided to remember the past in a passive but still relevant way.

[impecuniouslife]

Oh, so polite indeed Well I got everything I need. Oh make my days a breeze And take away my self destruction.

Soul to squeeze - Red Hot Chili Peppers

[chandventure]

Observer Pattern

I am now trying to find the route of the Observer pattern. Before sometime I have used this pattern but now I seem to have forgotten it. I even see the flashing autocomplete suggesting me java.util.Observer but without knowing what that is - I am intimidated to use it…

This inspired me to go into details to learn about this design pattern and to figure out the Observer design myself by finding solution for the main architectural problem at hand. 

Why is the Observer pattern used?

When I need to communicate a set of dependencies that a property of an object is changed. Now looking at it in a short sighted way the best approach I saw was to have the Class refere the Dependencies themselves. 

The job get's done by this mechanism. But there are couple of problems that emerges after this design is implemented. First of all the Interface needs to know about the User class. That's perfectly alright since the Interface has to keep track of the User. But User has to know about the interface as well. Now this is not a good design. If there is - let's say 50 interfaces… The User class needs to know about all the interfaces that the  connected. 

After that I understood that Observer pattern has much more detail into it and what I was thinking should be done in a different way. More importantly I read couple of articles and looked at the class diagrams over and over again and I understood it. 

Below is the best link I found to get the idea about the Observer pattern - http://java.dzone.com/articles/design-patterns-uncovered

[eldritch-thoughts]

Some times I wondered if I choose the right path. I wonder: what if? What if I didn't run to my priesthood and embraced my passion for crotchet? Would I be as happy? Would the stars have finally been right? Then I subject myself to the horror of Azathoth eating a baby rhinoceros for being so human.

The Great Cthulhu