My Adieu to LabVIEW : Your Comments

[FraggerFox]

@tbob:

I agree, that's why I am going through C# now 🙂

I came to know by googling that on doing C#, you are almost done with VB and Java......don't know to what extent is that true.

@jeff: why would you say that?

Message Edited by Fragger Fox on 01-20-2010 09:52 AM

[JÞB]

Frankly, it was mostly toungue-in-cheek.  However, my career path started as an electronics technician (25yrs ago OUCH!) the experience gathered from this path impacted my thought proceses in such a degree that when I was first exposed to the concept of data-flow It just gelled instantly.  I would postulate that, a good alectrinics technician almost HAS to think the same way data flow works.

While I've learned an incredible amount about programming (not all by a fair margin) I still find my thought process adapts better to LabVIEW than text-based languages.  I write a fair amount of code but, the code I write is secondary to the test systems I design.  LabVIEW is just too valuable to my job function to really opt out of maintaining and improving my LabVIEW skills and leveraging my reuse library.  

[Ben]

---

Jeff Bohrer wrote:

... my career path started as an electronics technician (25yrs ago OUCH!) the experience gathered from this path impacted my thought proceses in such a degree that when I was first exposed to the concept of data-flow It just gelled instantly.  I would postulate that, a good alectrinics technician almost HAS to think the same way data flow works.

...

---

Ditto that!

Ben

(Ex-Scope jockey)

[Nishant]

Hello All,

I have come back to this forum after a year and a half and i know many of the guys, especially Ben, who has always helped me in resolving my issues related to LabVIEW.

In all this time, i was not in touch of LabVIEW at all, but i am thinking to restart it again as i have thoroughly enjoyed working in LabVIEW with the supports of veteran here. So, i would ask the guy to not to leave the field of LabVIEW.

does anybody have job for me in LabVIEW?  

Regards,

Nishant

[PaulG.]

---

Ben wrote:

---

Jeff Bohrer wrote:

... my career path started as an electronics technician (25yrs ago OUCH!) the experience gathered from this path impacted my thought proceses in such a degree that when I was first exposed to the concept of data-flow It just gelled instantly.  I would postulate that, a good alectrinics technician almost HAS to think the same way data flow works.

...

---

Ditto that!

Ben

(Ex-Scope jockey)

---

Me, three! To me LV writes and reads a lot like a schematic. .

[AnalogKid2DigitalMan]

---

PaulG. wrote:

---

Ben wrote:

---

Jeff Bohrer wrote:

... my career path started as an electronics technician (25yrs ago OUCH!) the experience gathered from this path impacted my thought proceses in such a degree that when I was first exposed to the concept of data-flow It just gelled instantly.  I would postulate that, a good alectrinics technician almost HAS to think the same way data flow works.

...

---

Ditto that!

Ben

(Ex-Scope jockey)

---

Me, three! To me LV writes and reads a lot like a schematic. .

---

Me, four- What Paul said...

-AK2DM

[garya505]

---

AnalogKid2DigitalMan wrote:

---

PaulG. wrote:

---

Ben wrote:

---

Jeff Bohrer wrote:

... my career path started as an electronics technician (25yrs ago OUCH!) the experience gathered from this path impacted my thought proceses in such a degree that when I was first exposed to the concept of data-flow It just gelled instantly.  I would postulate that, a good alectrinics technician almost HAS to think the same way data flow works.

...

---

Ditto that!

Ben

(Ex-Scope jockey)

---

Me, three! To me LV writes and reads a lot like a schematic. .

---

Me, four- What Paul said...

-AK2DM

---

I also started as an Electronics Tech, went to C, then C++, then device drivers and APIs, now learning LabVIEW.

[AnalogKid2DigitalMan]

---

garya505 wrote:

---

AnalogKid2DigitalMan wrote:

---

PaulG. wrote:

---

Ben wrote:

---

Jeff Bohrer wrote:

... my career path started as an electronics technician (25yrs ago OUCH!) the experience gathered from this path impacted my thought proceses in such a degree that when I was first exposed to the concept of data-flow It just gelled instantly.  I would postulate that, a good alectrinics technician almost HAS to think the same way data flow works.

...

---

Ditto that!

Ben

(Ex-Scope jockey)

---

Me, three! To me LV writes and reads a lot like a schematic. .

---

Me, four- What Paul said...

-AK2DM

---

I also started as an Electronics Tech, went to C, then C++, then device drivers and APIs, now learning LabVIEW.

---

Ironically, this thread is look less like LabVIEW and more like a text based language. (Referring to the nested replies that have been quoted in successive posts) 🙂

-AK2DM

[JÞB]

Wow- LabVIEW Forum Recusion strikes again as seen here

Well- I USED to think that I was somewhat of an odd-ball moving to programming from a US Navy ET background.  Thanks for the corrections-

[DianeS]

You're not as much of an oddball as you think, Jeff.

(Or maybe you are?)

I started out as an engineer -- degree in EE -- designing and building lasers.  Lasers are sort of awesome and photons rock.  For me, LabVIEW started out as a toy...then became a tool...then became a joy...then became my career.  I left my laser engineering job (I spent 13+ years in that field) to write LabVIEW code for a living.

Right from the get-go, LabVIEW was far more intuitive to me than text-based programming.  Engineers are trained to think in flowcharts.  Dataflow is a natural for us, and I think that was part of the whole point of LabVIEW.

That being said, one must still understand good programming techniques and style in order to write good code in LabVIEW...just like any other language.  I think a lot of users don't really understand that you still have to use good practices with LabVIEW in order to end up with good code.