Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 05/31/2017 in all areas

  1. Yeah, No. I've never seen a patronising waveform before . That's not happening this time and probably hasn't happened for many years. We've seen LabVIEW stagnate with placebo releases and there are so many maker boards for less than $100, hell, less than $10, it's no longer funny (and you don't need $4000 worth of software to program them). I while ago I put a couple of Real-time Raspberry PIs in system instead of NI products. You love Arduino, right? There is a shift change in the availability of devices and the tools to program them and it has been hard to justify LabVIEW for a while now except if a company was already heavily locked in. If it's not working on Linux then that's a serious hobbling of the software since I, like many others, am now looking to expunge Windows due to privacy concerns for myself and my clients.
    2 points
  2. They're at NI marketing. I don't think anyone can make very well informed decision because so much of the platform is "Next version will have this feature, and fix this issue" and we can't really assess it until we have enough features to actually deploy a full real system, and find the things we like and dislike. I also have concerns about much of what you mentioned. I'll be presenting on NXG and 2017 in our next user group so I thought this might be a good time to illustrate what I call the NXG Cycle. The thing to keep in mind here is some at NI, and some LabVIEW insiders have been seeing NXG since 2013 or earlier. I've known about it but not for that long. 4 years or more of this cycle, all the while questioning all the current work you are doing and its relevance, can make for some very jaded feelings. You tend to stop having high highs, and low lows, and instead are just ready for it to be finished so you can deal with the change.
    1 point
  3. It really depends on your current situation and your future aspirations with LabVIEW in my opinion. In my case, I let my CLD certification expire a couple of years ago. I've been working for the same company for 13 years and having the certification didn't benefit me in any way aside from being able to prove a level of LabVIEW programming competency and provide a sense of achievement for myself. To date, my reputation as the "resident LabVIEW guru" has been more beneficial to me in my job than having my CLD was. Since my company is always 2-3 LabVIEW versions behind the latest releases, I was struggling during re-certification since the exams weigh heavily on having the knowledge of the latest features and functions. It ended up being more of a pain to me than it was worth, so I just let it expire.
    1 point
  4. My answer is, "it depends". I work primarily with production in the automotive industry; with my customers a CLD has no meaning when we try and get new work so there is little to no value there. If I was looking for a new job then a CLD would be something significant particularly if I can attach a significant number of years to it. If I worked for a company that primarily sold software, then (at minimum) a CLD would be critical.
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.