how do i know that im good in labview

[Yamaeda]

---

@Intaris wrote:

Actually looking back at old code and not crying is a good sign that you've matured as a LV developer.  It all depends on your definition of "old" of course.

---

Yesterday ...

/Y

[billko]

---

@Intaris wrote:

Actually looking back at old code and not crying is a good sign that you've matured as a LV developer.  It all depends on your definition of "old" of course.

---

Matured enough to look at your poorly written code and not cry, or matured enough to have written code good enough not to make you cry?  😉

Or maybe a little of both...

[crossrulz]

---

@billko wrote:

---

@Intaris wrote:

Actually looking back at old code and not crying is a good sign that you've matured as a LV developer.  It all depends on your definition of "old" of course.

---

Matured enough to look at your poorly written code and not cry, or matured enough to have written code good enough not to make you cry?  😉

Or maybe a little of both...

---

A little of both.

I'm still quite happy with code I wrote a year ago.  Looking at code from 2-3 years ago doesn't make me cry (I still remember why I was forced into the stupid coding corners).  But any more than 5 years ago, my code is just embarrassing, even though I had LabVIEW "figured out" and had my CLD.  I'm not even going to talk about my code from a year after I first started with LabVIEW (when I started to "figure it out").

[Oligarlicky]

• The coder that inherits your code doesn't curse your name too often
• The users that use your code daily call to ask for bug fixes and new features only every now and then

[billko]

I've learned to code even "engineering tools" with care and attention because, in reality, an engineering tool is just an application that hasn't been born yet.  At leas that was the destiny of just about every single engineering tool I'd ever writeen.