While attending local DevClub focused on hiring I could not miss a chance to reflect on the problems we are facing. Because I've been wearing many hats before I introduced a co-dependant perspective of the existing market (2024).
I've build go-omap and it's tiny library, that provides convenient wrapper around go maps and slices to provide a more convenient API for managing items that needs fast access, but also must be ordered at the same time.
Go v1.23 has been released just yet. With iterators being the most discussed feature there are couple more changes. Today I made a tiny experiments with the freshly baked unique library, that is now a part of std. What problem is it addressing? It is simple and short: comparison. The unique is working with comparable interface and it is here to improve the way we compare what's comparable. In reality it might be easy to compare ints, floats and strings and do not even consider any improveme
How I thought I found a silver bullet for application configs, but it turned out I overcomplicated things again for my tiny application. By the way there is a Youtube video I made recently where I show all the details of my Pkl experiments and it is based on the same notes this article was written. Years ago, when I started working as software developer I had no major choice of how to configure my application. I was using PHP and Javascript and mostly frameworks or platforms, like Symfony
The condensed introduction with real-life examples so you could organize your Go repository the easy way. While browsing different groups and communities around the Internet I often spot a question about structuring the repository of application written in Go. I remember how confusing it was back those days when I’ve been switching from PHP and JS development, writing Go code. Mostly because working with PHP and JS I used to use boilerplates, templates or framework init scripts to set things
