Rust’s guiding principle Link to heading I’ve been going through a fantastic book Start with Why by Simon Sinek, and I couldn’t shake the feeling that it reminded me of something. Then I recalled the talk Inventing on principle by Bret Victor. The main point of the talk is that, as a technologist, you can find your guiding principle.| Posts on FlakM blog
Automate the unispiring tasks Link to heading Some tasks do not spark joy. They are repetitive, tedious, and time-consuming. But they need to be done 💀 A prime example of such a task is changing my markdown notes describing a project to jira entries. I like the process of planning the tasks, discussing them with the team, and iterating on the plan. But with the most profound hatred, I don’t like the process of creating the jira tickets. The UI is junky, the process is slow, and the whole...| Posts on FlakM blog
Writing a CV, a wrong way Link to heading I’ve historically used Google Docs for my CV. It’s a great tool, but I’ve had some issues with it for my use case: Styling was never consistent, and changing styles was difficult Since I’m not a native English speaker and I’m a dyslexic, I had to keep going between sites like Grammarly and docs - which messed with the formatting (and I refuse to have it installed as a browser extension) I’ve spent sooo fucking much time perfecting nvim con...| Posts on FlakM blog
Setting up tailscale Link to heading One sad thing is that the host currently exposes SSH over the Internet. There is also a risk of accidentally exposing another service. To mitigate this risk, we can use modern VPNs and add additional firewalls on the Hetzner side. To avoid the hassle of managing my keys, I’ll be using a generous tailscale free tier. To enable tailscale, we’ll have to add one line in our configuration:| Posts on FlakM blog
I’m going through the fantastic book “Systems Performance” by Brendan Gregg. And I find it very useful to test the tools themselves and see how they work. So, I decided to write articles about the tools and techniques Brendan Gregg describes in his book. I will prepare a sample rust program to generate specific load on the system, and we will use the tools to analyze the system’s performance. We will focus on the tools available on Linux systems to examine each domain.| Posts on FlakM blog
Looking for stuff in code is an essential skill in daily tasks. It lets me keep a laser focus on the problem at hand. Examples of questions I find myself asking over and over again: Does this repository contain this variable? What was the context of changing this variable name? Who is the best person to ask questions about this project? What are all the versions of libc on my system? Here are my tips that make this process far more enjoyable.| Posts on FlakM blog
About the infrastructure Link to heading I’ll provision the environment using Hetzner and Cloudflare. The process could be better but should be simple to maintain and follow. Contents: Provisioning all the things Link to heading To host the code, I’ll need two things:| Posts on FlakM blog
Let’s expose the flake! Link to heading In a previous post, we built a simplistic but blazing-fast HTTP server that returns a hello world HTML page. It produces an elf binary that we can run. It’s where nixos starts. We’ll have to expose this piece of code as a nixos module. A nixos module is just a function that takes inputs and returns additional output evaluated when the whole system is built [^1] That sounds cool, but it’s pretty challenging to grasp without knowing how to use it ...| Posts on FlakM blog
Building a personal tech blog Link to heading Building a personal blog can be daunting, especially when choosing the right solution that will get out of the way. Therefore, I’d like to have a static site generator split the site and add ActivityPub integration to interact with it over time. I’ve also decided on self-hosting and using open protocols, especially after last year showed that building on top of free stuff is only sustainable in the short run. Not when the money stops being free.| Posts on FlakM blog
Short research about making decision to use rust in medium web development shop.| Posts on FlakM blog
List of interview questions along with minimal answers. A good question should: Check ability to think outside the box Check deep understanding of key concepts Invite discussion Check ability to communicate tricky parts of the technology Check formal knowledge of the domain| Posts on FlakM blog
How to understand and then profile heap memory usage in rust application. With the company with old friends: pmap, strace and heaptrack| Posts on FlakM blog
Uczę się obsługiwać czujnik wilgoci i temperatury DHT11 z użyciem rust i prezentuję wyników na ekranie lcd używając biblioteki zbudowanej w poprzednim wpisie| Posts on FlakM blog
Uczę się podłączać i z sukcesem wyświetlić napis na wyświetlaczu LCD 2x16 znaków opartym na kontrolerze HD44780 z rustem.| Posts on FlakM blog
I share the story of a frustrating debugging journey with a Rust application that was migrated to Kubernetes. Everything seemed fine until a suspected memory leak caused our application to scale uncontrollably. I dove deep into tracing memory usage with eBPF, heaptrack, and jemalloc profiling tools. The real twist came when I discovered that the memory leak was a phantom menace - a misinterpretation of Kubernetes memory metrics rather than a genuine issue. This post details the steps I took, ...| FlakM blog