Hussein Nasser engagement report
@hnasr - 89K followers on X
Measured over 13 original posts from a 30-day window, last computed on August 29, 2026.
Engagement
A typical post picks up 126 interactions against 89K followers, an engagement rate of 0.141%. Measured over 13 original posts, its engagement rate beats 58% of 3,882 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 9.8K times each, and 1.28% of those impressions turn into an interaction. That is about 11.0% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.7 post a day over the last 30 days, though only 43% of days saw any activity at all. Most posts go out around 14:00 UTC, and Monday is the busiest day of the week. Of the 13 posts sampled, 38% carry an image or video, 38% are part of a thread and 23% link out. The account's strongest tracked post pulled 1.2K interactions, about 9.6x its own typical post.
Measured over 13 original posts from a 30-day window, last computed on August 29, 2026.
Compared with accounts its own size
Hussein Nasser's engagement rate beats 58% of the tracked X accounts closest to it in follower count (3,882 accounts, accounts of similar size (decile 4 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.
On engagement per impression rather than per follower it beats 52% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.
Where this sits in the catalog
At 0.141%, Hussein Nasser sits above the 50th percentile of the 37,582 accounts in this comparison. That places it in the above the median band, which runs 0.081% to 0.439%.
Show the percentile table
| Percentile | Engagement rate |
|---|---|
| 10th percentile | 0.002% |
| 25th percentile | 0.012% |
| 50th percentile | 0.081% |
| 75th percentile | 0.439% |
| 90th percentile | 2.10% |
| 99th percentile | 158.1% |
This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built
Posting timing
This account posts most often around 14:00 UTC, and Monday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.
Show engagement by hour posted, utc as a table
| Hour (UTC) | Vs author median | Posts |
|---|---|---|
| 00:00 UTC | -1% | 52K |
| 01:00 UTC | -2% | 53K |
| 02:00 UTC | -3% | 51K |
| 03:00 UTC | -4% | 55K |
| 04:00 UTC | -6% | 44K |
| 05:00 UTC | -4% | 43K |
| 06:00 UTC | -4% | 50K |
| 07:00 UTC | -5% | 54K |
| 08:00 UTC | -4% | 62K |
| 09:00 UTC | -3% | 72K |
| 10:00 UTC | -2% | 74K |
| 11:00 UTC | -3% | 81K |
| 12:00 UTC | -2% | 89K |
| 13:00 UTC | -2% | 98K |
| 14:00 UTC | -4% | 101K |
| 15:00 UTC | -2% | 104K |
| 16:00 UTC | -3% | 102K |
| 17:00 UTC | -3% | 94K |
| 18:00 UTC | -1% | 88K |
| 19:00 UTC | -2% | 83K |
| 20:00 UTC | -1% | 77K |
| 21:00 UTC | -1% | 68K |
| 22:00 UTC | -2% | 59K |
| 23:00 UTC | -2% | 53K |
Show engagement by day of week as a table
| Day | Vs author median | Posts |
|---|---|---|
| Sunday | +5% | 237K |
| Monday | 0% | 300K |
| Tuesday | -3% | 299K |
| Wednesday | -1% | 256K |
| Thursday | -1% | 249K |
| Friday | -3% | 258K |
| Saturday | +3% | 232K |
Best tweets
- Aug 5, 20269.6x their median
In the coming few years, most engineers will heavily rely on AI to build software. Loops will produce and review code, while engineers will be out of the loop, figuratively and literally. The final product, which is supposed to be used by humans, is unrecognizable by the engineers who built it. Bugs and performance issues will arise, and the engineers will go back to the loops to fix them. The loops will fix the bugs but produce more others. Eventually, we will reach a stage where we can’t possibly know what is wrong with the system, because the agent built its own framework, libraries and abstraction that only it understands. The product will get into a state where no one can read or understand the code and only the loops can fix them. Loops need tokens, and engineers will have no choice but to shovel them like coal into the Titanic’s boilers. Very few engineers will be able to understand and troubleshoot systems. Those rare engineers who kept their skills sharp will be in high demand when we reach that state. By all means use AI but not to an extent it dulls your critical thinking.
- Apr 15, 20267.6x their median
I wrote a new book that has been in the works for years. It is called Root Cause, and it is for those who enjoy the art of backend engineering. Early in my career, 20 years ago, I built backend and database applications without fully grasping their inner mechanics. Performance issues, race conditions, bugs, and even data corruption often left me lost. Since that day, I resolved to truly understand how systems work. From networking protocols and intermediary proxies to backend services and various database engines. I made it a habit to follow every request on its journey through the dark alleys of the network, down to the bowels of the database engine, meanwhile interacting with various kernel data structures in the process at every hop, and back. I became obsessed with understanding what happens behind the scenes in software. Not just what breaks, and how but also why and what was the source of the bleed. Root Cause is a collection of the most interesting bugs I encountered, ranging from performance bottlenecks and non-deterministic crashes to subtle data inconsistencies and incorrect results. This book is for anyone curious about how production backend systems really behave under pressure, and how to debug them when they don’t. Even when you don’t have access to the source code. Root cause consists of 15 chapters, each is a story about a backend bug, with investigation, diagrams, a section of a fundamental concept until the root cause is revealed. Grab your copy here paperback or kindle ebook on amazon https://t.co/AgYMX4sWTQ
- Jun 25, 20266.5x their median
In the end, AI will produce more bloated products for us to troubleshoot and fix. If you are a good software troubleshooter who understands the fundamentals. you will be on high demand. And Your skillsets are deadly.
- Jul 1, 20264.2x their median
When I created this course I didn’t know it will grow and reach over 60k engineers. I honestly just shared my experience, lessons and patterns that I discovered in the backend engineering space. To this day (years later) I get emails of people who aced interviews and promotions, got more confidant building software and started polishing their foundation. They speak with grounded knowledge instead of throwing out abstract and confusing terminologies. If you have specific knowledge, share it to the World. You never know who may resonate with it.
- Apr 26, 20263.6x their median
When this news broke I really wanted to understand how the linux scheduler work. So I started to research. What I gathered so far: (of course I might be missing something) Unlike user code, the Linux kernel code isn’t usually preemptable. That is when a system call is executed or a page fault is triggered the kernel runs to completion hogging the cpu core it runs on. The current Linux 7 tip experimenting a different preemption model for kernel code, so other more critical tasks can be scheduled. With this default mode, Postgres experienced 50% dropped in performance in one test suite 96 cores, with 100GB shared buffers pool. The theory from the thread discussion is that the large buffer pool 100 GB with the default 4kb kernel vm page size, caused significant number of page faults. Page faults gets triggered to allocate physical memory on first access or on swap (I have a video detailing this). Page fault runs kernel code to do the allocation of the physical memory and update the page table data structure for the process. If page faults are being preempted, it keeps the user process code in spin lock waiting for access. Indeed Andreas, the postgres maintainer, was able to prove that even with stable Linux you could see the contention obtaining memory from shared buffers, its just not as obvious with 7.0 where kernel preemption is enabled Using huge pages significantly reduces page faults, improving the performance. My Page Faults The Backend Engineering Show https://t.co/QtcIL4nsZi Phoronix article https://t.co/hXMzz0KOi0
- Aug 26, 20262.8x their median
You wouldn’t know what a good software is until you've seen a bad one. Bugs and slowness must be experienced in software to appreciate quality efficient software.
- Jun 15, 20262.4x their median
https://t.co/rsO62YH2bF https://t.co/D4w6hl4FgW
- Jun 21, 20262.2x their median
Root Cause will make you look and think of system internals from a different lens. Grab your copy Amazon: https://t.co/flopo4GN73 b&n https://t.co/gz4usDugsn https://t.co/3DV2cXXy7M
- Jul 10, 20262.1x their median
Worker pools and connection pools can be mixed and matched into some interesting backend design patterns. NGINX has a process worker pool, each worker has a dedicated upstream connection pool, Making sharing challenging and increases overhead of connection establishments but reduces contention. HAProxy uses a threaded worker pool allowing sharing connections between threads with an access to local thread cache, can still run into contention when accessing the shared pool. I tell a story of how I discovered this concept in chapter 8 in my book, Root Cause, stories and lessons of two decades of backend engineering bugs, and expand on this further on Appendix A.
- Aug 10, 20262.1x their median
Routing is one of the most critical concepts in networking, yet it can be tricky to understand. I break down the concept of routing from the very basics to the most advanced routing tables that power the Internet. https://t.co/NhjjCUBtNh
Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.
Buy or sell X accounts - escrow-protected
PlayerSells is an escrow marketplace for X accounts. Every deal is protected, with no middleman risk.
Reading these numbers
A typical post picks up 126 interactions against 89K followers, an engagement rate of 0.141%. Measured over 13 original posts, its engagement rate beats 58% of 3,882 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 9.8K times each, and 1.28% of those impressions turn into an interaction. That is about 11.0% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.7 post a day over the last 30 days, though only 43% of days saw any activity at all. Most posts go out around 14:00 UTC, and Monday is the busiest day of the week. Of the 13 posts sampled, 38% carry an image or video, 38% are part of a thread and 23% link out. The account's strongest tracked post pulled 1.2K interactions, about 9.6x its own typical post.
- What is Hussein Nasser's engagement rate on X?
- Hussein Nasser (@hnasr) has an engagement rate of 0.141%, based on the median interactions across 13 original posts from the last 30 days against 89,455 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
- Is that a good engagement rate?
- At 0.141%, Hussein Nasser sits above the 50th percentile of the 37,582 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
- Does @hnasr have real engagement?
- Its engagement rate beats 58% of the tracked X accounts closest to it in follower count (3,882 accounts), which puts it in the middle of its size range group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
- When does @hnasr post?
- Most posts go out around 14:00 UTC, and Monday is its busiest day, at roughly 0.7 posts per day across the measured window.