Re: [elm-discuss] What concepts and models did you had to learn in order to be able to write good Elm code?

[John Orford]

the two themes I learned were:

simplicity & accuracy

simplicity: fewer concepts to learn than most languages

accuracy: following on from simplicity, lack of 'features' to shoot
yourself in the foot, leads to type checking and guarantee goodness

On Thu, 11 Aug 2016 at 16:59 Leroy Campbell  wrote:

> I'd say learning how to make illegal states unrepresentable.
>
> https://vimeo.com/162036084
>
> --
> You received this message because you are subscribed to the Google Groups
> "Elm Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elm-discuss+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[elm-discuss] What concepts and models did you had to learn in order to be able to write good Elm code?

[Leroy Campbell]

I'd say learning how to make illegal states unrepresentable.

https://vimeo.com/162036084

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[elm-discuss] What concepts and models did you had to learn in order to be able to write good Elm code?

[Peter Damoc]

"The fundamental fact about learning: Anything is easy if you can
assimilate it to your collection of models. If you can't, anything can be
painfully difficult.” - Seymour Papert

I'm trying to come up with a sorted list of concepts and models that a
prospective Elm user needs to learn in order become proficient in Elm.

Here is my list (I actively tried to keep it short) :

- types : the concept that information flowing through an Elm program has a
specific type and that the compiler will not accept the wrong type.

- type composition: the concept that types can be composed into more
advanced types using union type syntax and record syntax.

- type variables : the concept that you can have a type constructor that
can take arguments and produce a custom type (List, Maybe, etc)

- functions as types: the concept that you can give functions to other
functions in order to customize their application.

- currying/closures: the concept that you can take a multi argument
function and produce another function that has some of those arguments
applied.

- declarative: the concept that the Elm programs are made of one big
function that returns a specific type instead of a series of instructions.

How does your list looks like? Which one gave you most troubles? Which one
did you find most  amazing | useful | mind-blowing ?





-- 
There is NO FATE, we are the creators.
blog: http://damoc.ro/

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.