The course is aimed at humans who:
– are at least 12 years old,
– have no significant experience with any programming language,
– have good working command of English.
There’s no upper age limit or any further restrictions.
When *: Fridays: November 29, December 6 and 13
Intensive course : 3 meetups/4 hours each
Enroll -press the button JOIN ENGO!
Where: Business Center “Karat”
Khmelnitskogo St., 7 , Metro: “Akademija navuk”- Academy of Sciences, right beside cinema October
Get your tickets now.
And here’s our itinerary.
When an artist goes on tour, their luggage is impressing. U2 once employed 120 trucks, and Beyoncé needed 7 Boeing cargo planes for their tours.
2. Taking Travel Notes: Variables and Arrays.
Marco Polo was the first to describe his travels to Asia, and he probably took a lot of notes en route.
Likewise, your program needs to remember structured information. That’s what variables and arrays are for. We’ll also discuss data types and basic arithmetic in this course section.
3. A Map to Follow: Functions.
Christopher Columbus was sure to have reached Asia, but he was wrong, as we now know. This is what happens when you don’t have a map.
If you write your program without a plan, your code will be a mess.
Functions are an excellent means for structuring your program, for developing reusable tools, for writing clear code.
4. Road Fork: Checking Conditions.
You can fly non-stop to more than 50 destinations from Minsk airport.
We usually need fewer options in programming, but still we frequently have to choose the direction of further program execution.
5. A Place to Come Back to: Loops.
When Magellan came home from his trip around the world – the first such trip in history, he was probably too exhausted to repeat it.
But in programming, some snippets of code are repeated millions of times: to process big data, to serve many customers etc.
Most travels are driven by mere curiosity. Hillary’s and Tenzing’s epic climb of Everest had largely symbolic value.
7. Travel Bug: Dealing with Errors in Your Code
Most things went wrong on Livingstone’s search for the source of the Nile: disloyal assistants, stolen supplies, failing health.
Likewise, freshly written software rarely runs exactly as planned. Errors are inevitable. And there are tools for working with them, like debugging, logging etc.