Roadmap to a career as a Backend Dev 💯 . . #backend
❤1

Channel
@the_developer_guide
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
10,924subscribers
-106 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001626339485 |
|---|---|
| Type | Channel |
| Username | @the_developer_guide |
| Description | Level up daily with insider dev hacks, smart career tips, and real talk! 🚀 ⚡️ Stay connected with me: linktr.ee/AliSamir |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 56 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/the_developer_guide |
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 11 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 17:41 | 10,924 | +1 |
| 9 Nov 2026, 02:50 | 10,923 | -1 |
| 7 Nov 2026, 20:59 | 10,924 | -2 |
| 5 Nov 2026, 18:00 | 10,926 | -1 |
| 4 Nov 2026, 15:05 | 10,927 | -3 |
| 3 Nov 2026, 14:16 | 10,930 | -7 |
| 2 Nov 2026, 15:07 | 10,937 | -3 |
| 1 Nov 2026, 13:59 | 10,940 | -1 |
| 30 Oct 2026, 14:36 | 10,941 | +2 |
| 29 Oct 2026, 13:30 | 10,939 | +2 |
| 28 Oct 2026, 15:35 | 10,937 | -2 |
| 27 Oct 2026, 14:51 | 10,939 | +1 |
| 26 Oct 2026, 18:01 | 10,938 | +2 |
| 25 Oct 2026, 17:36 | 10,936 | +2 |
| 24 Oct 2026, 20:25 | 10,934 | -2 |
| 23 Oct 2026, 19:20 | 10,936 | -3 |
| 22 Oct 2026, 16:55 | 10,939 | -5 |
| 21 Oct 2026, 09:31 | 10,944 | -2 |
| 20 Oct 2026, 10:11 | 10,946 | +2 |
| 18 Oct 2026, 11:19 | 10,944 | first reading |
59 posts held, back to 11 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 58 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 11 November 2026 |
|---|---|
| Posts held | 59 (11 July 2026 – 11 November 2026) |
| Views total | 18,439 |
| Reactions total | 62 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 21:57 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 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
161 reactions across 52 posts, in 4 distinct kinds. The most used accounts for 95.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 153 | 95.0% | |
| 👏 | 3 | 1.86% | |
| 💯 | 3 | 1.86% | |
| 👍 | 2 | 1.24% |
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 53 of the 59 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 161 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 59 most recent posts we hold, published 11 July 2026 to 11 November 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.
Telegram’s own ‘edited’ marker: 2 of 22 posts held from the last 30 days (9.09%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Roadmap to a career as a Backend Dev 💯 . . #backend
❤1
ليه الـ AI مش دايمًا بيطلع النتيجة اللي أنت متوقعها؟ . . أغلبنا لما بيستخدم AI بيدخل يكتب Prompt، ويستنى الـ AI يطلعله النتيجة. يلاقي النتيجة مش زي ما كان متوقع، فيبدأ يعدل، ويكتب Prompt تاني، ويعدل تاني وتالت، وبعد شويه يكتشف إن التعديلات الجديدة بوظت حاجات كانت شغالة أصلاً... وده غالبًا بيحصل لأننا بنبدأ نطلب من الـ AI ينفذ قبل ما نكون حددنا بشكل واضح إحنا محتاجين إيه، وإيه التفاصيل والـ Requirements اللي المفروض …
❤4
دورة Pre-CyberSecurity . . دورة مصممة لتأهيل الطلبة لدخول مجال الأمن السيبراني عن طريق دراسة أساسيات الشبكات، أساسيات نظام اللينكس، أساسيات نظام الويندوز، وأساسيات مجال الأمن السيبراني، مع رسم خطة تأسيسية للمبتدئين ومشاركتهم أحدث المصادر التعليمية. https://netriders.academy/all-courses/pre-cybersecurity . . #cybersecurity
❤1
🚀 هل تبحث عن فرصة عمل حقيقية؟ وزارة الشباب والرياضة تدعوك للمشاركة في ملتقى توظيف شباب مصر 2026، أكبر تجمع للشركات وجهات التوظيف الباحثة عن الكفاءات الشابة. ✅ أكثر من 200 شركة عارضة ✅ آلاف الفرص الوظيفية في مختلف التخصصات ✅ مقابلات مباشرة مع مسؤولي التوظيف ✅ فرص للتدريب والتطوير المهني 📅 الموعد: 28 نوفمبر 2026 بمختلف المحافظات للتسجيل للحضور https://forms.cloud.microsoft/r/09QAmEuU8P لا تضيع الفرصة… قد تكون وظيف…
❤2
رسالة مهمة من أمازون لكل Software Engineer في عصر AI . . دور الـ Software Engineer بيتغير. مش كفاية تكون شاطر في كتابة الكود، لازم تعرف تستخدم AI بذكاء، وتفهم إمتى تعتمد عليه وإمتى تتدخل بخبرتك. المهندس اللي هيتميز هو اللي يقدر: - يستخدم AI و Agents لزيادة إنتاجيته. - يراجع ويفهم الكود اللي AI بيكتبه. - يفكر في System Design وجودة الحل. - يفهم احتياجات البيزنس والعميل. - يركز على النتيجة مش عدد أسطر الكود. قيمتك كم…
❤5
إمتى تستخدم Module Bundler؟ . . تخيّل إنك شغال على مشروع JavaScript فيه عشرات الملفات، ومكتبات خارجية كتير، وكل ملف بيعتمد على ملفات تانية... هل المتصفح هيقدر يتعامل مع كل الملفات والـ Dependencies دي بسهولة؟ وإزاي تقدر تجهّز المشروع بحيث يكون أداؤه أفضل، وحجمه أصغر، والكود متوافق مع المتصفحات المختلفة؟ هنا بيظهر دور الـ Module Bundler. أداة ممكن تفرق جدًا في طريقة تنظيم مشروعك وتجهيزه للـ Production، وعلشان كده خ…
❤2
مفهوم الـ HTTP Caching 💯 . . لو مهتم بـ Web Performance، فـ الـ HTTP Caching من المفاهيم الأساسية اللي لازم تكون فاهمها، لأنه بيساعد بشكل كبير في تقليل وقت تحميل المحتوى وتقليل عدد الـ Requests على السيرفر. تعال نشوف إيه هو الـ HTTP Caching، وإزاي بيشتغل، وإيه أهم الإعدادات اللي بنستخدمها للتحكم فيه. ——— 📌 يعني إيه Caching؟ الـ Caching معناه إن الموقع بيخزن بيانات معينة في مكان قريب من المستخدم (زي المتصفح أو سير…
❤2👍1
مفهوم الـ Rate Limiting 💯 . . من أهم الحاجات اللي لازم ناخد بالنا منها وإحنا بنبني أي Web Application هي إننا نتحكم في حجم الـ Requests اللي بيوصل للسيرفر، وده دور الـ Rate Limiting. تعال نبسط الفكرة ونتكلم ليه الـ Rate Limiting مهم وليه لازم نفكر فيه في المشروع بتاعنا. ——— الـ Rate Limiting معناه إننا نحدد عدد الطلبات (Requests) اللي مسموح لأي مستخدم أو خدمة إنها تعملها على السيرفر خلال فترة معينة. يعني مثلًا، م…
❤3
أسئلة باك إند مهمة 💯 https://roadmap.sh/questions/backend . . #backend
❤1
مراجعة سريعة عن الـ OOP 💯 https://youtu.be/dZh68SpsgoI . . #software_engineering
❤2
AWS Cloud Training Full Course for Beginners (Better Than Any Bootcamp) . . - AWS First Principles - Cloud Architecture Fundamentals - Cloud Infrastructure Fundamentals - AWS Case Studies - Cursor & AI Agents AWS - Cloud Security Q&A - Jobs & Careers with Gaz - Interviews & Career Q&A ——— 📌 Course Link: https://youtu.be/EHUCb92gUg0 ——— #devops
❤3
The Complete Backend Developer Roadmap [2026] 🚀 https://substack.com/@arslanah/note/p-179838506 . . #backend
❤5
Showing the 12 most recent of 59 posts we hold for @the_developer_guide. 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.
@the_developer_guide edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 13 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“DevGuide” (@the_developer_guide), 10,924 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/the_developer_guide.
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.