Channel
@ProgrammingTip
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
46,484subscribers
-725 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001124766173 |
|---|---|
| Type | Channel |
| Username | @ProgrammingTip |
| Description | Programming & AI: Tips 💡 Articles 📕 AI & LLMs 👾 Design, Architecture, Principles ✅ 🇳🇱 Contact: @MoienTajik |
| Created | 7 July 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/ProgrammingTip |
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 21 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 22:19 | 46,484 | -85 |
| 19 Sept 2026, 17:21 | 46,569 | -45 |
| 17 Sept 2026, 07:58 | 46,614 | -63 |
| 15 Sept 2026, 06:58 | 46,677 | -46 |
| 13 Sept 2026, 12:17 | 46,723 | -45 |
| 11 Sept 2026, 15:41 | 46,768 | -44 |
| 9 Sept 2026, 00:38 | 46,812 | -38 |
| 5 Sept 2026, 19:59 | 46,850 | -12 |
| 3 Sept 2026, 18:19 | 46,862 | -30 |
| 2 Sept 2026, 11:34 | 46,892 | -17 |
| 1 Sept 2026, 09:43 | 46,909 | -22 |
| 31 Aug 2026, 07:27 | 46,931 | -20 |
| 30 Aug 2026, 03:55 | 46,951 | -7 |
| 29 Aug 2026, 01:49 | 46,958 | -16 |
| 27 Aug 2026, 23:17 | 46,974 | -1 |
| 27 Aug 2026, 00:38 | 46,975 | -20 |
| 26 Aug 2026, 01:03 | 46,995 | -12 |
| 25 Aug 2026, 04:15 | 47,007 | -14 |
| 23 Aug 2026, 21:19 | 47,021 | -15 |
| 22 Aug 2026, 06:38 | 47,036 | first reading |
33 posts held, back to 22 August 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 104 pages of 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 26 September 2026 |
|---|---|
| Posts held | 33 (22 August 2024 – 26 September 2026) |
| Views total | 30,430 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 18:03 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.
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Claude Opus 5.5 is available in the API 🚀 Anthropic released Claude Opus 5.5, and it is available through the Claude API. The practical pitch is simple: lower typical token costs than Opus 5, plus a faster mode when response time matters more than squeezing out the last bit of reasoning. What to check in your evals: • Run the same tool-use and coding tasks against Opus 5. • Measure latency separately for normal a…
Claude Opus 5.5 is now on the Claude Platform 🚀 Anthropic introduced Claude Opus 5.5, a lower-cost frontier model available in Claude Code and through the Claude Platform. That matters if your agent workload has been split between a high-end model for hard tasks and cheaper models for everything else. A lower-cost Opus tier can change where that handoff happens. What to check: • Run your existing eval set, not a …
GPT-6 Sol and GPT-6 Luna are in the API 🚀 OpenAI shipped GPT-6 Sol and GPT-6 Luna for API developers, alongside their availability in Codex and ChatGPT. This is a two-model release, so do not blindly swap your existing production model. Put both behind the same eval set first: tool calls, structured output, long-context retrieval, refusal behavior, and latency under your real prompt size. What to do this week: • …
Hex turns GPT-6 Astra analysis into visual reports 🚀 Hex is using GPT-6 Astra to turn complex analysis into visual reports. The useful bit is not just asking a model to summarize a table. It is moving from an analysis request to a result people can inspect and share. What this points to: • Analysis as an artifact: teams need charts, assumptions, and outputs, not a chat answer pasted into Slack. • Human review stil…
Cloudflare saved 100 TB of RAM with math and Rust 🔥 Cloudflare reclaimed more than 100 TB of RAM globally in a Pingora-based consistent-hashing service. No new hardware. The win came from changing data representation and the algorithms around it. ✅ Lessons: • Measure retained memory, not only allocation rate. • Check collection shape: duplicated keys, oversized buckets, and pointer-heavy graphs add up fast. • Fix…
GitHub improved the Copilot code review flow 🔥 GitHub shipped an improved Copilot code review experience. That matters most on the boring, high-volume PRs where reviewers need help finding a real issue, not another summary of changed files. For C# teams, use Copilot review as an extra pass on every ASP.NET, EF Core, and library PR. Then keep the human review focused on contracts, failure behavior, and whether the c…
Gemini 3.8 Live is generally available 🚀 Google moved Gemini 3.8 Live and Gemini 3.8 Live Extended Thinking to general availability in the Gemini API. These are the real-time audio models exposed through the Live API. Live is for the voice path: streaming audio in, streaming audio out, and handling a conversation without bolting together STT, an LLM call, and TTS yourself. What to check: • Gemini 3.8 Live: the lo…
GitHub moved the Copilot runtime to Rust 🚀 GitHub migrated the runtime behind Copilot to Rust, and used Copilot during the migration itself. ✅ Why this is worth reading: • Runtime work is systems work: a language migration means tracing real production behavior, not just translating syntax. • Copilot was part of the workflow: useful for exploring an unfamiliar codebase, drafting changes, and keeping momentum thro…
.NET 11 performance work is landing across the stack 🔥 Microsoft published the running list of performance improvements headed for .NET 11. This is not one magic runtime switch. The work spans the runtime, JIT, libraries, and tooling paths that show up in normal application code. Use the post as a migration checklist: • Find code that is CPU-bound, allocation-heavy, or called per request. • Run your benchmarks on …
Make coding agents earn the green check 💡 Do not end an agent task with "implement this." End it with a command that can fail. For a .NET repo, that might be dotnet test, a focused test project, a formatter check, or a small reproduction script. Tell the agent which command to run, what output to inspect, and what it should do if the command fails. A good task contract has three parts: • Change: the files or beha…
GPT-6 Astra is OpenAI's new work model 🚀 OpenAI shipped GPT-6 Astra. They are calling it the next generation in intelligence for work. Not a research teaser. A work model. Expect the name in agent stacks and coding tools. Why you care: ✅ New flagship name to put on your eval harness ✅ Pitched for workplace tasks, not playground chat ✅ If you pin model ids in config, read this before you swap anything Start with …
Agents API is in public beta 🚀 OpenAI put the Agents API in public beta. Cloud agents with the Codex harness, managed sessions, tools, and either a hosted sandbox or one you bring yourself. What shipped: ✅ Codex harness, not a chat-completions wrapper you have to babysit ✅ Managed sessions and tools in the API ✅ Hosted sandboxes, or bring your own Public beta, so expect sharp edges. If you ship coding agents or a…
Showing the 12 most recent of 33 posts we hold for @ProgrammingTip. 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.
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.
Named by 1 registered channel — 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.
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 27 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.
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 6 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Programming & AI Tips 💡” (@ProgrammingTip), 46,484 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/ProgrammingTip.
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.