This channel is intended for people just starting with the Raku Programming Language (raku.org). Logs are available at irclogs.raku.org/raku-beginner/live.html
Set by lizmat on 8 June 2022.
Superstart033 What’s the best way to start with Raku? 02:23
MasterDuke m: start say "this way perhaps" 02:29
camelia ( no output )
Nemokosch phunny 07:58
depends on your former knowledge I think 08:00
doesn't explain ::Type kind of captures, I think
I mean, if you are familiar with programming, especially a scripting language (JS, Python, Ruby, possibly Perl), you could do what I like to do: find reasons to use Raku and pick up structures on the way, asking around 08:04
masukomi yeah, i'm going to second what <@297037173541175296> suggested. I think the best way to learn _any_ new language (assuming you know how to program A language relatively well) is to find something you want to build in it and start building. 13:16
If you're sticking within OOP / Procedural paradigms (which most people are) then it's really just a matter of going "ok i need a loop. What is this language's syntax for a loop"... or case statement, or whatever." From a user perspective they're all essentially the same just with different sigils to express the same ideas.
The only time there's notable... impedance mismatch between your knowledge and how it's invoked is when you start crossing the border between OOP and Functional programming.
--
One additional thing I do which i think helps learning many languages is to write unit tests for how i _think_ a thing works. Like really _really_ simple things. The result both proves/disproves my understanding AND acts as a reference for later on when i'm like "wait, how do i do a case statement in this language?"
yeah, i'm going to second what <@297037173541175296> suggested. I think the best way to learn _any_ new language (assuming you know how to program _A_ language relatively well) is to find something you want to build in it and start building. 13:17
If you're sticking within OOP / Procedural paradigms (which most people are) then it's really just a matter of going "ok i need a loop. What is this language's syntax for a loop"... or case statement, or whatever." From a user perspective they're all essentially the same just with different sigils to express the same ideas.
The only time there's notable... impedance mismatch between your knowledge and how it's invoked is when you start crossing the border between OOP and Functional programming.
--
One additional thing I do which i think helps learning many languages is to write unit tests for how i _think_ a thing works. Like really _really_ simple things. The result both proves/disproves my understanding AND acts as a reference for later on when i'm like "wait, how do i do a case statement in this language?"
yeah, i'm going to second what <@297037173541175296> suggested. I think the best way to learn _any_ new language (assuming you know how to program _A_ language relatively well) is to find something you want to build in it and start building.
If you're sticking within OOP / Procedural paradigms (which most people are) then it's really just a matter of going "ok i need a loop. What is this language's syntax for a loop"... or case statement, or whatever. From a user perspective they're all essentially the same just with different sigils to express the same ideas.
The only time there's notable... impedance mismatch between your knowledge and how it's invoked is when you start crossing the border between OOP and Functional programming.
--
One additional thing I do which i think helps learning many languages is to write unit tests for how i _think_ a thing works. Like really _really_ simple things. The result both proves/disproves my understanding AND acts as a reference for later on when i'm like "wait, how do i do a case statement in this language?"
yeah, i'm going to second what <@297037173541175296> suggested. I think the best way to learn _any_ new language (assuming you know how to program _A_ language relatively well) is to find something you want to build in it and start building. 13:18
If you're sticking within OOP / Procedural paradigms (which most people are) then it's really just a matter of going "ok i need a loop. What is this language's syntax for a loop"... or case statement, or whatever. From a user perspective they're all essentially the same. They just use different sigils to express the same ideas.
The only time there's notable... impedance mismatch between your knowledge and how it's invoked is when you start crossing the border between OOP and Functional programming.
--
One additional thing I do which i think helps learning many languages is to write unit tests for how i _think_ a thing works. Like really _really_ simple things. The result both proves/disproves my understanding AND acts as a reference for later on when i'm like "wait, how do i do a case statement in this language?"
yeah, i'm going to second what <@297037173541175296> suggested. I think the best way to learn _any_ new language (assuming you know how to program _A_ language relatively well) is to find something you want to build in it and start building. 13:19
If you're sticking within OOP / Procedural paradigms (which most people are) then it's really just a matter of going "ok i need a loop. What is this language's syntax for a loop"... or case statement, or whatever. From a user perspective they're all essentially the same. They just use different sigils to express the same ideas.
The only time there's notable... impedance mismatch between your knowledge and how it's invoked is when you start crossing the border between OOP and Functional programming.
--
One additional thing I do which i think helps learning many languages is to write unit tests for how i _think_ a thing works. Like really _really_ simple things. The result both proves/disproves my understanding AND acts as a reference for later on when i'm like "wait, how do i do a case statement in this language?" it also just gets me actually typing more code in that language, instead of just thinking