LVOOP: Lesson Learned (not a question, just sharing experience)

[Ray.R]

I know the feeling  😞

[Norbert_B]

---

@JÞB wrote:

[...]Bing translates as "Is planning to replace random error" (German grammar confuses me but,  "The purpose of planning is to limit random errors"?)

---

My experience with such translation boards is that they don't take punctuation into account (as well as semantics it seems). So, Bing seems to translate a statement into a question.

So to correctly elaborate my free translation, the saying would sound like this:

Planning (as process) replaces random errors (happen by chance) with mistakes (misunderstood/incomplete requirements, overly optimistic view of task/resources, ...).

Hope this clears things up.

Regarding the LVOOP book/documentation:

When talking about the Actor Framework, i use to go for the NI Week presentation, which shows the "origin" of the Actor Framework. I find this very helpful for understanding its purpose and possibel use-cases.

[hecmar.arreola]

I think where I'm currently struggling is wrapping my UI up in LVOOP.  It seems like I get all my LVOOP classes figured out and make their methods and properties as easy to use as I can... but then I resort to orchestrating them in my UI.  So my UI not only controls my UI elements but also has the authority over all my objects and it never seems like a good design.

Still learning...  I'm just now getting familiar with the Actor Framework and it seems to hold solutions to my problems.  I just need to sit down one of these weekends and solve a problem using it.  I've gone through the literature and the examples but until you solve a new problem with something you never will master it.