Labview for software developer as career?

Question

1.00/5 (1 vote)

See more:

Hello,I know this platform is not for question that I asking, but I want you all people advise for this. I am a asp.net developer I am working from last 8 months on .Net after my graduation. But Now in my Company new platform is assign to me which is LabView. I treat that IT industry is a area where I make my career. now I am completely shifted on LabView. because of this now I am thinking about to switch company where I can work on .NET.
I am confused about is there chance to make career in IT industry with LabView, which I can in .Net Sorry for such a question but I only found reliable source to clear my Question.

Posted 25-Feb-16 17:22pm

Kishor-KW

Updated 29-Feb-16 3:28am

v3

Add a Solution

Comments

[no name] 25-Feb-16 23:43pm

This question is related to Career not technical one. So please post this question in Discussion board or Help(Ask question).

dan!sh 26-Feb-16 0:18am

Do not repost the question. Also, try work issues forum. Here. It is better suited for this question.

Sinisa Hajnal 26-Feb-16 6:30am

I'd say that it is completely up to your decision and what do you consider "making a career in IT" - if you think only .NET then you have to change. If you consider that IT is much, much, much (and much) :) broader then just .NET and that you're just starting the career then you could stay and learn.

2 solutions

Solution 2

I tend to disagree what Sergey Alexandrovich Kryukov has mentioned. I am not sure if he is basically making a general assumption based on his experience. Labview is like any other language which has its ups and down. Labview is data driven but it can easily be based on Control and interrupt as National Instrument is expanding and improving its capability.

Me personally moved from VC++, MFC ( 10+ experience ) to Labview ( 5+ going on) and I am not too upset about it.

Your question about career as labview developer and future is partially misguided because tool cannot be the barometer to find success (as SAG mentioned). Other Question you have to look is in what industry and location you are working.
If you have lots of Engineering/Automative and Electronics domain then labiew has good prospect. But if you thinking more like classical IT as such as Banking sector, Retils....web based etc then labview will not help you much.

The basic premise is be strong in your analytical, problem solving skill and toll just supplement those.
If you have any queries regarding Labview, Please let me know

Posted 29-Feb-16 3:28am

super

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2016-02-26T18:34:00

This is a totally off-topic question, but I'll take a chance to tell you my opinion, in hope it could help you. I never knew anything worse than LabView in the related industries. Most of my time I worked in experimental scientific and industrial machinery control and monitoring, and my first international conference presentation was anti-LabView (suggesting my own alternative approach), and I must say: many participants took my opinion with understanding. The idea of "dataflow programming" and especially "graphical programming" was really destructive. To add too numbers they draw two lines to a "plus" node! (Don't tell me about DLL-based extension; I'm talking about main ideas.) And in real life data flows are rare, it's more about events, interrupt and some failures to recover from. LabView authors managed to grab the market and force most hardware manufacturers to adhere to their ridiculous proprietary (worst thing here) standards. I never met a decent specialist in data acquisition, controls (and related fields) who would ever volunteer to work with LabView, but the naive often catch the lure.

But my opinion an a particular tool is not so important for answering your question. Personally for you, there is a bigger problem right now. What would you say if some auto mechanic says "I want to make a career in hex wrench"? :-) But, essentially, you are trying to say the same. A "career" is made not in using of some particular tool. For a career, you have to learn the design and development of technical systems, starting from physics and mathematics behind them and ending with mastering some professional working techniques. And that includes using of any tools which may be useful, and not just existing ones, but also those which are yet to be developed by the moment you could utilize them in your work.

—SA