Talk:Getting Started

Organization

I put this list in the order I think would be best for a new LabVIEW programmer. My goal would be to be able to point someone new to this list and have then go though it during onboarding. Add to this discussion if you think I left something out or if you think the order should be different. Let's come up with the best list we can for both those entirely new to programming and the accomplished programmer just new to LabVIEW. --Q (talk) 19:24, 19 May 2020 (UTC)

My goal would be to be able to point someone new to this list and have then go though it during onboarding. - This is one of the reasons I'm contributing to the wiki :)

In my experience, transitioning programmers want to know the difference between what they are used to and how LabVIEW compares to that. Unfortunately this can mean different things to different people. In general, however, they want comparison charts, reference lists, and tips and tricks. Novice programmers on the other hand want to understand the basics and see quick results (otherwise they get demotivated quickly). This is very hard to balance. I suggest to have multiple sections on this portal, perhaps based on the Core 1-3 training levels? So one section would provide links to pages that aid in the training exercises or extend on the knowledge provided in those lessons. --Logmanoriginal (talk) 20:15, 19 May 2020 (UTC)

• So, should the flow of topics on this page should be the order we think a new programmer should take, then also have links to things a transitioning programmer would need as well? I did create this page to start a comparison for text-based programmers, Text-Based terminology. I also started the Skill Level category with Beginner, Intermediate, and Advanced subcategories to help with grouping topics. However, some pages have beginner information and tips and tricks that would be intermediate or advanced on the same page. --Q (talk) 20:46, 19 May 2020 (UTC)

Yes that is right. The categories are fine in my opinion and it shouldn't be a problem if pages cover both basic and advanced skill levels, so long as the learning curve is not too steep. It is probably safe to assume that transitioning programmers can assess on their own if a particular topic or section is of interest to them. The focus should be on new users with no prior knowledge. Topics like Text-Based terminology should probably be listed under advanced topics at the end of the page or in a separate section altogether. Here is a rough sketch of what I mean (there are probably better names for the sections).

Fundamentals This section covers topics and supplemental information for the LabVIEW Core 1 training course. These topics are aimed at new users. Environment LabVIEW Virtual Instrument Front Panel Block Diagram Icon Editor Connector pane Data types Boolean data type Integer data type String data type Structures While Loop For Loop Case Structure Tools Debugging Design patterns State Machine Intermediate This section covers topics and supplemental information for the LabVIEW Core 2+3 trainig course. These topics are aimed at users who are familiar with LabVIEW fundamentals. Environment LabVIEW Project Project Library Application Builder Run-Time Engine Data types Array data type Cluster data type Structures Event Structure Design patterns Event Handler Producer/Consumer Queued Message Handler Functional global variable Advanced This section covers information for advanced LabVIEW topics. These topics are aimed at experienced users who are familiar with the core concepts of LabVIEW. Object-oriented programming VI Server Experts This section covers topics for expert LabVIEW users with experience in programming medium to large-scale applications in LabVIEW. VI Scripting Actor Framework XControl

--Logmanoriginal (talk) 07:12, 20 May 2020 (UTC)