Decoupling in Practice - How Good Software Engineering Can Save...
summary
Claims that long LabVIEW load and build times come from unexpected cyclic and deep dependency chains, with real cases like 20 minutes to load and builds stretching toward 1–3 hours. Diagnostics use the project dependency view and an old John McB tool. Fixes that actually work: move typedefs and helper VIs out of classes into foundational libraries, break cycles with interfaces or one‑way module calls, and remove accidental parent→child links.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:19How LabVIEW loads dependencies
- 3:04Dependency chains and cycles
- 6:37Why decoupling matters
- 8:05Coupling mistakes to avoid
- 9:27Type definitions causing issues
- 11:32Nested libraries risks
- 12:54Accidental class dependencies
- 14:38Unnecessary class calls
- 15:44When coupling is appropriate
- 16:26Parent calling child methods
- 17:50Legacy project fixes
- 18:10Coupling in Actor frameworks
- 19:54Decoupling DQMH modules
- 21:22Lessons on cyclic dependencies
- 22:23Q&A
related talks
58mGetting a grip on your code dependencies
44mDependencies; Devil or Darling?
01h 38mBreaking Dependencies: The Path to High-Quality Software
50mBehind the Scenes of the LabVIEW Compiler
54mBreaking Down Your Build: Architectural Patterns For A More Efficient Pipeline
28mI've Fallen Into a Large Codebase and I Can't Get Up!
35mKnowing Your TCO (Total Cost of Ownership)
56mLaw of Demeter: A Practical Guide to Loose Coupling