Channel
@terminal_stuff
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,498subscribers
+164 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001419089404 |
|---|---|
| Type | Channel |
| Username | @terminal_stuff |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/terminal_stuff |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 09:38 | 3,498 | +39 |
| 15 Sept 2026, 07:21 | 3,459 | +2 |
| 11 Sept 2026, 11:36 | 3,457 | +15 |
| 6 Sept 2026, 07:14 | 3,442 | +2 |
| 1 Sept 2026, 22:28 | 3,440 | +5 |
| 29 Aug 2026, 13:53 | 3,435 | -6 |
| 26 Aug 2026, 17:15 | 3,441 | +25 |
| 23 Aug 2026, 07:35 | 3,416 | +10 |
| 20 Aug 2026, 02:25 | 3,406 | +15 |
| 16 Aug 2026, 19:54 | 3,391 | +12 |
| 13 Aug 2026, 09:06 | 3,379 | +22 |
| 10 Aug 2026, 02:28 | 3,357 | +23 |
| 6 Aug 2026, 22:15 | 3,334 | no change |
| 6 Aug 2026, 22:03 | 3,334 | first reading |
21 posts held, back to 10 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 21 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
184 reactions across 21 posts, in 8 distinct kinds. The most used accounts for 66.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 122 | 66.3% | |
| 👍 | 41 | 22.3% | |
| 👌 | 8 | 4.35% | |
| 🤔 | 6 | 3.26% | |
| 🔥 | 3 | 1.63% | |
| 🤣 | 2 | 1.09% | |
| 🐳 | 1 | 0.543% | |
| 👎 | 1 | 0.543% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 21 of the 21 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 184 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 10 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
یه کتاب آموزشی در مورد Claude توی لینکدین پیدا کردم که سرفصل های خوبی داره و رایگان منتشر شده. اگر دوست داشتید نگاه بندازید بد نیست. لینک پست لینکدین: راهنمای جامع Claude: از صفر تا حرفه ای https://www.linkedin.com/pulse/%D8%B1%D8%A7%D9%87%D9%86%D9%85%D8%A7%DB%8C-%D8%AC%D8%A7%D9%85%D8%B9-claude-%D8%A7%D8%B2-%D8%B5%D9%81%D8%B1-%D8%AA%D8%A7-%D8%AD%D8%B1%D9%81%D9%87-%D8%A7%DB%8C-bahman-shamshirsaz-nbkte لینک مستقیم کت…
❤4👎1
شاید یه چیزی که کمک کنه به این که حس ناکافی بودن از زیاد بودن ابزارهای AI نگیریم اینه که ببینیم بقیه دارن چیکار میکنن. اینجا یه community شکل گرفته که آدم ها ستاپ هاشون رو به هم نشون میدن و به هم امتیاز میدن. دوست داشتید یه سری بزنید. https://app.therundown.ai/community
🤣2
💡 شکاف بهرهوری هوش مصنوعی: چرا برنامهنویسان هنوز ۱۰ برابر سریعتر نشدهاند؟ بیورن روچ (Bjorn Roche) بیش از دو دهه تجربه در صنعت فناوری و برنامهنویسی دارد و در وبلاگ شخصی خود درباره مهندسی و مدیریت مینویسد. خلاصهای از مطلب جدید او را در نوشدارو میخوانید؛ با این هدف که نگاه تازهای در اختیار مدیران و برنامهنویسان حوزهی فناوری قرار دهد. هوش مصنوعی بدون تردید سرعت کدنویسی را افزایش داده است؛ اما برخلاف تصور برخ…
❤9
کتاب معروف Designing Data-Intensive applications بعد از حدود ده سال ویراست دومش رو داده. اگر تا حالا نخوندینش الان بهترین وقت برای خوندنشه. اینجا در موردش بخونید: https://medium.com/javarevisited/i-read-designing-data-intensive-applications-2nd-edition-and-its-awesome-417103df5aab من خودم یه فصلهایی ازشو خوندم و خیلی دوستش داشتم.
👍8❤3
هر کدوم از اصطلاحات در htop به چه معنی هستند؟ هدفش لزوما htop نیست، کلی چیز در مورد کرنل یاد میگیرید. https://peteris.rocks/blog/htop/
❤7👍2
اگه دوست دارید مختصر و مفید در مورد reflog در git بدونید این صفحه رو ببینید. به طور خلاصه reflog مال وقتیه که روز بدی داریم. :))) دنبال کامیت هایی هستیم که در هیچ برنچی نیستن و اصطلاحا گم شدن و منتظرن GC بیاد و پاکشون کنه. https://wizardzines.com/comics/the-reflog/
👍3❤1
هرچیزی که به عنوان برنامه نویس باید از حافظهی سیستم بدونید: https://people.freebsd.org/~lstewart/articles/cpumemory.pdf
👍4
به عنوان یک Engineering Manager چطور وقت و انرژی خودمون رو بودجه بندی کنیم؟ این مطلب رو من خیلی دوستش داشتم چون می اومد با مثال و توضیح میگفت که اگر اینجا اینقدر وقت بگذاریم نتیجه چی میشه و خیلی کمک میکرد به درک اتفاقاتی که در لایه مدیریت میفته و تاثیرش روی تیم. https://www.manager.dev/newsletter/the-engineering-manager-s-attention-budget
❤5👍1
یه موقعیت شغلی توی بلاگ byte byte go دیدم که خیلی جالب بود. شاید یه دید خوبی به شما هم بده که دنیای برنامه نویسی داره به کدوم سمت میره. موقعیت شغلیش آموزش 𝐖𝐫𝐢𝐭𝐞 𝐏𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐆𝐫𝐚𝐝𝐞 𝐂𝐨𝐝𝐞 𝐰𝐢𝐭𝐡 𝐀𝐈 بود. و توانایی که لازمه داشته باشی. با ایجنت ها بلد باشی کار کنی، نحوه کارشون رو بشناسی. برای کدی که نوشته میشه هم بلد باشی با سرعت بالا ریویو کنی و باگ و مشکلات امنیتیشون رو بشناسی تا ai slop مرج نکنی. https://blog.bytebyteg…
👍13🐳1🤔1
در این باره من یکسری کتاب ورق زدم، یکیش که خیلی دوست داشتم کتاب AI engineering از Orielly بود. آخر ۲۰۲۴ منتشر شده بنابراین تمرکزش روی Agent ها شاید زیاد نباشه ولی مفاهیم پایه رو بدون ریاضی و بدون کد، در حد مفاهیم کاربردی آموزش میده. در واقع همون طور که اسمش میگه بیشتر جنبه مهندسی داره و به دل من نشست. صفحه معرفی کتاب: https://www.amazon.co.uk/dp/1098166302 وبسایت نویسنده: https://huyenchip.com/ ریپوی گیتهاب یک نف…
❤6
یه کتاب از یکی از نویسندگان Designing data intensive applications اسمش که خیلی خلاقانه هم هست The missing README ئه، و سعی میکنه نکات عملی در حوزه کار نرمافزار رو بگه که جای دیگه در دانشگاه و غیره بهش پرداخته نمیشه. فصل های متنوعی داره و چیزهای جالبی گفته، نقدش رو اینجا بخونید: https://nurkiewicz.com/2021/10/the-missing-readme-book-review.html
❤12
Linux file permissions are more than just rwx. Learn about the special permisions. https://linuxhandbook.com/suid-sgid-sticky-bit/
❤2
Showing the 12 most recent of 21 posts we hold for @terminal_stuff. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 21 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 25 September 2026 — this entry's latest reading, not the date you are reading this.
“نوشتههای ترمینالی” (@terminal_stuff), 3,498 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/terminal_stuff.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.