Prompt Engineering for LLMs @things_to_know_channel
❤2
Signed Fatemeh

Channel
@things_to_know_channel
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
756subscribers
+44 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002530023864 |
|---|---|
| Type | Channel |
| Username | @things_to_know_channel |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/things_to_know_channel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 06:18 | 756 | +44 |
| 6 Aug 2026, 21:40 | 712 | no change |
| 6 Aug 2026, 18:18 | 712 | first reading |
20 posts held, back to 23 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 1 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (23 July 2026 – 6 August 2026) |
| Views total | 15,993 |
| Reactions total | 143 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 18:18 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
143 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 63.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 91 | 63.6% | |
| 👍 | 22 | 15.4% | |
| 🔥 | 12 | 8.39% | |
| 👌 | 10 | 6.99% | |
| 😍 | 3 | 2.10% | |
| ⚡ | 2 | 1.40% | |
| 👏 | 2 | 1.40% | |
| ❤🔥 | 1 | 0.699% |
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 20 of the 20 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 143reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 23 July 2026 to 6 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.
Prompt Engineering for LLMs @things_to_know_channel
❤2
Signed Fatemeh
📚 معرفی کتاب 📖 Prompt Engineering for LLMs ✍️ John Berryman & Albert Ziegler معماری نرمافزار در عصر هوش مصنوعی بدون تسلط بر نحوه ارتباط با مدلهای زبانی بزرگ ناقص است. این کتاب کاربردی به شما میآموزد چگونه با طراحی دقیق پرامپتها، خروجیهای دقیقتر و قابل اتکایی از هوش مصنوعی دریافت کنید و تعاملات سیستم را بهبود ببخشید. ارزش این اثر در ارائه الگوهای عملی برای حل مسائل واقعی مهندسی است. • اصول طراحی پرامپت • زنج…
❤2🔥1
Signed Fatemeh
اگه دنبال کانالی هستین که : تست نویسی ✍ تمرین برنامه نویسی💻 ویدیو آموزشی 🎥 ویدیو های کوتاه برنامه نویسی 📱 انگیزشی ❤️🔥 کتاب های برنامه نویسی 📚 بزاره کانال ما عضو شوید 👇👇 https://t.me/programmings_world
😍3👍2
Signed Fatemeh
#linux_time 🚀 مگه میشه سیستم رو ریبوت کرد بدون اینکه BIOS بالا بیاد؟ تا حالا شده وقتی سیستم رو ریبوت میکنی، کلافه شی از اینکه باید چند دقیقه منتظر بمونی تا BIOS و UEFI لود بشن و بعدش تازه kernel بالا بیاد؟ راستش یه راه هست که بشه بدون این همه انتظار و بدون اینکه سختافزار کلاً ریست بشه، kernel رو عوض کرد یا آپدیت کرد که بهش میگن kexec. توی یه ریبوت معمولی، kernel یه syscall میفرسته که به سختافزار دستور مید…
❤7👍2⚡1🔥1
Signed Fatemeh
#linux_time 🤔 چرا لینوکس به برنامهها قول میده RAM-ی رو بده که اصلاً وجود نداره؟ تا حالا شده توی گزارشهای سیستم ببینی که مجموع RAM-ی که برنامهها درخواست کردن خیلی بیشتر از مقدار واقعی RAM سیستمته، ولی با این حال درست کار میکنه؟ این اتفاق به خاطر مفهومی به اسم memory overcommit میافته؛ یه استراتژی توی kernel لینوکس که اجازه میده processها بیشتر از RAM موجود، RAM allocate کنن. داستان اینه که وقتی یه process …
❤11👍4🔥2👏1
Signed Fatemeh
#linux_time 🔗 xargs — تبدیل خروجی به ورودی تا حالا شده بخوای خروجی یه دستور رو بدی به یه دستور دیگه، ولی اون دستور ورودی رو از طریق پایپ قبول نکنه؟ دستور xargs دقیقا همین مشکل رو براتون حل میکنه. در ادامه چند تا مثال کاربردی ازش میبینیم: 📌 محدود کردن تعداد آرگومانهای ارسالی به هر دستور $ echo 1 2 3 4 | xargs -n 2 echo 📌 تعریف جایگزین برای جایگذاری ورودی در دستور $ ls *.txt | xargs -I {} rm {} 📌 اجرای م…
❤8👍1👏1🔥1
Signed Fatemeh
#linux_time ⚠️ بهینهسازیای که ممکنه ضرر بزنه تا حالا شده روی سرور یا سیستم شخصیت احساس کنی یه سری اپلیکیشنهای دیتابیس یا برنامههای سنگین، یهو دچار لگهای عجیب و غریب میشن در حالی که CPU و RAM هنوز جای خالی دارن؟ اینجاست که مفهومی به اسم transparent huge pages یا همون THP وارد میشه؛ یه قابلیت توی kernel لینوکس که سعی میکنه مدیریت RAM رو بهینهتر کنه تا سرعت دسترسی به دادهها بره بالا. داستان از این قراره…
❤8👍2👌1🔥1
Signed Fatemeh
practical packet analysis 3rd edition @things_to_know_channel
❤5⚡1
Signed Fatemeh
📚 معرفی کتاب 📖 practical packet analysis 3rd edition ✍️ Chris Sanders دیدن ترافیک شبکه بدون ابزار مناسب مثل خواندن نامه در تاریکی است. کتاب تحلیل عملی پکیجها راهنمای جامع و کاربردی برای درک عمیق پروتکلهای شبکه و عیبیابی با وایرشارک است. این اثر بدون مباحث تئوری اضافه، مستقیماً به سراغ حل مشکلات واقعی شبکه میرود. • تحلیل پروتکلهای لایه شبکه • کشف ناهنجاریها و ترافیک مشکوک • عیبیابی مشکلات عملکردی • کار با وا…
❤7❤🔥1
Signed Fatemeh
#linux_time ⚡ تفاوت Page Cache و Buffer Cache در لینوکس تا حالا شده وقتی داری یه فایل خیلی حجیم رو روی هارد کپی میکنی، تعجب کنی که چرا مصرف RAM سیستم همینطوری میره بالا، در حالی که هیچ برنامه سنگینی باز نکردی؟ اینجاست که داستان page cache vs buffer cache توی لینوکس وسط میاد؛ دو تا مکانیزم داخلی که کارشون اینه نذارن RAM بیکار بمونه و دادههایی رو که احتمالاً قراره دوباره بخونی یا بنویسی، موقتاً اونجا نگه دارن. …
❤7
Signed Fatemeh
#linux_time 📂 راز فایلهای device تا حالا شده به پوشه dev نگاه کنی و از خودت بپرسی لینوکس چطور میفهمه کدوم فایل مربوط به hard driveـه و کدوم مربوط به keyboard یا یه serial port؟ شاید فکر کنی اسم فایل مهمه، ولی در واقع لینوکس از سیستمی به اسم major/minor device numbers استفاده میکنه تا بتونه هر فایل رو به driver درستش وصل کنه. وقتی یه process سعی میکنه یه فایل تو پوشه dev رو باز کنه، kernel به جای اینکه به اس…
❤8
Signed Fatemeh
Operating System Concepts @things_to_know_channel
❤3👌1
Signed Fatemeh
Showing the 12 most recent of 20 posts we hold for @things_to_know_channel. 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.
Citation-graph rank — 225,398 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“TKC” (@things_to_know_channel), 756 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/things_to_know_channel.
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.