Rube Goldberg Code

[Broken_Arrow]

People that "grew up" on dynamic data and Express VIs tend to do this. I hope the compiler knows better. 

[altenbach]

Slicing and dicing a JSON string like a master sushi chef! (no toolkits) can be done in many ways. Some fit on a quarter postcard!

Seen here

[MatthiasAr]

---

@altenbach wrote:

Slicing and dicing a JSON string like a master sushi chef! (no toolkits) can be done in many ways. Some fit on a quarter postcard!

---

Yes, made to the Rube Goldberg thread. 🤣

That's what happens when you want to code someting by learning DIY hardly any training and no one to ask for advice. I asked the question to learn and improve

[altenbach]

---

@MatthiasAr wrote:
Yes, made to the Rube Goldberg thread. 

---

No shame in that. It is always an honor to be mentioned! Congratulations!

(After using LabVIEW for almost 30 years, sometimes looking at my own code from 10 years ago (i.e. written with 20 years of daily programming experience!) makes me cringe. 😄 Hey, I can do that with half the code!)

[altenbach]

Parsing a file can be hard and might require many loops, multiple delete from array and insert into array, even detours to 3D arrays! (seen here)

Or it could be done with much less:

[santo_13]

---

@altenbach wrote:

Parsing a file can be hard and might require many loops, multiple delete from array and insert into array, even detours to 3D arrays! (seen here)

Or it could be done with much less:

---

At least, the developer documented the code well with wire labels and comments.

[altenbach]

Two ways to close a polygon:

(The version on top was seen here. I suspect that it was intentional to track student plagiarism. 😄 )

[alexderjuengere]

---

@altenbach wrote:

(The version on top was seen here. I suspect that it was intentional to track student plagiarism. 😄 )

---

😉

[raphschru]

Here is some FPGA Rube Goldberg code for flattening multiple clusters and arrays into a single (fixed-size) array of U32. Sometimes the need for resource optimization pushes the developers to try all sorts of weird workarounds (seen here). It adds unnecessary delays because of all the shift registers, and uses lots of resources because of all the insertions at variable indexes (useless because the output array has the max size anyway).

Which is equivalent to this:

[elset191]

I can't speak to that specific use case, but looks like they were trying to do some pipelining, as illustrated in the examples here:
https://www.ni.com/en/shop/electronic-test-instrumentation/add-ons-for-electronic-test-and-instrumen...

Edit: clicked the link in the post and saw the discussion discussing exactly this