Channel
@dev_ascent
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003221791392 |
|---|---|
| Type | Channel |
| Username | @dev_ascent |
| Description | Строю карьеру в IT с 15 лет, транслирую свой путь Backend-разработчик: Go | Python | Микросервисы Цель — Senior к 18 годам и финансовая независимость. Про жизнь: путь, ошибки, личный опыт Делюсь кодом, архитектурой и реальным опытом. Связь: @CodesForge |
| Created | 3 November 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dev_ascent |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 19:18 | 7 | no change |
| 10 Aug 2026, 07:16 | 7 | first reading |
7 posts held, back to 3 November 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 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 7 posts for this entry, the most recent from 3 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
18 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 94.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 17 | 94.4% | |
| 👎 | 1 | 5.56% |
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 6 of the 7 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 3 November 2025 to 3 March 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.
🔥 Уровни изоляции транзакций в PostgreSQL - Когда несколько пользователей работают с базой одновременно, без контроля начинается хаос. Чтобы этого избежать, в SQL есть 4 уровня изоляции. 1️⃣ Read Uncommitted — Технически можно читать незакоммиченные данные (грязное чтение). — В PostgreSQL не поддерживается — автоматом повышается до Read Committed. 2️⃣ Read Committed (по умолчанию) — Видишь только то, что уже заком…
👍1👎1
🚀 Вышла моя библиотека secure-python-utils для FastAPI/Python! Всем привет! Выпустил свой первый production-ready toolkit для backend: secure-python-utils. Внутри: • Argon2-хэширование паролей (безопасность) • Rate Limiting на Redis (анти-спам, ограничение запросов) • Logger для дебага и аудита Почему стоит попробовать? • Простая интеграция — пара строк, и сервис защищён • Идеально для pet-проектов, стажирово…
👍3
🚀 BACKGROUND TASKS В FASTAPI: МГНОВЕННЫЕ ОТВЕТЫ API Сегодня о том как делать API в 100 раз быстрее с Background Tasks. 🎯 СУТЬ: Клиент получает ответ мгновенно, а тяжелые операции выполняются в фоне после отправки ответа. ⚡️ РЕЗУЛЬТАТ: • Было: 3+ секунды ожидания • Стало: 100ms мгновенный ответ • Производительность: +3000% 💡 КОГДА ИСПОЛЬЗОВАТЬ: • Отправка email • Обработка файлов • Сложные вычисления • Логирование…
👍3
⚡️ RabbitMQ vs HTTP: когда что использовать HTTP — для мгновенного ответа: • Логин пользователя • Оплата заказа • Проверка баланса RabbitMQ — для фоновых задач: • Отправка email • Обработка изображений • Сбор аналитики • Нотификации 💡 Правило: Нужен ответ сейчас → HTTP Можно подождать → RabbitMQ
👍3
📊 ИНДЕКСЫ В БАЗАХ ДАННЫХ: от теории к практике Сегодня разбираем индексы на примере моего проекта с RabbitMQ: 🔍 ПРОБЛЕМА: Один из запросов в микросервисе работал 500ms EXPLAIN показывал "Seq Scan" - полное сканирование таблицы 🎯 РЕШЕНИЕ: Добавил составной индекс: CREATE INDEX idx_user_covering ON users (username, email) INCLUDE (created_at); 📈 РЕЗУЛЬТАТ: - Время запроса: 500ms → 15ms - Тип сканирования: Seq Scan …
👍3
🚀 Запускаю Dev Ascent — канал о профессиональном росте в разработке Меня зовут Влад, мне 15 лет. Я backend-разработчик, и сегодня начинаю этот технический дневник. Что здесь будет? - Реальные проекты на Go и Python с полным разбором архитектуры - Глубокая работа с базами данных: индексы, оптимизация запросов, EXPLAIN ANALYZE - System design и микросервисные паттерны - Еженедельные отчеты о прогрессе Мой стек: - P…
👍4
Channel created
Showing the 7 most recent of 7 posts we hold for @dev_ascent. 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Dev Ascent” (@dev_ascent), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dev_ascent.
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.