Welcome to Lorbic! By accessing and using this website, you agree to comply with and be bound by the following terms and conditions of use. If you do not agree to these terms, please do not use this website.
We do not collect, use or sell your information. You may share your email address and name by contacting the author and while commenting on a blog post. Your email address and name will only be used for replying to you or idetification on the comment system. Other than that we do not use it.
In future there might be newsletters and account registration features. Then we will update this document and add new terms and privacy policies.
The content on this blog is provided for general information purposes only. The author and the website make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability, or availability of the information, products, services, or related graphics contained on the website for any purpose.
The copyright for the content on this website is owned by the author and Lorbic. All rights reserved.
Lorbic reserves the right to change these terms of service at any time. Changes will be effective immediately upon posting to the website. Your continued use of the website constitutes acceptance of the modified terms.
If you have any questions or concerns regarding these terms, please contact us at [email protected].
Thank you for visiting Lorbic!
Bitmasking is one of those computer science tricks that feels like wizardry, until you realize it’s just some clever shifting and binary math. This blog explores the idea, shows how we use it in Go, and why it's surprisingly useful when working with databases like Couchbase.
In Go, method receivers determine whether a method acts on a copy of a value or a reference to it. This choice isn’t just about performance—it affects correctness and behavior, especially when dealing with synchronization primitives (mutex, wait group, etc), slices, and embedded types.
When it comes to writing clean, maintainable code, there are a few fundamental rules that can help improve the overall structure and quality of your codebase. As engineers, our goal should be to keep things simple, clear, and scalable. With this in mind, here are some guidelines which prioritize code readability, functional clarity, and the overall maintainability of a project. These guidelines are based on principles from clean code, SOLID, and functional programming while emphasizing simplicity over unnecessary complexity.
SOLID and functional programming principles explained and implemented in Go
