Exploratory poll about code-heavy tutorials Progr...

# getting-started

[Aleksey Zamulla]

Exploratory poll about code-heavy tutorials

Programming tutorials, especially “Getting Started” (for example, for Kotlin Multiplatform), are often written like this:
1. Create a file.
2. Copy this code to the file.
3. Create another file.
4. Copy that code to the other file.
5. And so on.
But a good tutorial is supplemented by the example project with all these files if you want to avoid copying-pasting.

What do you do more often when following these tutorials: copy and paste to create your own project or explore the ready-made project supplied in the tutorial?

Please choose the walking Kodee if you usually create example projects by hand kodee walking or the loading Kodee kodee loading if you typically learn by exploring a ready-made project.

You're welcome to comment if you have something more nuanced to share!

[CLOVIS]

Third option! Learning by reading articles that explain how things work in general.

In my opinion, the Rust community does it very well:
• The Rustlings course for people who want step-by-step actions,
• Rust by example for people who want commented examples,
• The Rust book for people who learn by reading the theory.

[Aleksey Zamulla]

@CLOVIS Yeah, tutorials are definitely not the only way to learn. “Rust by example” is close to what I'm talking about — you can copy examples from the docs one by one, line by line, or just go to GitHub and clone everything at once.

[Pablichjenkov]

I do both ways.