This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
3 measurements spanning 7 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 679–685 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 14:48
680
-4
6 Aug 2026, 16:38
684
no change
6 Aug 2026, 07:20
684
first reading
Engagement
20 posts held, back to 27 February 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 · 30 days
17.3%
avg views ÷ 680 subscribers
Avg views / post
118
4 posts measured
Reaction rate
1.91%
reactions ÷ views · ER floor
Posts in window
4
of 20 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 5 August 2026
Posts held
20 (27 February 2026 – 5 August 2026)
Views total
471
Reactions total
9
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Aug 2026, 16:38 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.
Reaction mix
34 reactions across 14 posts, in 4 distinct kinds. The most used accounts for 67.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
23
67.6%
👍
8
23.5%
👏
2
5.88%
🔥
1
2.94%
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 16 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 34reactions 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 27 February 2026 to 5 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.
Software Architecture is frozen LANGUAGE.
The biggest lie in software: We can rename it later.
YES, You can rename a class in minutes. But you cannot rename a concept that's been frozen into:
- Four services
- Three databases
- Two years of API contracts
- The minds of four different teams
The gap between what a word means to different people is what kills software.
Word => Thinking => Model => Architecture => Cod…
🍀👓اپیزود جدید پادکست نگاه دوم بر روی اسپاتیفای منتشر شد.
فصل زبان الگوها - اپیزود 2: از خانههای کاشان تا کتاب GoF
اپیزود اول را با کریستوفر الکساندر شروع کردیم؛ معمار و فیلسوفی که در سفر به ایران، توی حیاطهای مرکزی خانههای کاشان چیزی را دید که تا قبل از آن در هیچ کتاب معماری ننوشته بودند.
او اسمش را گذاشت: نظم زنده. و الگو را نه یک راهحل آماده، که زبانی زنده برای خلق فضاهای انسانی تعریف کرد.
حالا در اپیزود دوم…
ارائه روحالله دلپاک در ششمین رویداد حضوری نقطه
جمعه این هفته در تهران، در ششمین رویداد نقطه میزبان روحالله دلپاک خواهیم بود.
«بیگدار به آب نزنید؛ به AI هم همینطور!»
ساخت یک نمونه اولیه مبتنی بر LLM کار سختی نیست؛ اما وقتی همان اپلیکیشن قرار است وارد محیط عملیاتی شود، چالشهای واقعی تازه آغاز میشوند.
کنترل هزینهها، مدیریت مصرف، امنیت، پایداری سرویس، مسیریابی هوشمند درخواستها، مدیریت نرخ درخواستها (Rate Li…
⬤ بعد از مدتها، «نقطه» دوباره برگزار میشود.
این بار با یک سؤال مهم:
اگر امروز دوباره قرار بود مسیرمان را در دنیای نرمافزار شروع کنیم، چه چیزهایی را متفاوت انتخاب میکردیم؟
دنیای مهندسی نرمافزار در حال تغییر پارادایمی بزرگ است. AI کد مینویسد، تست تولید میکند و کنار ما در تصمیمهای فنی قرار گرفته است.
اما سؤال اصلی شاید دیگر این نباشد که: از چه ابزاری استفاده کنیم؟
بلکه:
چه چیزهایی را باید عمیق یاد گرفت؟
چه چ…
چند روز پیش، در مورد Office Hours و جلسات Mock Interview نوشتم و استقبال خیلی عالی از این اتفاق شد. از همهی شما که وقت گذاشتید و apply کردید، صمیمانه سپاسگزارم.
---
📌 یک خبر خوب:
اولین دور جلسات Office Hours برای این آخر هفته برنامهریزی شده و گروه اول، جلسات خودشون رو پیش رو دارن. با بقیهی دوستانی هم که درخواست دادن، بهتدریج و طی هفتههای آینده ارتباط خواهیم گرفت.
---
⚠️ متاسفانه متوجه شدم که برخی از ایمیلهای…
🐒Today I published Part I of my book, Language-Driven Design
Software Architecture is Frozen Language
It took me years to understand what that sentence actually meant.
The more software systems I worked on,the less convinced I became that architecture begins with architecture
It felt like we were always starting the story from chapter two.There had to be something earlier!
It was failing because the language unde…
Office Hours with Masoud Bahrami⭐🌱
جالبه، گاهی بین اونی که واقعا هستیم و اونی که توی مصاحبه دیده میشیم، یه فاصلهی عجیب وجود داره.
بارها پیش اومده بعد از یه مصاحبه، آدم با خودش فکر میکنه:
کاش این سؤال رو یه جور دیگه جواب میدادم.» یا «اصلاً منظور سؤال رو درست نفهمیدم.
در حالی که شاید اگر همون مسئله رو فردای اون روز، سر کار یا کنار همکارات حل میکردی، خیلی بهتر از پسش برمیومدی.
مصاحبه یه مهارته. همونقدر که طراح…
🎙 اپیزود جدید پادکست «نگاه دوم» منتشر شد.
تا حالا برایتان پیش آمده آنقدر غرق یک کار شوید که اصلاً متوجه گذر زمان نشوید؟
همان لحظههایی که انگار همهچیز سر جای خودش قرار گرفته، تمرکزتان عمیقتر از همیشه است و کار کردن نه خستهکننده است و نه اجباری؛ بلکه خودش تبدیل به پاداش میشود.
روانشناس مشهور میهالی چیکسنتمیهایی این وضعیت را Flow یا جریان نامید؛ مفهومی که سالهاست روی یادگیری، خلاقیت، بهرهوری و حتی کیفیت زن…
Discipline Changes Everything | Best Motivational Speech | Novak Djokovic
یکی از گپوگفتهای کوتاهی که بسیار ارزشمند و تاثیر گذاره بوده و لذت بردم از شنیدنش
https://www.youtube.com/watch?v=Gj8TdHnIfuk
ورکشاپ عملی Enterprise Integration Patterns🟡
هرچه بیشتر در پروژههای واقعی کار کردهام، بیشتر به این نتیجه رسیدهام که بخش سخت طراحی سیستم، نوشتن کد نیست؛ طراحی ارتباط بین سیستمهاست.
اوایل بیشتر سوالها درباره کلاسها، Design Patternها یا ساختار کد است. اما از یک جایی به بعد، جنس سؤالها عوض میشود:
این پیام را چه کسی باید منتشر کند؟
اینجا Event بهتر است یا Command؟
اگر وسط مسیر یکی از سرویسها از کار بیفتد چه می…
ورکشاپ عملی Clean Code Mastery
اگر قرار باشد کیفیت یک نرمافزار را فقط با یک معیار بسنجیم، احتمالا آن معیار تعداد قابلیتها، سرعت توسعه یا حتی تعداد باگها نخواهد بود.
سؤال مهمتر این است:
اضافه کردن تغییر بعدی چقدر سخت خواهد بود؟
چون تقریباً تمام تصمیمهای فنی ما، دیر یا زود خودشان را در هزینه تغییر نشان میدهند.
بیشتر سیستمها روز اول مشکل خاصی ندارند. کدها نسبتاً تمیز هستند، ساختار پروژه قابل فهم است و توسعه با …
آکادمی مسعود بهرامی🌏⭐
بیشتر توسعهدهندگان در سالهای اول مسیر حرفهای خود یک سؤال مشترک دارند:
چطور میتوانم معمار نرمافزار شوم؟
پاسخ رایج معمولا فهرستی از تکنولوژیهاست. مایکروسرویسها، کلود، پیامرسانها، الگوهای طراحی، و دهها مفهوم دیگر.
اما خب در عمل، مسئله جای دیگری است.
بسیاری از سیستمهایی که نگهداری آنها دشوار شده، به خاطر انتخاب اشتباه تکنولوژی شکست نخوردهاند. مشکل از جایی شروع شده که تیم، سیستم را فقط…
❤3
Showing the 12 most recent of 20 posts we hold for @DomainDrivenDesign_ir. 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
Citation-graph rank — 745,022 of 1,345,403entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Cite this entry
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.
“کانال مکتبخانه DDD” (@DomainDrivenDesign_ir), 680 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/DomainDrivenDesign_ir.
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.
