07-18-2025 01:40 AM
I have been using LabVIEW on and off for the past 2.5 years. The 1st year was MSc related and the latter is work related. (Im based in the UK)
My only language is not LabVIEW at the work place, so its mostly general / easily doable code for someone who knows their way around a LabVIEW environment and a language like C.
Yesterday my company decided to take me to GDevCon in Sept and I saw that certification is possible there. I was previously not too keen on this but I am thinking why not. I also see a lot of people asking to take CLD directly instead of CLAD.
Now my question is with 2 months of preparation, do you think I can crack CLD or should I try to crack CLAD? Or third option is to give more time to myself rather than pushing to the impossible.
Do ask me if you need any more info. Any guidance is appreciated. Cheers!
07-18-2025 01:52 AM
If your company would pay CLD, try. If not, ask yourself if you really need certification after all.
07-18-2025 03:18 AM
When I did them (almost 20 years ago) the CLAD was a 40 question multiple-guess quiz that really tested your knowledge of a lot of aspects of LabVIEW, and the CLD was a four-hour practical exercise where you built a working application. I think that's still the case, although you don't need the CLAD to take the CLD anymore, right? Anyway, take a look at the practice exams for each and see if you can pass them. On-and-off LabVIEW might not have given you enough insight to pass the CLAD today and, if you haven't written complete applications, CLD might be hard. I think either is attainable in two months for a motivated person that's already comfortable with the language, though.
07-18-2025 06:44 AM
The best way to find out is to look into the CLD prep examples that are out there.Try to build the code to meet the requirements. Once done look at how much time it took you to do the code. Once you feel you have some worth looking at come back and put your code here for others to give feedback. The people on here will help you with the important stuff that NI looks for in the exams. Documentation is as important as the code. In four hours you will probably not get the code complete. It is more about how you design your code. The flow of your code. Good programming practices and documentation to explain what you are doing and why.