We’re excited to announce Elm Japan 2020, the first conference in Asia about @elmlang!
Join us in Tokyo on April 4th, 2020 for a great day of knowledge exchanges and community bonding.
#elm#elmlang#elmjapan#elmjapan2020
https://t.co/bRV6pjKkqN
These principles show up all over the place. Just a few examples:
* Dealing with memoization in #Ruby https://t.co/8Squ4XpE13
* Working with Maybe in @elmlang https://t.co/od7t5G7zim
* Structuring automated tests https://t.co/KRKsleLNCD
I like to think of these as forming 3 sides of a triangle. This is the same principle viewed from slightly different perspectives
1. Write functions at a single level of abstraction
2. Push conditionals up the decision tree
3. Separate decision code from "doing" code
I burnt $17.25 today thanks to this poorly positioned sign that should have apparently warned me that NO CHANGE WILL BE GIVEN. #errordiary#badDesign#badUX
don't forget to also check your local machine (for the backdoor, https://t.co/9pjp2pYSwx, ICYMI)
find / -type d -name "event-stream" -print 2>/dev/null
🔮 What’s the future of WebAssembly?
And how can WebAssembly level up—both inside and outside the browser?
Here’s a skill tree to lay it all out → https://t.co/NZfjvL3CWe
Loved @itsmegrantmaki's talk at @elmconf about cultural change in teams.
Excellent insights born from experiences at Ford. Definitely helpful when folks ask me about how to introduce @elmlang at work. It's funny and has heart too. Great work! (Really!)
https://t.co/mpfNftnhjV
Beautiful read on side effects, dependency injection and the Effect functor in #javascript - incidentally preventing thermonuclear war and explaining how tensor flow essentially works:
https://t.co/S7KqUzsZ45