Digests » 114
Amazing insights into errors and performance issues, plus host metrics and an easy to use custom metrics platform.
This process had a few major issues. It was an all or nothing deal - either your data had issues and it would fail to import, or it was perfectly clean. It also didn’t provide any feedback on what the status of anything was; you just saw an indefinite spinner until you didn’t anymore. To make matters worse, if there was an issue, you often got an error message that didn’t tell you how to fix your source data.
One of the first and most impressive characteristics I saw when I started to study Elixir was the powerful yet simple built-in tools to help developers write documentation and tests.
Deploying a new version of an application can be a scary. When you’re putting a lot of work into crafting beautiful code and building great features, things can get messy and things can break. So once you’re finally prepared to push that deploy button, there’s always an unnerving uncertainty: Is it still going to work?
A high performance web crawler in Elixir.
A few months ago I posted describing my journey learning elixir and basically speed coding in my spare time to do so. The project was a community site with reddit-like threads and rooms. It was chosen in order to explore as much of elixir as possible not only from the language mechanics perspective but deployment, whether it is prepared for a wide range of needs, day to day viability stuff basically.