Digests » 143
Manage your visual assets like you manage your code. Collaborate on design socially with resolvable image discussions. You can easily target a specific coordinate of an image and start a discussion around it. Image discussions are available in merge requests and commit detail views.
this week's favorite
When coming from object-oriented languages, I often hear people ask the question, “How do I organize my code? Modules are just bags of functions!”. That is a question I asked myself as well, but after using Elixir and Elm for a while, I have noticed that there is a principle of organization that I keep using and that I see in the wild. I like to think of it as the principle of attraction.
Some time ago we have already mentioned Ecto while we were describing Ecto models. Ecto quite a big topic, which we cannot cover in a single post. Today I would like to talk again about Ecto and describe Ecto Queries.
Many functional languages have the concept of a Result type. It is a data structure that represents the outcome of a function that could return either a value, or an error. A classic example of this would be the output from a simple HTTP call. The HTTP call either returns the body of the response, or in the case of an error, an error code.
I recently found myself wishing for the simple convenience of a while loop in Elixir. I had a test where I wanted to loop and test a condition, and either break out of that loop, or time out after some period.
I’ve been looking forward for a while now to write a little Telegram Bot guide in Elixir with TELEX (awesome bot api made by Rock Neurotiko, check his GitHub rather than his Medium profile… ehem, ehem…).