Been working on @elmlang for over a decade now, so I put together some fun stories to celebrate.
Met so many lovely people through this project, and it was a heartwarming surprise to see so many of you in the chat 🥰
Thank you @realmario for organizing!
https://t.co/yFJA9XkWDR
Finished! 🎉 Done in @elmlang (and @tailwindcss) in under 90min (@dan_abramov 👀), if this tweet gets enough likes I'll do it live next Saturday on @Twitch! 🥳
Want to join us creating next level tools for cinemas? We're looking for a cloud engineer, either part time or contractor. Read more at https://t.co/Lf61IFgGlS
Want to work with #elmlang and #GraphQL? We're hiring frontend engineers at https://t.co/Q4DrPekGmO
DMs are open if you have any questions.
https://t.co/Ap5mXAQRn7
What got me into this way of thinking was @elmlang and https://t.co/xyQVx5BtAy and I think it's a powerful approach. Kinda worried it'll make everything less flexible in the end.
How much implementation can I avoid by modeling the domain more accurately? There's probably a sweet spot for minimizing complexity for both but I'm curious where that spot is.
I'm usually quick be really naive about the data model and solve ALL THE THINGS in code, but I'm trying a different approach where a lot of the domain is encoded into the model.