How often has this happened to you?

[Ray.R]

Ben,

If the original program did not do what it was intended to do (notice I did not use the word design), then you are actually writing the app that never was..

[Hummer1]

I am finding that I can't even understand the vi's I put together last year.  I like the Front Panels though and can probably strip a few valuable subVi's out of them, and that is what I intend to do "when we need to change them".  The old code and the documented operations problems become a very good functional specification for the new code.  The Design Specification and coding can make use of the subVi's that worked well...then new structures (patterns) are those that fit the problem now that I have been reading and listening to you guys.  So, old dogs, new tricks.  Is it really a "complete rewrite" if you still use the front panel designs and major functionality and simply restructure the operation for speed, security, memory use, reliability and maintainability?  There is a great deal of value in finally figuring out "What to do", even though the "How to do it" part may be lacking.

Hummer1

"Just jack up the radiator cap and drive a new car under it!"

[Brian_Beal]

I am now at a point where I am going back a re-writing some of my first programs.  52 sequence frames?  Did I really need to do that? No! After being asked to add features, and doing it, they had become monsters.  Start from scratch with the idea that features will need to be added, and you will be much happier in the long run.

[Ben]

---

Brian Beal wrote:

I am now at a point where I am going back a re-writing some of my first programs.  52 sequence frames?  Did I really need to do that? No! After being asked to add features, and doing it, they had become monsters.  Start from scratch with the idea that features will need to be added, and you will be much happier in the long run.

---

You were hidding that from me where you?

Ben

[Brian_Beal]

Ben-

Of course I was!  I only let you see the OK stuff, not the embarrassing stuff.

[Hornless.Rhino]

---

Brian Beal wrote:

52 sequence frames

---

One for every week of the year 🙂

[JÞB]

Update:

Thanks for the continued support (and occasional Horror stories)  Its good to know I'm not alone.

So- we are not only refactoring- But, I managed to get assigned to take on a three phase project to move into a LVOOP based, totally reusable, Test class engine.  (so I'm re-refactoring) Or, in the words of this threads posters, writing the test executive that never was.  I've been awful lucky  The first phase will be a LOOP (no class definitions to confuse management) project.  The next will expand the test step definition and include resources in the definition, the third phase translates to LV classes.

Advice welcomed,  Having a ball with this now!

[Ray.R]

I have to get deeper into LVOOP, otherwise one day, I'll end up in POOP.  😉