[Slack] Role Management at Slack Controlling which users are able to take which actions is no simple task. Building this into Slack has always been an interesting challenge. In large enterprise organizations, the standard types of roles we offered to customers were too broad, and delegating a generic admin role can grant someone

Channel
Software engineering blogs
@software_engineering_blogs
On this record: Topic · Growth · Engagement · Posts · Cite this entry
190subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001469179478 |
|---|---|
| Type | Channel |
| Username | @software_engineering_blogs |
| Created | Between 1 April 2019 and 12 May 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 9 October 2026 |
| On Telegram | t.me/software_engineering_blogs |
Topic
Technology — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 13:20 | 190 | -2 |
| 22 Aug 2026, 09:29 | 192 | +1 |
| 7 Aug 2026, 07:03 | 191 | no change |
| 6 Aug 2026, 14:48 | 191 | first reading |
Engagement
20 posts held, back to 12 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 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 24 May 2021. An engagement rate over an empty window would be a number about nothing.
Recent posts
[Uber] Fraud Detection: Using Relational Graph Learning to Detect Collusion As Uber grew in popularity and scale among legitimate customers, it also attracted the attention of financial criminals in the cyberspace. One type of fraudulent behavior is collusion, a cooperative fraud action among users. For example, users collude by taking
[Airbnb] Building a faster web experience with the postTask scheduler Building a Faster Web Experience with the postTask SchedulerWhen was the last time you opened a page on a website and tried to click on something multiple times for it to work? Or the last time you swiped on an image in a carousel and it stuttered and shifted around unnaturally?While this type of
[Dropbox] How we managed our global supply chain through a year of lockdown
[Skyscanner] Maker to Manager — How We Support New Leaders Maker to Manager — How We Support New LeadersIntroductionAt Skyscanner, we take the career aspirations of our teams seriously, which is why we have spent a ton of time building our two distinct engineering paths; individual contributor IC or manager. Advancing your career as an IC is seen as a
[Facebook] Peering automation at Facebook Traffic on the internet travels across many different kinds of links. A fast and reliable way to exchange traffic between different networks and service providers is through peering. Initially, we managed peering via a time-intensive manual process. Reliable peering is essential for Facebook and
[Uber] The Architecture of Uber’s API gateway API gateways are an integral part of microservices architecture in recent years. An API gateway provides a single point of entry for all our apps and provides an interface to access data, logic, or functionality from back-end microservices. It also
[Lyft] Chaos Experimentation, an open-source framework built on top of Envoy Proxy Services are bound to degrade. It’s a matter of if, not when. In a distributed system where there are many interdependent microservices, it is increasingly difficult to know what will happen when a service is unavailable, latency goes up, or when the success rate drops. Usually, companies find
[GitHub] GitHub Artifact Exporter open source release GitHub is the home for software development teams and is the place where they collaborate and build. For larger organizations, you might have a dedicated reporting team that wants to export this activity at a
[Spotify] A Product Story: The Lessons of Backstage and Spotify’s Autonomous Culture TLDR; In episode 08 of our podcast series “Spotify: A Product Story”, we share stories and lessons from building and open sourcing Backstage, our homegrown developer portal. Hear why a developer-friendly, market-based platform like Backstage could only have been developed at Spotify where
[Dropbox] Optimizing payments with machine learning
[Rust] Six Years of Rust Today marks Rust's sixth birthday since it went 1.0 in 2015. A lot has changed since then and especially over the past year, and Rust was no different. In 2020, there was no foundation yet, no const generics, and a lot organisations were still wondering whether Rust was production ready. In the
Showing the 12 most recent of 20 posts we hold for @software_engineering_blogs. 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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“Software engineering blogs” (@software_engineering_blogs), 190 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/software_engineering_blogs.
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.