2016 Advanced User Track
TS9518 : How Applying Agile SW Design Principles Changed My Designs and Code
Dmitry,
At the beginning of your presentation you polled the room to see how many people came from a Computer Science background and although the video did not show the entire room, my guess is that it was a much smaller percentage compared to those who come from the Electrical or Mechanical disciplines. I too fall in the latter camp and much of the core principals of proper CS I learned from looking at and modifying quality LabVIEW code.
I consider myself a competent, advanced LabVIEW user and I do have a passing grasp of the OO teneants of encapsulation, inheritance, polymorphism/dyanmic dispatch; but that is a far cry away from actually implementing a design using GOOP. I have just enough knowledge to realize that your presentation was packed full of sage advice but nowhere near enough knowledge to fully understand why; I particularly failed in the UML diagrams. What advice do you have for those of us who don't have extensive knowledge on OO principals & design but realize they are falling behind the curve by not understanding such things?
As LabVIEW syntax continues to take on more modern-day features, I feel the divide between the formally trained CS users and the non-CS users will grow exponentially. I've not yet found a good bridge between something any CLD should know such as the QMH and the Actor Framework. Either you understand OO and "get" the Actor Framework, or you don't; and if you don't you fall back on the non-OO things you do know. I wan't to break this cycle but I'm not sure where to start.
