Skip to main content

Finally decided

I have been having these various itch since quite some time. Both about what i am doing here (where i work) and what am i meant to do.
Finally, i have decided "I need a job change". I guess IT services industry was never meant to be the right industry for me. Don't get me wrong there, it's not that i wanna quit because i am not getting any interesting work, it's just that I have ideas about life which does not match with what my company is doing. (As amatter of fact, they have some really beautiful concepts which are great to work on). But i have believed web to be the future and now i have started realising that personal dreams do become quite a pain in the neck, when they are ignoired.

Huh.... now that i put it on a log, i feel much better. Back to work...



Comments

Anonymous said…
“A wise man makes his own decisions; an ignorant man follows public opinion” Chinese Proverb
Sachin Nayak said…
Yes, i am quitting. But after a delay considering that my current manager has helped me quite lots and i dont wanna leave him stranded
Anonymous said…
Hey,

If you're still looking out for a job, maybe we could use your help? Check us out. Email me or drop me a line on my blog, would love to hear what you're interested in.
Anonymous said…
Good luck with your venture, Sachin, but we'd have loved to have more guys around here that love Javascript. If you know anyone that might be interested, feel free to have them look us up.

cheers,
Hrush

Popular posts from this blog

So you have your website deployed in PROD ... now what ??

Posting on behalf of Usr.Web.Speed - My previous job had been to architect and develop websites for various customers. During that time my team and I have architected and developed various web applications mainly for enterprises. (But below info is not restricted to enterprises) Other than the usual development and testing tasks involved, our focus area was to abide by multiple SLAs. One of the primary SLAs was to provide the users of our websites a very low (usually subsecond) response time (or page load time). To adhere to this SLA, we did multiple activities, in code, process as well as infrastructure. These include (but not limit to) - Using best practices including (http://developer.yahoo.com/performance/rules.html) Determining the optimum number of calls to the databases, open connections, etc. Providing the fastest mechanisms to download associated content (such as stylesheets, JS files, etc. over CDN) And debugging the reason for the slowness of the websites, when ...