Your LabVIEW Code Is a Work of Art... But I Can't Read It
summary
Argues that style and prettiness do not equal readability and proves it by building and annotating several attractive but unreadable VIs then fixing them with concrete changes: name splitters and panes, set readable numeric and string formats, show full paths, change class wire colors and match banner text, avoid passing mother clusters and prefer explicit control references, label nondefault constants, and add a cue like a plus sign on property folders that do extra work. Uses tools like Pain Relief and Quick Format, cites 75% English installs, and demos these techniques across 76 slides.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:01Why this talk exists
- 12:49Always be reading
- 13:10Naming objects
- 17:30Splitters and UI pain points
- 20:18Class properties vs methods
- 23:28Text for readability
- 32:28Readable block diagrams
- 41:16Error wires
- 43:47Reference wires and connectors
- 45:33Avoid mother cluster
- 50:08Labels and free labels
- 52:33Summary
related talks
07m6x7 NASA LabVIEW Peer Review Tool
30mDoes Your Code Hurt?
01h 03mKeynote: Abstraction Patterns
39mYou should stop writing code
48mA Personal Philosophy of Excellent Engineering
15mThe Uncomfortable Truth of Bad Code
54mReadable Code: The Secret to Clean, Productive Software
27m'The Art of Software Development'