The opposite of getting the "clay" like feedback is putting all the punch cards in the hopper and waiting many minutes to find out if the computer liked the stack or ejected a card. The computer should be more like a bicycle for the mind, and less like something that gets back to you when it is good and ready.
you don't have mutable data, data is always immutable, what is mutable is the memory, the storage where we put that data in. Variables & pointers are an abstraction on memory, for direct & indirect access respectively, and what functional programming is about is to make our code dependent on values and not on memory locations, traditionally the FP community call this, referential transparency, but the clever guys for the imperative world have given it a better name, value semantics.
ok, tell me you don't understand types without telling me you don't understand types. *types don't fix the understanding of anything.* *types are markets, tags that track code where certain assumptions about the code where made* so when you need to make changes you can follow the types and change all the places where you have changed your assumptions and understanding.
James Trunk presentations are always interesting and well structured!
Thats true!
Loving that manifesto!
‘AWS for banking’ - wish the best of success, sounds really cool! :)
The opposite of getting the "clay" like feedback is putting all the punch cards in the hopper and waiting many minutes to find out if the computer liked the stack or ejected a card. The computer should be more like a bicycle for the mind, and less like something that gets back to you when it is good and ready.
I thought of sculpting with clay vs stone.
you don't have mutable data, data is always immutable, what is mutable is the memory, the storage where we put that data in. Variables & pointers are an abstraction on memory, for direct & indirect access respectively, and what functional programming is about is to make our code dependent on values and not on memory locations, traditionally the FP community call this, referential transparency, but the clever guys for the imperative world have given it a better name, value semantics.
Thanks, great talk!
off topic, but does anyone know what the widget is/does that says "in x hours/minutes"?
nice!
Awesome
ok, tell me you don't understand types without telling me you don't understand types.
*types don't fix the understanding of anything.*
*types are markets, tags that track code where certain assumptions about the code where made* so when you need to make changes you can follow the types and change all the places where you have changed your assumptions and understanding.
check out the “spec-ulation” and “maybe not” talks by rich hickey.