Stefan Luptak

@stefanluptak.com

Elixir Developer@recycla.se Bratislava, Slovakia

So much useful knowledge from the @render.com community forum is now gone... I have visited that page just a few weeks ago. Now wanted to check some info there just to find out they did move to Discord only two days ago. No upfront e-mail notice, not to mention the Discord content won't be indexed 🤦‍♂️

Introducing `Ash.TypedStruct`, a nice convenient wrapper around creating struct types 🎉. It doesn't do typespecs, as we're waiting for the type system to add generated types in Ash, but you get all the other benefits, including automatically supporting OpenAPI & AshGraphql. #AshFramework #ElixirLang

Bild

I hope I'll see a day when we won't care about files and directories when programming. Just modules and functions (or types for that matter). Having to think about the file structure feels redundant. I want to work with the code similar to a mind mapping tool.

I keep a draft PR open for our app to try CI against the main Elixir branch (1.19). There were so many warnings I thought it's nonsense. But then I looked closer and realized it found calls to non-existing fields on schemas being passed through multiple layers without pattern matching 🤯 #elixirlang

I mean this in the most positive way, but I feel like the "Official Elixir LSP" effort deserves some communication towards the community. Many (I hope) of us (or our companies) have set up sponsorships to help it, but after 1/2 year we have no idea what's going on. Or I missed something? #elixirlang

Any idea why am I seeing `:erlang.binary_to_existing_atom("...")` in my @appsignal.com error? Three dots instead of the problematic string isn't very useful. AppSignal is showing a warning "Backtrace regex did not match" for that line, but I have no idea what that means. #elixirlang

That feeling when trying to configure NeoTest in LazyVim as a total noob only to realize after a few days, that I had a typo in otps vs opts. 🤦‍♂️😅

I wrote a new article exploring how set-theoretic types (the foundation of Elixir's type system) could address how many statically typed languages do not allow libraries to evolve their data definitions in a backwards compatible manner: dashbit.co/blog/data-ev... - be warned, it is a long one.

Data evolution with set-theoretic types - Dashbit Blog

In this article we explore the challenges of data evolution in static typing and explore type safe solutions.

dashbit.co