Hi,
Is anyone may help me to understand how a recursive code works?
I ve watched the online course from Long NGuyen and he s showing this recursive code at [35.57]minutes:
Recursion is a common coding situation where a Method calls itself until some (or several) stop condition happens (if you fail to prevent a safe exit … you’ll get a frozen computer).
I would strongly advise to get the gist of the concept via some simple entry level cases (like dividing a Rectangle etc).
Given the length of the C# walk … beginner means 0.001.
I’ll see what ultra simple stuff is available (but the problem is that my defs are written for real-life … meaning lot’s of lines and/or freaky Methods and/or you name it).
Thank you Peter
I got the code from someone else I ll check it and try to get how it works.
How did you learn coding?
any advises or materials suggestions?
Forget Internet. Turn computer off. Get some proper C# books. Isolate. Read’m many times (even if you don’'t understand an iota [ for instance: Classes, Events, Threads, Object oriented code etc etc]). Then read’m again.
When it’s time to use the computer? Who knows? And who cares?
Just before you do the right thing get the attached. Note that the exit conditions are 2 (could be far more). In general: use as many public vars as you can. Before adding some code mastermind the exit (better safe than sorry).
Tip 1: C# is kinda martial arts: the first 10 years … are a bit tough.
Tip 2: The ultimate scope of coding is NOT to do things but to know when NOT to do things.
As I said many times … geometry is nothing (even kids can do it: just look around you). But managing geometry in the broad/optimum sense is the core of the matter. If you plan to learn coding for doing wild forms and the likes … you miss the point by a million miles (and sooner or later you’ll pay a very heavy price). That said Parametric should serve the rational … instead it serves the art of pointless (but the history of mankind is full of similar things).
Besides in our trade there’s the BIM thingy as well. Meaning that you should pick some proper app for that (my stuff: AECOSim/GenerativeComponents + various Bentley Systems Verticals + ProjectWise + CATIA + SiemensNX). Meaning that R/GH are just a tiny part of the whole story. Meaning that you should ALWAYS take into acount solution/code portability … and the ways that teams deliver the goods in real-life.
All that until AI hits the masses. Dig a big rabbit hole. Or better marry a rich girl and change trade: Architecture (as we know it) has very limited future in the very same way that AutoMotive design is in the hands of big Corporations (who knows/remembers Bertone/Giugiaro/Earl/Callum/… ?).
Anyway … before walking the walk read this (many times):
Thanks for the books suggestion.
I m working on plan automation. I did a MS 2 years ago and worked previously on parking automation in JavaScript for a French company. I m trying to reproduce the solution in rhino through C# and then go further and probably in the deep field of AI. I m looking to meet people interested in those fields to interact share our thoughts and be inspired
Did that many years ago (Fuzzy Sets, HAC Clustering, Ill Defined Problems, MOO, … , 40K lines of code blah, blah). It’s just another rabbit hole promoting - implicitly or explicitly - the anathema of our times: the 3rd market sector (i.e. Services) AND thus cities (until a mega city would cover the whole &#^#% planet).
C Alexander would be greatly surprised with the direction of things (but that was expected).
Note: The Light At The End Of The Tunnel Is A Train.