views:

42

answers:

3

might be repetitive question..please answer guys

1.the company that offer me a job only works on vb and ado.net technology I'm new to dotnet. I dont know about it..So tell me about the scope,?Is it good to say yes to my employer?

2.after 2 years of experience in that , will i still can get a good job, ?

3..Most of the companies still using vb and ado.net?

+1  A: 

whether your employer works in one technology or two or twenty two. YOU have to make sure you have knowledge of most if not all .net technologies (if you want to get a good job after 2 yrs). How can you accomplish that is by reading blogs, practicing at home on small projects and reading books to increase your knowledge. Start working on small projects at home (like a phone number address book application, or an application where you keep track of your monthly expenses and your income etc)

HTH

user279521
Good suggestion really. But What will I do after 2 years if the technology which I have as experience is considered as old one?
Senthil
I don't think anyone will consider any technology old after 2 yrs. Take an example of the current .net technology. If you work on vb and ado.net at your employers place, then at home you read on C# and F# (when you get comfortable with C# and F#, you start on Silverlight, then you start on LINQ), you will ALWAYS have companies giving you job offer - I gurantee you.But its not easy to study / read / practice at home.
user279521
Ya..Valuable Suggestions really.Thank you.
Senthil
In summary Senthil, its your responsibility to make sure you have knowledge of current technology, its not your employers job.
user279521
I dont know about vb.net visual basic and ado.dot net .They tested me in C/C++. I got shortlisted. So only asked about the scope here
Senthil
+2  A: 

VB.NET and C#.NET code is very similar in every context except the actual language syntax. In my experience, learning .NET is more about learning the framework itself, so I wouldn't be concerned about working in Visual Basic rather than C# - if you have worked with one, you can pick up the other in a very short time.

Knowing .NET a valuable skill set to have and should be for some time to come. A few years of solid experience using it should certainly lead to greater opportunities in the future.

I can't speak as much for ADO.NET's widespread usage; my company still uses it exclusively. I think it will be awhile before LINQ and other newer technologies muscle it out completely, though.

If it's an interesting place to work, you should't let the exclusive use of VB.NET and ADO.NET hold you back from accepting a job there, IMO.

Darel
thanks for the suggestion. in the last line are you saying that , I should accept this offer?
Senthil
I don't know enough about your situation to say for sure :) But I would say that the fact that they are using VB.NET and ADO.NET would not be enough of a negative in my eyes to be a deal-breaker.
Darel
So you are saying I can accept if I view the VB.NET and ADO.NET are the problems..
Senthil
thanks for the suggestion
Senthil
yes, in my opinion.
Darel
A: 
  1. VB.Net is still used in lots of places I'd imagine so it isn't a bad place. The question is what kind of business does the company operate, how well is it funded and other non-technical questions that would be how I'd decide as some places may use the latest and greatest technology but with poor practices they will burn new hires out quick. This is the hazard to be aware of understanding.

  2. My crystal ball is on the fritz. Do you think anyone can predict what technologies will be popular 2 years from now accurately and would share that freely? Seriously. Will the global economy recover enough that the current malaise will pass? That would be the better question to my mind as there is a good chance that the bad times will stick around for another few years possibly but that is just a guess.

  3. This is likely among those that wouldn't be disclosed. In my job I can run into some VB.Net from time to time as some applications have their source code in this, so I have to understand it, but it isn't alone in what I use.


Soem thoughts about what to watch in a job to determine if it is a good one or not:

  1. Physical environment. Do you like what your work area looks like? Do you enjoy being around your co-workers or do they all seem like passive-aggressive masters out to push your buttons all the time?

  2. Boss. How do you feel about your boss? Is your boss a friend or just someone you tolerate because this person gives you a possible potential paycheck periodically? If your boss says, "Hi, how are you?" does this make you cringe or happy? Does the boss micromanage everything you do or totally let you do whatever you want and only check in once a week or month?

  3. Technical environment. What methodologies are used for development, is it all adhoc cowboy coding or is there something more formal like Waterfall or Agile? Do you know procedures for promoting code between environments? Do you know what source control and bug tracking software is used? What kind of technical specifications does your work machine have, is it high-end, mid-range or low-end compared to most other machines?

  4. The company. Is it a start-up? Is it profitable yet? If it isn't, who is funding the company and how well is this believed to sustain the company for the next few years? How experienced are the executives in the company? What are the company's values? What does the company believe is its mission or purpose of existence?

These are just some basic things that I'd consider and use to determine how good is where I work. If you want a more general heading to ponder, think about expectations, both what you expect from the company and what the company expects from you to help shed some more light on your situation.

JB King
Nice tips.,k..tell me the ways to approach the peoples of organizations to know the informations regarding positions and other technical details
Senthil