Channel
@AlseCode
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
80subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001413784424 |
|---|---|
| Type | Channel |
| Username | @AlseCode |
| Description | Краткость — сестра разработки Опыт инженерных изысканий и опасных экспериментов в сфере Kotlin/Java и прочего. Блог: https://alse-code.ru Менторю: https://solvery.io/ru/mentor/alexey_stepanov Связь: @arsennikum |
| Created | Between 1 April 2019 and 5 May 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/AlseCode |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 19:16 | 80 | no change |
| 7 Aug 2026, 20:10 | 80 | first reading |
19 posts held, back to 5 May 2021 — 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 July 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
Measured directly from 1 video 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.
37 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 40.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 15 | 40.5% | |
| 🤡 | 7 | 18.9% | |
| ❤ | 5 | 13.5% | |
| 💩 | 4 | 10.8% | |
| 🔥 | 3 | 8.11% | |
| 🍓 | 1 | 2.70% | |
| 🎅 | 1 | 2.70% | |
| 🤬 | 1 | 2.70% |
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 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 37reactions 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 5 May 2021 to 2 July 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Немного о методах решения конфликтов в разработке. Proof Of Work. При возникновении конфликта, например, на код-ревью (дальше рассмотрим и другие примеры) - хорошим решением для руководителя будет организация следующего процесса: кто напишет тесты на свой вариант с бОльшим покрытием, то решение и принимается. Плюсы/минусы: + хорошее покрытие говорит о хорошей архитектуре. На практике подверждается как минимум жизне…
🤡7👍6❤2🍓1🔥1
Как починить IntelliJ IDEA Недавно мой менти (ученик) обратился с такой проблемой. При работе с проектом любимый продукт JetBrains начинает тупить. Проблема достаточно частая: всё подсвечивается красным, хотя все зависимости есть. Что делать? Продиагностируем: Запустите из консоли mvn compile test или ./gradlew build. Если не собирается, значит проблема не в IntelliJ. Если собирается, а в IDEA нет, значит Решаем п…
👍5🤬1
Провожу сегодня вебинар для общественной организации "Общее Дело" по профориентации в ИТ. Для аудитории моего канала основная тема возможно будет слишком проста, но кто сейчас в ситуации "прошёл обучение, всё знаю, но как теперь найти первую работу?" - вы те, кто мне нужен на этом вебинаре! Поделюсь секретами и предложу варианты 😏 Сегодня в 19:00 Мск, регистрация по ссылке https://obchee-delo.ru/it
💩3❤2🎅1🔥1
Отличные размышления по поводу собесов. Нестандартный взгляд, новые мысли и логическое обоснование рисков найма, которые видны чаще интуитивно
🔷 "Обязан ли разработчик развиваться?" - статья на Хабре полностью подтверждает актуальность целей нашего объединения архитекторов. Мы уже не раз обсуждали в чате сообщества @ru_arc_chat о том, что требуются новые способы разрешения противоречия между трудоемкостью освоения перегруженной области знаний и стесненностью ресурсов времени практикующего специалиста. Именно этим фактором вызван взрывной рост интереса на …
👍2💩1🔥1
Выступаю завтра на конференции в Бишкеке с темой SQL vs NoSQL vs NewSQL. Ориентиры в мире БД. Также будет много других крутейших докладов и классных спикеров, подключайтесь к трансляции или лично! Пост от коллеги с подробным описанием: https://t.me/mikrotikninja/1357 Или от одних из организаторов в инсте: https://www.instagram.com/p/CdplKb_oLYO Запись выступления https://youtube.com/watch?v=Yxu-AHXGJMM&t=21790s
Как достигается изоляция транзакций в PostgreSQL? Разве блокировками? Очень интересный вопрос для собеса, но я ничего подобного не слышал ни разу и сам не спрашивал. Но теперь запишу и буду задавать😎 Первое, что приходит на ум, когда читаешь про ACID и конкретно про Isolation, - "да ведь это всё на блокировках, всё ясно!" Отнюдь - инженерная мысль ушла далеко. В Postgres'е реализован механизм многоверсионности: х…
❤1👍1
Проблема с микросервисами Видео от автора одной из основных книг по CD Очень многие мысли пересекаются с моим докладом, но под другим углом --- #concept #погружение #микросервисы
👍1
Если ты ещё не знаешь, как выглядит карьерная лестница программистов..
Photo, posted without a caption
Kotlin log VS Lombok Скучаете по аннотации @Slf4j из Lombok? Забываете, как там пишется это всё вручную? Решение есть! Всего несколько движений мышкой и корень… Preferences -> Editor -> Live Templates -> Kotlin -> + -> Live Template: Abbreviation: log Description: insert slf4j log Template Text: private val log = LoggerFactory.getLogger(this::class.java) Applicable context->Define: Kotlin: class (см.картинку) И …
Микросервисы. Послевкусие - устали от темы микросервисов? Посмотрим на них с непопулярной стороны - сбиваем спесь и разгребаем последствия одного из мощнейших хайпов десятилетия - относятся ли плюсы микросервисов действительно к микросервисам? - может не надо или когда-нибудь может и надо и что происходит? монорепы, модули, soa, unix-пайпы, FaaS? Спокойствие, только спокойствие --- Запись с конференции Ссылки из п…
Showing the 12 most recent of 19 posts we hold for @AlseCode. 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.
Citation-graph rank — 466,948 of 1,189,255entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“AlseCode | Краткость и раскопки по разработке” (@AlseCode), 80 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/AlseCode.
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.