I need an advice with my carreer
-
Most people I know who worked for TCS wouldn't call moving-to-TCS-for-a-lower-salary a remotely intelligent move. :~
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. Also visit the Ultimate Toolbox blog (New) -
What's the use of having a company as a Label in your CV, when you will not be able to grow technically in the company. Imagine you joined in TCS and then after a few years you decide to move. Will you be technically a better person after working in TCS or at your company? Will you be able to handle the questions asked in an interview any better? In the end that will matter rather than which company's stamp you have in your CV. Also you will lose money when you join TCS. So it is an extremely dumb move.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
-
What's the use of having a company as a Label in your CV, when you will not be able to grow technically in the company. Imagine you joined in TCS and then after a few years you decide to move. Will you be technically a better person after working in TCS or at your company? Will you be able to handle the questions asked in an interview any better? In the end that will matter rather than which company's stamp you have in your CV. Also you will lose money when you join TCS. So it is an extremely dumb move.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
Well, as I see it (obviously I'm wrong) TCS is a better company just because it is know and not mine. It's the same than working in IBM or the company next door... An other thing is that you see like I will enter really from the bottom, but it's just possible, if I defend myself I could enter as a module leader for example. (Friends of mine have entered like that with my same experience). It's not I'm arguing after making a question, it's just that I'v thinked a lot and now you tell me not to do what I tought it was better, so I just try to understand how you think and where I'm wrong :) Thanks!
-
Well, as I see it (obviously I'm wrong) TCS is a better company just because it is know and not mine. It's the same than working in IBM or the company next door... An other thing is that you see like I will enter really from the bottom, but it's just possible, if I defend myself I could enter as a module leader for example. (Friends of mine have entered like that with my same experience). It's not I'm arguing after making a question, it's just that I'v thinked a lot and now you tell me not to do what I tought it was better, so I just try to understand how you think and where I'm wrong :) Thanks!
My assumption is that you want to leave TCS after sometime, maybe after your CV looks good with TCS on it. If that is not the case, you should select a company where you will have maximum growth technically as well as financially. There is a right time for everything. If TCS will offer more growth than go right ahead otherwise stay where you are and gain some more experience.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
-
My assumption is that you want to leave TCS after sometime, maybe after your CV looks good with TCS on it. If that is not the case, you should select a company where you will have maximum growth technically as well as financially. There is a right time for everything. If TCS will offer more growth than go right ahead otherwise stay where you are and gain some more experience.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
-
Rama Krishna Vavilala wrote:
My assumption is that you want to leave TCS after sometime, maybe after your CV looks good with TCS on it.
This is exactly what I plan :) How did you guessed hehe :~
siskhoalanka wrote:
This is exactly what I plan
If that is the case, then it is a bad idea to join TCS. Stay in your company and grow and then leave.
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -Brian Kernighan
-
Ravi Bhavnani wrote:
If you're not going to grow as a developer in your new position, I think you should stay where you are.
Even if I can continue the path I'm following in a much more known company? I mean, this soft company where I am now don't really gives me something if I try to get out of my country, in the other side I suppose you know TCS, it's a world known company, I mean, from this perspective I think it is a good point. But I wouldn't be asking here if I was sure of what to do, so... I listen to the advices :)
siskhoalanka wrote:
Even if I can continue the path I'm following in a much more known company?
Imho, yes. In 2000, I left a large, successful (at the time :)) worldwide leader in the digital imaging industry after 6 years of working there, because I felt I wasn't growing any more. When I become the defacto MFC "guru" in the department, I knew it was time to move on. So I joined a little known startup and found myself being intellectually challenged almost every day. I was surrounded by several smart engineers and my comfort level quickly dropped (a good sign). It was a great learning experience and I've always tried to seek out an environment where I'm likely to learn from folks much smarter and experienced than myself. TCS is doubtless a well-known company, but would you rather be an engineer from TCS who knows x, y and z at a superficial level (note, I'm not generalizing about TCS or large companies) or someone from a lesser known firm who knows x, y and z as well a, b and c, all in great detail? I know who I'd rather hire. :) /ravi
My new year's resolution: 2048 x 1536 Home | Music | Articles | Freeware | Trips ravib(at)ravib(dot)com
-
Most people I know who worked for TCS wouldn't call moving-to-TCS-for-a-lower-salary a remotely intelligent move. :~
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. Also visit the Ultimate Toolbox blog (New) -
Hi, now it is my time to ask for an advice :rolleyes: I am in this soft company since a year, quite known in my country (I don't want to tell which one so my coworkers don't recognize me). It's my second job, I'm 22 and the first one was in an unknown company but I've been there 3 years, so in total it's 4 demonstrable years of experience. Now I have the opportunity to enter TCS(Tata Consultancy Services), it would be really better for my cv, but there are a few good and bad points: Good: It's good for my cv. Bad: In my actual company, the coders are better than tcs ones, especially in .NET. My actual company pays me more I already know a lot of people and gained a trust level I don't have to do any extra hours since i'm in outsourcing In Tcs I will have to do an avg of 1 extra hour or 2 per day (I know because I have a lot of friends there) I will restart almost from the beginning because I do not have enough experience to pretend to enter as a Project Leader or an Analyst, so I'll probably enter as a Team Member (Maybe Senior Developper if I'm lucky) I know I will leave, but the real thing is: Right now or should I wait more than one year? (Consider that my forst experience is not really considered because I was coding in vb6 only and tcs really don't give a s*** for vb6, so it's not like nothing but it's not like 3 years in .NET) So I'd like to know what you think :) Thanks!
With very few exceptions, the name of the company on your resume does not help you. The biggest exception is if you worked for very large or very small companies for many years and are switching to the opposite extreme (the worry being that the cultures between the two are usually VERY different and many people have a hard time adjusting. I do; I go crazy working for large companies.) When young, go for the company that will give you the broadest experience at their expense, even if your salary is low. The specific computer language isn't nearly as important as learning how to simply program better and how to manage projects from the smallest to largest details. When older, go for the salary with the fewest hours possible. (I also detest all the hand-holding, lets-all-get-along crap that is so common now in companies as a substitute for actual management, but that's another story all together.)
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
Ravi Bhavnani wrote:
Nish, are you back?
Yep. Got back 3 AM last morning and seriously jet-lagged.
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. Also visit the Ultimate Toolbox blog (New)
