Path to follow

This post, after along time, is long time pending. I have been traveling constantly through a road without any aim. I just traveled the way the road goes. Some times the road diverts leading to a road with shades and comfort. Taking that road may not be upto the liking of your parents, but you still wander through these roads. We divert back to the main path because we are afraid of the consequences / we dont know what waits for us. I would have preferred to have taken this road. Now I understand that the shades are unreliable and dont care for the traveler.

Procedure

The initial weeks @ Yahoo was nice. Lots of things to understand and lots of basic stuff to know. There are many things that happen in an organization like Yahoo. The first thing is that no one explains things to you unless you trouble them. There are manuals and other docs that let you learn.

The levels of filtering that a web page access goes through is extensive. Performance is another thing. Your users would stop using your application if it has not been configured for great performance. Integration with the rest of the applications and single sign on implementation is another highlight. Load balancing and routing of requests has been done wonderfully.

Rest to come after I learn something !

Yahoo !

It was always my ambition to get into a good organization after I complete my education. I was not that great in studying but did pretty good. I was lucky mostly and had great friends who helped a lot. I was thrilled when Jayasu got into Yahoo! during those placement days and had thought of making him refer me at a later stage. Well that paid off ! Jayasu referred me and here I am @ Yahoo! The office is great but whats excellent is the work force. The people here are amongst the best in the industry. The architecture and maintainability of these huge chunks of code is something that I am very interested in knowing and understanding. The interoperability that components of Yahoo has and how they do scalability. How do they block attacks and where do they get great ideas. Tough times lie ahead as to understand them ill need a lot of time, but ill wait and take one day at a time.

Phew - Learning is hard

The last month had a learning curve to it. I had to learn and understand quite a bit of stuff. General http was one. These interview sessions require that you have the basic knowledge of stuff. The web is some thing that I thought I was comfortable with, but the sessions proved me wrong.

Javascript was some thing that I studied. I have used normal Javascript functions but not to the level as Closures. "Everyone uses closures, knowingly and unknowingly" was the statement of a friend of mine. Cross Side Scripting was another thing that I understood.

What are Sessions ? What are Cookies ? What are the different types of Cookies ? What do you do to maintain Sessions if Cookies are not accepted by your browser ? What is the access policy for a Cookie ?

Alternate Ajax techniques was also another topic that I went through. What happens if the Javascript in the browser is deactivated ? What is Accessibility and whats its importance ? What is Reverse Ajax ? Polling and Pushing ? What are iFrames used for and what are its disadvantages ? Whats JSONP ? What are the security issues ?

What are Javascript Events and how do you handle Cross Browser Event Handling problems ? What is Capturing and Bubbling ?

Why are CSS said to be Cascading ? What is the priority set by the CSS selectors ?

How would you improve the performance of a page ? What are Http Caches ? What are the Http Status Codes ? How would I track errors if accessed using Ajax ?

Why do I use Doctypes ? What are Semantic Markups used for ?

What is a Proxy ? What is a Reverse Proxy ?

Theres a vast array of questions but these troubled me a lot lately.