Telegram RegisterThe public register of Telegram
Telegram profile photo for andreyka26_se

Channel

andreyka26_se

@programming_space

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,143subscribers

+58 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001178612004
TypeChannel
Username@programming_space
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/programming_space

Growth

1,0851,1461,115.58 August 2026 — 1,085 subscribers8 August 2026 — 1,086 subscribers11 August 2026 — 1,126 subscribers15 August 2026 — 1,133 subscribers18 August 2026 — 1,143 subscribers21 August 2026 — 1,122 subscribers25 August 2026 — 1,140 subscribers27 August 2026 — 1,144 subscribers30 August 2026 — 1,145 subscribers3 September 2026 — 1,146 subscribers8 September 2026 — 1,143 subscribers1,1438 August 20268 September 2026
11 measurements spanning 31 days, net +58. 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 1,076–1,155 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 07:351,143-3
3 Sept 2026, 12:001,146+1
30 Aug 2026, 22:051,145+1
27 Aug 2026, 23:551,144+4
25 Aug 2026, 01:241,140+18
21 Aug 2026, 16:051,122-21
18 Aug 2026, 18:341,143+10
15 Aug 2026, 11:051,133+7
11 Aug 2026, 15:321,126+40
8 Aug 2026, 16:051,086+1
8 Aug 2026, 01:011,085first reading

Engagement

20 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

119 reactions across 19 posts, in 5 distinct kinds. The most used accounts for 46.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5546.2%
2521.0%
👍2016.8%
😁1512.6%
🤯43.36%

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 19 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 119 reactions 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 5 August 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.

Recent posts

7 Aug 2026, 23:43 UTC52 views8 reactionsread 8 August 2026
Video

Video, posted without a caption

🔥4😁3👍1

7 Aug 2026, 23:43 UTC53 views2 reactionsread 8 August 2026

Literally the same conversation (the fucker has access to all the skills, logs, mcps) “Are these the connection of type A”? - yes (Opening different chat and somehow realize they are type B) (Going back to original chat) “OR MAYBE THEY ARE FUCKING CONNECTION OF TYPE B??????” - yes they are connection type B ???????? ????????????????????????

😁2

7 Aug 2026, 23:40 UTC53 views2 reactionsread 8 August 2026

And investigating with AI is crazy exhausting if it is unknown thing. I self reflected why. With ai, anything it told me can be hallucinations and false. So after asking 5-6 questions about how it works and what can be the root cause - you have tons of combinations of which of these might be false. And therefore it is painful to even try to ground up your conclusions on these AI answers. Or if you do it, you wasted

👍2

7 Aug 2026, 23:25 UTC64 views5 reactionsread 8 August 2026

Fuck AI first projects. Now I have to deep diving into this shit for 10 hours today that has been vibecoded, because it suddenly stopped working and now 5 engineers don’t know why. This is what happens, when you dont have code ownership(or your app is crud trivial shit, which is not our case at all) Fuck ai. I want ai to disappear, to be forbidden in software engineering (except frontend)

😁4🤯1

7 Aug 2026, 14:13 UTC226 viewsread 8 August 2026
Photo

For me it is like that as well. I am very poor user of agents tbh. I just say to them what to do and then swearing that they didn’t do what I said until they do.😁 Sometimes I do it in plan mode. Sometimes I am writing skill (we have bunch of skills at my job). They might be helpful. I have heard about spec driven, but people say it is hard to maintain specs I was mostly reading claude/cursor off docs === Share y

7 Aug 2026, 14:00 UTC239 views4 reactionsread 8 August 2026

Btw interview round “to check your AI usage, agentic development approaches” is already a thing that exists or getting onboarded to hiring process. So learn how to properly use agents. This is now not an engineering skill, but interview skill as well

4

7 Aug 2026, 01:51 UTC306 views6 reactionsread 8 August 2026
Photo

Seen post like MB/s vs Mb/s, and the difference. Well actually there are more😁 Mebibits - bits in binary 1024 format Mebibyte - bytes in binary 1024 format Megabit - bits in decimal 1000 format Megabyte - bytes in decimal 1000 format

6

6 Aug 2026, 21:58 UTC313 views7 reactionsread 8 August 2026

Btw yea, most of the “protocol” things are amazingly explained in rfc, with “official” terminology and stuff. Whenever you have discussion with someone, your argument: “this is rfc confirming my point” - is killer-argument. Applies to http, dns, and whole tcp/ip stack, oauth/oidc(not really on rfc but has official doc), etc I made so many people crazy with “jwt with login+password is insecure antipattern discourag

🔥52

6 Aug 2026, 21:32 UTC307 views1 reactionsread 8 August 2026
Photo

Yeeea, flashbacks in instagram dm. This is how all “blogging” thing and andreyka26.com started. There was no-one explaining authorization like I do: deep, with all questions and reasons behind what’s done covered, detailed step-by-step, etc So I investigated, built, made a video and article, and in 2023 +- it got pretty high attention. But not anymore, I think now claude might explain it better, maybe. Side thing, I

1

6 Aug 2026, 02:30 UTC365 views10 reactionsread 8 August 2026

I was like, how old are you? Yea, 21. You started lately then , right? Well, I have 5 years of experience 💀💀💀💀 I am like, WHAAAT?

🔥10

6 Aug 2026, 02:28 UTC362 views11 reactionsread 8 August 2026

Btw the guy is crazy. I thought I am the “early bird”, started working when I was 18, had pretty much only first year of uni and then skipped most of the stuff But Maksim started doing freelance tasks at 16-17, and IN THE BEGINNING of the first year in uni, when he was 17 - he interviewed and got a job🤯. Practically, he fully skipped uni. Legend. Big respect

🔥11

6 Aug 2026, 00:41 UTC351 views5 reactionsread 8 August 2026
Photo

Daily 362nd day streak It took me some time to come up with nice solution, but in general, since easy - any bruteforce will fit here. No pattern though. https://leetcode.com/problems/smallest-divisible-digit-product-i/description/?envType=daily-question&envId=2026-08-06 #daily #easy #nopattern

🔥5

Showing the 12 most recent of 20 posts we hold for @programming_space. 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.

Mentions

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.

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.

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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“andreyka26_se” (@programming_space), 1,143 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/programming_space.

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.