Where our thread pool server meets its match, and I discover that sometimes the best way to handle thousands of connections is to pretend threads don’t exist. (Source: https://berb.github.io/diploma-thesis/community/042_serverarch.html) The Tantalizing Promise Fresh from the victory of my thread pool implementation, I felt invincible. My server could handle hundreds of concurrent connections with predictable resource usage. Thread creation was under control, context switching was manageable, and memory consumption was reasonable. ...

Where our simple single-threaded server meets the harsh reality of concurrent clients – and how I learned to think in threads. Source: https://commons.wikimedia.org/ One Server, But More Than One Clients Last week’s victory almost felt complete as my handshake server seemed to work flawlessly – until concurrency kicks in. Unless there are only single server and single client (too strong assumption!), we always have to take multiple clients into consideration. ...

The tale of how I went from basic Rust knowledge to implementing a custom 3-way handshake protocol – and what I learned about both networking and Rust along the way. Source: https://commons.wikimedia.org/ The Beginning: A Simple Goal Everything began suddenly and whimsically yesterday – just like many of my curiosity-seeking journeys. Disclaimer: While the story I introduce in this post reflects the real development experience, I’ve intentionally dramatized certain moments to deliver the developer journey in more engaging ways. The actual process was indeed smoother than portrayed – this small project falls well within what the community calls “easy Rust” territory. ...

From architectural insights to working implementation – the complete journey from frustration to functional publishing platform (source: https://blog.viktoradam.net/2019/03/28/netlify-hugo/) The Final Implementation After understanding the architectural foundations that make static site generators so powerful, it was time to build the actual system. This final episode documents the complete process – from installing Hugo to deploying on Netlify – with practical insights from actually building and launching my new technical blog. ...

Understanding why some tools fight you while others amplify your thinking (source: https://www.cosmicjs.com/blog/static-site-generators-explained-in-5-minutes) The Rabbit Hole Begins After documenting the frustrations and systematic failures of my copy-paste workflow, I found myself staring at a deeper puzzle. I understood what was breaking – LaTeX equations becoming image files, code blocks losing syntax highlighting, semantic structure collapsing into visual formatting. But I had no idea why these specific things kept breaking in such predictable ways. ...

A personal journey from platform acceptance to technical rebellion (source: https://www.netlify.com/blog/2020/04/14/what-is-a-static-site-generator-and-3-ways-to-find-the-best-one/) The Unquestioned Years A decade ago, I lived in blissful ignorance of better alternatives. Windows was my operating system, Microsoft Office was my document suite, and whatever blog platform provided was my publishing tool. I wrote movie reviews, game critiques, and random thoughts about life – mostly text with occasional images. The web editors worked fine because my needs were simple. ...

When we need population-level insights without the distributional baggage of random effects Picture this: We’ve just finished implementing that elegant mixed effects model from last week’s deep dive, and the hospital executives are thrilled with our patient length-of-stay predictions. But then the epidemiologist on our team asks a different question: “What’s the average effect of this new treatment protocol across all our hospitals?” Our mixed effects model gives us subject-specific predictions – how much longer will this particular patient stay at this specific hospital? The policy question requires population-average inference – if we implement this protocol system-wide, what’s the expected change in average length of stay across the entire health system? ...

When your neural network treats every hospital the same, but your statistician intuition screams that they shouldn’t be Picture this: You’re building a model to predict patient length of stay across 200 hospitals. Your gradient boosting model achieves impressive metrics on your test set, but something feels off. Hospital A consistently shows longer stays than predicted, while Hospital B always runs shorter. Your model treats every hospital identically, missing systematic patterns that could unlock better predictions and deeper insights. ...

A deeper look beyond the textbook distinction that’s been confusing practitioners for decades The Problem We All Face Picture this: You’re sitting in a committee meeting, and someone suggests using “factor analysis to reduce dimensions” while another colleague insists “PCA will identify the underlying factors.” Both sound reasonable. Both seem to accomplish similar goals. Yet something feels… off. If you’ve found yourself nodding along while internally questioning whether these methods are really as different as your statistics textbook claimed, you’re not alone. The standard explanation—“FA finds latent factors, PCA reduces dimensions”—is technically correct but practically incomplete. It’s like saying “cars move people, planes fly people”—true, but missing the nuanced reality of when and why you’d choose one over the other. Choosing the wrong method can lead to misleading conclusions about underlying mechanisms or inefficient models that fail in production. ...

On operating systems, evolution, and the gradual convergence of computing environments The Return Ten years ago, I attempted to make Linux my daily driver and failed. Not catastrophically – more like learning to ride a bicycle and discovering that while technically possible, the experience required more effort than I was prepared to invest. My motivation wasn’t purely practical; I secretly aspired to be a Unix user because they looked like the hackers and gurus I wanted to become someday. There was an undeniable appeal to the idea of mastering a system that seemed to separate the technically sophisticated from ordinary computer users. ...