https://rbino.com/Recent content on rbinoHugoen-us© rbinoSat, 26 Apr 2025 00:00:00 +0000https://rbino.com/talks/Sat, 26 Apr 2025 00:00:00 +0000https://rbino.com/talks/Here’s a collection of talks I’ve given at conferences, meetups etc. TigerBeetlex for Zig developers (video not available) Beyond your first NIF (video not available yet) TigerBeetlex: an Elixir and Zig love story Craft your query DSL with NimbleParsec and Ecto Distributed Zig with Elixir and Zigler Beyond the MQTT Broker (video not available) Party like it’s 1989: Making Music with a Game Boy (italian) Audio Production on Linux (italian) Git first steps (italian)https://rbino.com/posts/build-dot-zig/Wed, 13 Dec 2023 08:05:42 +0100https://rbino.com/posts/build-dot-zig/A nice byproduct of my work on TigerBeetlex is a library called build_dot_zig. It’s similar to elixir_make, but it allows you to use the Zig build system instead of make to define your build steps and have them automatically execute during mix compile. You just put a build.zig file in your project root, add :build_dot_zig to your Mix compilers and you can start leveraging it as a build system for your NIFs, or in general to Do Stuff™.https://rbino.com/posts/wrap-your-nif-with-zig/Wed, 09 Aug 2023 23:47:17 +0200https://rbino.com/posts/wrap-your-nif-with-zig/If you’ve heard about Zig, you’ve probably heard about comptime, its mechanism for doing introspection, metaprogramming, and more. I’m probably in my honeymoon phase with comptime and I like to throw it at almost everything. The great thing about it is that you write some code and think “This makes sense, will it Just Work™?” and it actually does. Today I’m going to show you an example of how it can be used to abstract away some common code that appears at the beginning of all Elixir1 NIFs, allowing the resulting code to be more clear in its intentions by removing some mechanical noise.https://rbino.com/posts/rock-paper-scissors/Mon, 05 Dec 2022 12:19:47 +0100https://rbino.com/posts/rock-paper-scissors/This is an external post of mine. Click here if you are not redirected.https://rbino.com/posts/zig-stm32-blink/Tue, 13 Apr 2021 22:53:00 +0200https://rbino.com/posts/zig-stm32-blink/I recently discovered the Zig programming language thanks to this post, which first caught my attention for the mechanical keyboards background. I liked the premise of Zig’s aim to be a “better C”, as opposed to other languages (e.g. Rust) that tend more towards “better C++”, so I decided to give Zig a try and use it to do something I would usually use C for: programming a microcontroller. This post will walk through the example, discussing some of the choices I’ve made and the tools I used.https://rbino.com/posts/hello-world/Thu, 01 Apr 2021 00:59:54 +0200https://rbino.com/posts/hello-world/Here’s a shiny new blog, I will try to fill it with some content. I’m writing the first post on the 1st of April so I can have my easy way out.https://rbino.com/about/Fri, 18 Oct 2019 00:00:00 +0000https://rbino.com/about/Hi, I’m Riccardo! During the day I mostly do backend development using Elixir, but I also like messing with other stuff like embedded development, electronics, music, and cooking. I’m a strong believer in having many different tools in the toolbelt to avoid using a hammer to plant screws. I’m a big yak shaver and I tend to start a new project before I’m finished with the old one. This blog is also meant to force myself into finishing things so I can write about them.https://rbino.com/license/Fri, 18 Oct 2019 00:00:00 +0000https://rbino.com/license/Content license All non-code blog content is licensed under the Creative Commons BY license. Code license All source code files and snippets found on this blog, unless otherwise explicitly noted, are licensed under the MIT license, as reported below. Copyright © Riccardo Binetti Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: