Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
Growth
35 measurements spanning 43 days, net -1,105. 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 139,908–141,345 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)
Subscribers
Change
17 Sept 2026, 16:15
140,074
-37
15 Sept 2026, 11:39
140,111
-43
13 Sept 2026, 20:21
140,154
-68
12 Sept 2026, 03:21
140,222
-88
9 Sept 2026, 20:18
140,310
-91
6 Sept 2026, 11:57
140,401
+3
4 Sept 2026, 04:22
140,398
-27
2 Sept 2026, 21:12
140,425
-8
1 Sept 2026, 19:35
140,433
-56
31 Aug 2026, 20:34
140,489
-25
30 Aug 2026, 18:55
140,514
-65
29 Aug 2026, 16:23
140,579
-26
28 Aug 2026, 16:13
140,605
-46
27 Aug 2026, 17:04
140,651
-14
26 Aug 2026, 19:05
140,665
-45
25 Aug 2026, 16:04
140,710
-33
24 Aug 2026, 18:33
140,743
-95
23 Aug 2026, 03:17
140,838
-30
21 Aug 2026, 13:17
140,868
-22
20 Aug 2026, 15:22
140,890
first reading
Engagement
55 posts held, back to 28 June 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 108 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
6.81%
avg views ÷ 140,074 subscribers
Avg views / post
9,540
22 posts measured
Reaction rate
0.149%
reactions ÷ views · ER floor
Posts in window
22
of 55 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. It is computed over the 21 of 22 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 26 September 2026
Posts held
55 (28 June 2026 – 26 September 2026)
Views total
209,923
Reactions total
306
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
26 Sept 2026, 23:39 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.
What this channel posts
Photos
≈927
Videos
≈31
Links
≈1,230
Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
941 reactions across 53 posts, in 7 distinct kinds. The most used accounts for 47.3% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
445
47.3%
👍
239
25.4%
👎
116
12.3%
🔥
57
6.06%
😁
38
4.04%
🗿
27
2.87%
👨💻
19
2.02%
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 54 of the 55 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 955 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 55 most recent posts we hold, published 28 June 2026 to 26 September 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.
Introduction to Solon
A comprehensive tutorial walks through building a REST API with Solon, an independent enterprise Java framework, starting from a basic greeting endpoint and extending it into a task management API backed by H2 and MyBatis-Flex. It covers Solon's architecture, dependency injection, configuration layering, HTTP handling, and testing with solon-test, drawing comparisons to Spring Boot concepts thro…
The strangler fig pattern: modernizing without a big-bang rewrite
A detailed guide to the strangler fig pattern for modernizing legacy systems capability by capability rather than through a big-bang rewrite. It covers how the facade layer routes traffic, the tradeoffs between dual writes and change data capture for data ownership during migration overlap, how to choose which capability to strangle first, why migratio…
Lessons From Four Years of Writing a Weekly Newsletter
A .NET blogger reflects on four years and 210 weekly issues of his newsletter, distilling four lessons: consistency beats brilliance, teaching accelerates learning, fundamentals (modular monoliths, domain-driven business rules, API contracts, idempotency, outbox pattern) outlast frameworks, and audience feedback sharpens thinking. He also shares his bullish stanc…
We first featured Asentum four months ago ahead of its $ASE token launch. This JavaScript-native blockchain opens its Incentivized Testnet and gamified airdrop campaign.
Participants can earn XP by running a validator, using dApps, sending transactions, completing quests, referring friends and more - you can do so on any device 💻
🚨 This is not your typical mindless clicking experience🚨
It's completely free to join…
Hello everyone some of you may not know but now we started to expand to WhatsApp and we are inviting you to join our WhatsApp channel link here 👇👇👇👇👇
WhatsApp Computer Science and Technology
We welcome you all to be part of this family
Dates Are Not Data, They Are Context · Nikhil Gautam
A developer recounts a bug where a billing report showed bills from the wrong day due to a timezone mismatch: the frontend sent plain calendar dates (e.g. '2026-01-01') without timezone context, and the backend converted them directly to JavaScript Date objects while MongoDB stored timestamps in UTC. The core lesson is that a calendar date is not the same as a time…
React 19.3 – React
React 19.3 is now available on npm, stabilizing two previously experimental APIs: View Transitions and Fragment Refs. The new <ViewTransition> component animates elements entering, exiting, moving, or resizing using the browser's View Transition API, with support for custom animations via addTransitionType and integration with Suspense for coordinated loading of fallbacks, images, and fonts. Fragme…
Scaling Down Costs, Not Performance: How We Migrated from Couchbase to PostgreSQL
Trendyol's product content team details a phased, zero-downtime migration of five 'helper bucket' datasets (2.24 billion documents across two clusters) from Couchbase to PostgreSQL to cut infrastructure costs while preserving read performance. The strategy combined dual-writes via Kafka consumers, a custom CDC-based migrator tool for hi…
Bun v1.4.2
Bun v1.4.2 patches two regressions introduced in v1.4.1: a bun build variable name collision that broke Elysia imports with a SyntaxError, and an AsyncLocalStorage memory leak affecting timers and promises created inside store.exit() or nested store.run(). It also fixes a worker_threads 'online' event ordering bug that caused @discordjs/ws to hang, adds CMYK/YCCK JPEG decoding support to Bun.Image, pulls i…
Build with Tailscale using tsnet, APIs, and automated sharing
Tailscale is expanding from a network you configure into a platform you build with and on. The tsnet Go library lets applications embed Tailscale connectivity directly, giving each app its own tailnet identity, MagicDNS name, and automatic TLS certificates without opening ports or managing proxies. A tailscale-rs library is in pre-alpha, promising bindings…
What’s new in Svelte: September 2026
Svelte 5.57 adds new SvelteMap methods (getOrInsert, getOrInsertComputed), a createContext has function, select defaultValue support, and new svelte/server type exports. SvelteKit 3's next release candidate continues iterating with several breaking changes including reworked cross-page form actions, split Vite plugin hooks, defineParams relocation, and route filtering for test fil…
❤9👍2🗿1
Showing the 12 most recent of 55 posts we hold for @computer_science_and_programming. 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.
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.
Mentions
Named by 14 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.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@computer_science_and_programming named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@discordjs named in 2 posts, 23 September 2026 – 24 September 2026
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 13 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
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.
Apna College @aman_dhattarwal · 34,378 Telegram ranks this channel #1 of 51 here — alongside 50 others — read 3 September 2026
🤖 Coding News ⚡️ @CodingNews · 23,118 Telegram ranks this channel #2 of 68 here — alongside 67 others — read 19 September 2026
FrontEnd Development @fedevelopment · 28,752 Telegram ranks this channel #3 of 88 here — alongside 87 others — read 9 September 2026
Telegram Shorts: Best Funny Videos @AI_Agentic_Coding · 25,054 Telegram ranks this channel #4 of 67 here — alongside 66 others — read 14 September 2026
Web Development @webde · 31,910 Telegram ranks this channel #4 of 84 here — alongside 83 others — read 5 September 2026
Codehub @pythonadvisorai · 32,027 Telegram ranks this channel #4 of 71 here — alongside 70 others — read 5 September 2026
Artificial Intelligence @Artificial_intelligence_in · 65,766 Telegram ranks this channel #4 of 90 here — alongside 89 others — read 21 August 2026
Programming & AI Tips 💡 @ProgrammingTip · 46,484 Telegram ranks this channel #5 of 73 here — alongside 72 others — read 27 August 2026
Front End World @front_end_first · 25,950 Telegram ranks this channel #6 of 90 here — alongside 89 others — read 13 September 2026
HCL GUVI @guvigeek · 26,890 Telegram ranks this channel #9 of 49 here — alongside 48 others — read 11 September 2026
Linuxgram 🐧 @linuxgram · 72,668 Telegram ranks this channel #10 of 90 here — alongside 89 others — read 19 August 2026
The Devs @thedevs · 32,129 Telegram ranks this channel #11 of 82 here — alongside 81 others — read 5 September 2026
Learn JavaScript @JavaScript_Trainings · 96,712 Telegram ranks this channel #11 of 68 here — alongside 67 others — read 16 August 2026
TheSanskaarSingh @codeslearningTG · 272,410 Telegram ranks this channel #11 of 84 here — alongside 83 others — read 11 August 2026
Flutter Heroes @flutterDev · 22,496 Telegram ranks this channel #12 of 87 here — alongside 86 others — read 20 September 2026
Learn React and NextJs @React_Training · 62,922 Telegram ranks this channel #13 of 64 here — alongside 63 others — read 21 August 2026
Web design & 😃 development @WebsiteDesignLearningGroup · 27,872 Telegram ranks this channel #14 of 63 here — alongside 62 others — read 10 September 2026
GitHub repos @github_repos · 27,297 Telegram ranks this channel #15 of 76 here — alongside 75 others — read 11 September 2026
Curious Coder @Curious_Coder · 134,549 Telegram ranks this channel #18 of 75 here — alongside 74 others — read 13 August 2026
Web Development @webdev_trainings · 133,855 Telegram ranks this channel #19 of 65 here — alongside 64 others — read 13 August 2026
Coding Resources @CodingResourcees · 43,841 Telegram ranks this channel #20 of 68 here — alongside 67 others — read 28 August 2026
Programmer Jokes @programmerjokes · 106,959 Telegram ranks this channel #20 of 90 here — alongside 89 others — read 15 August 2026
CODING SOLUTION - Placement Jobs & Materials @codingsolution_IT · 132,461 Telegram ranks this channel #20 of 86 here — alongside 85 others — read 13 August 2026
Tech Guide @techguide · 41,573 Telegram ranks this channel #21 of 76 here — alongside 75 others — read 29 August 2026
This channel appears in 72 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“Computer Science and Programming” (@computer_science_and_programming), 140,074 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/computer_science_and_programming.
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.