I keep things running, also love Free/Libre and Open Source Software, developer in my spare time and @nixos_org/@nixpkg contributor.

Earth
Joined July 2021
Bryan Albuquerque retweeted
Cons of being a software engineer no one really talks about 👇 Everyone sees the salaries, WFH perks, and fancy titles. Here’s the other side: • Your learning never ends If you stop learning for even 6–12 months, you start falling behind. Tech doesn’t wait. • Mental fatigue is real Staring at screens, debugging for hours, context switching—your brain gets tired before your body. • You’re judged by output, not effort 10 hours of hard thinking can look like “nothing” if the feature didn’t ship. • Imposter syndrome never fully goes away New stack, new company, smarter peers → constant self-doubt. • Deadlines don’t care about bugs Management promises dates. Engineers deal with reality. • Work-life balance depends on the team, not the role One bad manager can ruin a “dream job”. • Rejections hit differently You can be good and still fail interviews because of luck, timing, or niche questions. • Side projects feel mandatory To grow or switch jobs, your free time often becomes “resume time”. • AI pressure is increasing You’re expected to be faster, smarter, and more productive—constantly. • Your worth can feel tied to your skills When code breaks, confidence breaks with it. Still a great career. Just not the “easy money” path social media sells. If you’re choosing this field—choose it with eyes open.
92
133
23
1,372
109,614
| ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| | Don't Push To Production On Friday | |_________________| \ (•◡•) / \ / —— | | |_ |_
110
1,101
148
5,498
496,186
| ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| | Don't Push To Production On Friday | |_________________| \ (•◡•) / \ / —— | | |_ |_
138
2,017
214
9,434
412,516
Bryan Albuquerque retweeted
Every developer's dilemma: wanting to fix all the bugs but also wanting to go home at a civilized time. The struggle between responsibility and sanity continues.
1
23
1
159
20,230
Bryan Albuquerque retweeted
Why are we so slow?
4
275
14
1,770
126,571
Bryan Albuquerque retweeted
I'm moving stuff around and I forget how heavy books are! I have a lot of books and what you see here is probably just ⅓ of them. "So, Gustavo... if you like to read so much, why don't you write a book instead of recording lectures?" Look, I'm sure it would be a lot easier to simply write a book. I know this might sound arrogant but I promise it's not! I noticed that if something takes me one day to write, it takes me a about a week to record a lecture on the same topic. Yes, I've thought about writing books before, but there are two main reasons that made me step back. First, most publishers that approach me to write a book don't really want me to write a book because they think my content is good. They are really after my followers and my students. That's why we see so many "influencers" writing mediocre books; publishers want their followers. PacktPub and Manning are champions on that; NoStarch is not that bad. And I get it, some people do it for the "look mom, I published a book!", but I'm too old for that and the whole prestige & ego thing does not get my blood pumping. The second reason is because it doesn't matter what most people say, looking back at my personal learning path... it didn't matter how much I read about a topic, the *first* time a concept clicked with me was usually from a live lecture, a simple conversation with a friend, or from a video lecture. There are some very (very!) well-written books that manage to break that curse, but the truth is that complex ideas rarely clicked first time with me just from reading about them. It was always from someone moving their hands furiously while they are explaining something, or from a well-timed finger pointing to a variable on a formula, or by simply changing the tone of voice to emphasize something important at the right time. Animations are also very good at that, and more modern online resources like videos and blogs use them really well. And the reason I buy so many books is because they worked great *after* I overcame that first brick wall that made the topic less intimidating. Still, most of my initial "aha!" moments didn't come from books and I usually buy a book only after I had a super enlightening lecture about a topic. That's it! That's why I don't think I'll write books and why I prefer to teach stuff showing my face. Who knows, maybe I'm someone's first *click*.
31
19
3
378
41,937
what, and i cannot stress this enough, the fuck
193
480
308
4,908
589,059
Bryan Albuquerque retweeted
When the code you've written runs perfectly on the first try, it's not a miracle. It means the Universe is playing a prank on you and the real bug is hiding somewhere, plotting its grand entrance.
7
54
3
425
35,832
Bryan Albuquerque retweeted
Nothing screams job security like a codebase that only you can understand
7
46
3
469
48,197
Bryan Albuquerque retweeted
#SySadmin Just drafted an online doc about #DragonFlyBSD and I'm looking for feedback. Anyone interested in reviewing it? Please PM me.
3
6
12
911
Bryan Albuquerque retweeted
k8s-image-swapper is a mutating webhook for Kubernetes, downloading images into your own registry and pointing the images to that new location It is an alternative to a docker pull-through proxy ➤ github.com/estahn/k8s-image-…
7
57
6,347
10
91
5
1,340
52,658
Bryan Albuquerque retweeted
12
507
19
4,574
128,581
4
61
742
36,165
Bryan Albuquerque retweeted
We all owe Markus a lot of love for use-the-index-luke.com ♥️🙂
12
142
17,504
Bryan Albuquerque retweeted
Introduction guide to Linux kernel internals and modules development (updated to 5.x kernels) "The Linux Kernel Module Programming Guide" sysprog21.github.io/lkmpg/ #Linux #kernel
2
131
3
497
25,857
Bryan Albuquerque retweeted
A nice read on space efficiency of B-Trees and LSM-Trees > Compared with B+-tree, LSM-tree has a higher storage space usage efficiency, which can be explained as follows: One LSM-tree consists of multiple immutable SSTable files, each one contains a number of blocks (typical block size is 4 KB). Being immutable, all the blocks can be 100% full (i.e., completely filled with user data). > As a result, each B+-tree page (regardless of compressed or uncompressed) must entirely occupy one or multiple 4  KB LBA blocks on the storage device. When B+-tree applies page compression, the 4KB-alignment constraint could incur noticeable storage space waste. This can be further illustrated in Fig. 3: Assume one 16 KB B+-tree page is compressed to 5 KB, the compressed page must occupy two LBA blocks (i.e., 8 KB) on the storage device, wasting 3 KB storage space. Therefore, due to the CPU overhead and storage space waste caused by the 4 KB-alignment constraint, B+-tree page compression is not widely used in production environment. Meanwhile, under workloads with random writes, B+-tree pages tend to be only 50%∼80% full [3]. Hence, B+-tree typically has a low storage space usage efficiency. usenix.org/publications/logi…
One of the hottest topics in the MySQL world. for more than a decade, has been around space efficiency. RocksDB was FB/Meta’s solution to the problem. TiDB leverages RocksDB too. Nobody talks about space efficiency in the Postgres space. The data sets are smaller in practice? Recommending FS compression doesn’t count. MySQL can do that too.
4
58
371
38,297
Bryan Albuquerque retweeted
🚨🚨🚨 URGENTE: Está oficialmente aberta a segunda temporada da Rinha de Backend!!! Só colar no repositório pra ver as regras e dar um RT pra ajudar! ♥️♥️♥️
42
187
48
806
178,582
After months offline, DISCMASTER rises again! 💿 The site, which is not run by the Internet Archive, offers users the ability to perform semantic search of thousands of shareware & compilation CD-ROMs preserved at @internetarchive 👉 blog.archive.org/2024/01/21/…
6
366
9
1,222
76,983