10-31-2018 09:23 AM
@Hooovahh wrote:
"... artificially removing tools normally available adds unnecessary difficulty. Not allowing a developer to use something they are expected to have available during their work, would make the test not representative of the job difficulty. However being familiar with the tools and knowing where to find solutions is a valuable skill."
@Hoovah, thanks for supporting my perspective that the CLAD should not be a "paper exam". Administering the test in this way seems to put more emphasis on memorizing icons rather than the ability to use LabVIEW.
Thanks for all the feedback. I compromised: I administered a written exam first, without the use of a the LabVIEW environment, just as in the CLAD. A second part consisted of writing some VIs to solve a various problems using the LabVIEW environment, and in consideration of your input, I disabled the example finder and left the Help.
10-31-2018 02:37 PM
Just to throw a monkey wrench/spanner into the works, I know of several accomplished LabVIEW programmers that use the examples as a starting point for their design patterns.
You can never satisfy everyone, y'know? 😉
10-31-2018 02:39 PM
Probably a slightly less accurate way of measuring LabVIEW prowess is to ask them to write it out for you. If they can get all the CAPs in the right places, there's a decent chance they know how to actually program correctly. 😉
10-31-2018 02:48 PM
@billko wrote:
If they can get all the CAPs in the right places, there's a decent chance they know how to actually program correctly. 😉
I knew someone that would throw resumes in the trash immediately if it wasn't capitalized properly. This wasn't for entry level LabVIEW people obviously.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord