# How buggy is the Agilent VEE programming environment?

**URL:** <https://boards.straightdope.com/t/how-buggy-is-the-agilent-vee-programming-environment/567936>\
**Category:** In My Humble Opinion\
**Created:** [January 17, 2011, 1:40pm UTC](https://boards.straightdope.com/t/how-buggy-is-the-agilent-vee-programming-environment/567936 "2011-01-17T13:40:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Napier](https://avatars.discourse-cdn.com/v4/letter/n/ce73a5/32.png) [@Napier](https://boards.straightdope.com/u/Napier)\
**Post date:** [January 17, 2011, 1:40pm UTC](https://boards.straightdope.com/t/how-buggy-is-the-agilent-vee-programming-environment/567936/1 "2011-01-17T13:40:43Z")

</div>

How buggy is the VEE programming environment, by Agilent? VEE is typically used for data acquisition and is similar to LabVIEW. However, LabVIEW is so buggy that it is hard to use for any but small projects, and managing frequent updates that introduce new bugs is time consuming. I’ve given it up as unproductive. How does VEE compare?
