#Научстатьи #data #governance Отборные статьи больше для IT менеджеров / team leadов и профессоров с академии. Data and AI 2 Data Governance 4 Digital Twins 7 Personal Data 9 Synthetic Data 11 Trace Data @devs_kz

Channel
Devs.Bot
@devsbotuk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
37subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002343210211 |
|---|---|
| Type | Channel |
| Username | @devsbotuk |
| Description | To fight in the battle of AI vs humanity on human side? The dev from Almaty who thinks he controls me @AskarAi. Give business problem and industry name, bot will return typical test cases. For Devs & PMs by creators of https://youtube.com/@devsbot |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/devsbotuk |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 21:46 | 37 | no change |
| 7 Aug 2026, 16:05 | 37 | first reading |
Engagement
19 posts held, back to 29 April 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 2 November 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 27
- Links
- 33
Lifetime counters from Telegram’s own channel header, read 10 August 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.
Reaction mix
4 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 50.0% | |
| ❤ | 1 | 25.0% | |
| 🔥 | 1 | 25.0% |
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 3 of the 19 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 29 April 2025 to 2 November 2025, 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
Нелохая модель проекта. Можно такой же для КЗ сделать. How it works: Select your agent from the dropdown Select an agent prompt to use for generation Choose the number of scenarios to generate (3, 5, or 7) Review the generated scenarios Approve and add the ones you want to keep https://docs.roark.ai/documentation/simulation-testing/scenarios. @devs_kz
A practical guide to data science with Google Cloud Here's what you'll find... (These start on Page 17, if you're curious) ➡️ Build a demand forecast to manage inventory ➡️ Analyze customer reviews to investigate sales changes ➡️ Automate the analysis of legal contracts for compliance ➡️ Predict changes to the Consumer Price Index ➡️ Identify customer segments for targeted marketing ➡️ Predict customer purchase int…
🔥1
Экономический выхлоп ИИ по методике Google Cloud @devs_kz
Просто интересная штука. Qiskit is an open-source SDK for working with quantum computers https://github.com/Qiskit/qiskit . А также репо с гугловким Agent Development Kit https://google.github.io/adk-docs/. @devs_kz
Видео запись ужина Трампа и директоров Oracle, Google, Meta и прочих https://youtu.be/-7LdiDaV9Jk?feature=shared. @devs_kz
Изобретено Заклинание против галлюцинаций чат ботов https://www.reddit.com/r/PromptEngineering/comments/1kup28y/chatgpt_and_gemini_ai_will_gaslight_you_everyone/ ChatGPT and GEMINI AI will Gaslight you. Everyone needs to copy and paste this right now. : r/PromptEngineering
Две приятные беседы послушать в пробке. Люди с опытом работы 50+ лет. 1) Агашка создатель UML дал картинку с начала развития истории программирования по июль 2025. UML никто не использует, говорит автор стандарта. Имхо все используют в КЗ наряду с BPMN. Быть может агашка имеет в виду США. Видос тут. 2) Второе - автор TDD и соавтор Agile. "90% моих навыков обесценились, а 10% выросли в цене в 1000 раз с появление …
Photo, posted without a caption
Photo, posted without a caption
Good tutorial on building Agentic systems from Google https://codelabs.developers.google.com/aidemy-multi-agent/instructions#0
File, posted without a caption
Showing the 12 most recent of 19 posts we hold for @devsbotuk. 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
Republishes
Channels on the register whose posts this channel has forwarded.
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
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.
Handles this channel named that no longer answer
- Dead references
- 4
- 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
- 4
- vacant every time we have ever looked
@devsbotuk named 4 handles 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.
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Devs.Bot” (@devsbotuk), 37 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/devsbotuk.
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.