My name is Łukasz Niemier, but I am mostly using Hauleth over the internet.
I am part of the Erlang Ecosystem Foundation Observability WG where we are trying to improve observability features in Erlang ecosystem.
I am open for hire. If you want to inquiry me about my services then contact me at lukasz@niemier.pl.
On Lobste.rs I have found today the article written by the Charity Majors - CTO of the Honeycomb.io "AI enthusiasts are in a race against time, AI skeptics are in a race against entropy". This was pretty good read until there was this question posed:
What would it take for you to feel comfortable shipping code to production without reading it?
Furthermore, I think that mocking must be destroyed.
This story is not about a goal, but friends optimisations we met along the way.
Some time ago, there was an anime available on Netflix — Godzilla Singular Point. It wasn't a spectacular success, but it featured a plot device that I think reflects something increasingly common today: you need to know the answer to your question before you can ask it.
This is something I see all the time in the current wave of AI hype. You need to know what the answer should be before you can write a useful prompt.
In Elixir 1.11 landed set of new features that allows for more powerful logging by utilising Erlang's logger features. Here I will try to describe new possibilities and how You can use them to improve your logs.
mix.exs? It comes out as quite powerful and useful place for storing configuration and post-launch scripts.