Warum Magnete besser sind als Jira #AgileSoftwareentwicklung #JIRA In der beliebten Reihe "Was Tools aus unserer Arbeitsweise machen" hier mal ein ungleicher Kampf: Magnete gegen Jira․

Channel
heise Developer
@heise_developer
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
72subscribers
-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 | -1001126276280 |
|---|---|
| Type | Channel |
| Username | @heise_developer |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 10 October 2026 |
| On Telegram | t.me/heise_developer |
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 28 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 29 Sept 2026, 08:18 | 72 | -1 |
| 11 Sept 2026, 03:54 | 73 | +1 |
| 20 Aug 2026, 02:56 | 72 | -1 |
| 9 Aug 2026, 22:15 | 73 | no change |
| 6 Aug 2026, 12:02 | 73 | first reading |
Engagement
20 posts held, back to 11 January 2024 — 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 11 January 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
Neu in ․NET 8․0 [2]: Neue Anwendungsarten #NET80 #Net #Blazor #Microsoft #Webentwicklung Blazor bekommt in ․NET 8․0 einen Auto-Rendering-Modus und Blazor Static-Server-Rendering․
Buchbesprechung: Not with a Bug, But with a Sticker #Buch #Datenqualität #MLModellTraining #MachineLearning #Softwareentwicklung Das neue Werk aus dem Wiley-Verlag behandelt verschiedene Arten von Attacken auf Machine-Learning-Systeme – und wie damit umzugehen ist․
Die Produktwerker: Reflexion – der Schlüssel zur Weiterentwicklung #AgileSoftwareentwicklung #ProductOwner #Projektmanagement #agilesProjektmanagement In dieser Episode des Podcasts geht es passend zum Jahresende um Reflexion, eine gute Möglichkeit zur persönlichen und beruflichen Weiterentwicklung․
Digitale Produkte richtig zu bauen, ist komplex – im Team aber zu meistern #Angular #JavaScript #Webentwicklung Auf der Onlinekonferenz "Agile Softwareentwicklung im Unternehmen 2023" behandelt Markus Andrezak die speziellen Schwierigkeiten beim Bauen digitaler Produkte․
Neu in ․NET 8․0 [3]: Primärkonstruktoren in C# 12․0 #NET80 #Net #CSharp #Microsoft Die Programmiersprache C# bietet in Version 12․0 die Möglichkeit, über eine Parameterliste hinter dem Typnamen einen Primärkonstruktor zu definieren․
Die Produktwerker: Zielsetzung – mit Fokus in die Weiterentwicklung #AgileSoftwareentwicklung #ProductOwner #Projektmanagement #agilesProjektmanagement Neues Jahr, neues Glück? Auf die Reflexion zum Jahresende folgt die Zielsetzung als Schlüssel der persönlichen Weiterentwicklung zum Jahresanfang․
DevOps ist eine Grundeinstellung – und so funktioniert sie #DevOps #DevSecOps #DevSecOpsTools #Softwareentwicklung #Softwarequalität DevOps trifft auch unter IT-Fachleuten noch häufig auf Skepsis․ Es ist an der Zeit, die Missverständnisse auszuräumen und die Vorteile in den Fokus zu rücken․
Vision Pro: Welche Entwickler zum Start mit dabei sein wollen #Apple #Apps #VisionPro #visionOS Die Veröffentlichung der Apple Vision Pro in den USA naht․ Einige Entwickler fiebern diesem Augenblick seit Monaten entgegen – auch aus Deutschland․
JavaScript Rising Stars 2023: Neue UI-Komponentensammlung stößt Bun vom Thron #GitHub #JavaScript #JavaScriptFramework #React #UserInterface Das beliebteste JavaScript-Projekt 2023 heißt laut einer Studie shadcn/ui․ Der Newcomer ist eine Radix-basierte Sammlung von UI-Komponenten․
Gericht: US-Verbraucher können Open-Source-Code einklagen #Fernseher #GNUGPL #Immaterialgüter #Immaterialgüterrecht #Kalifornien #Linux #OpenSource #Recht #SmartTV #SourceCode #USA #Urheberrecht #Verbraucherrechte #Vizio Der TV-Hersteller Vizio nutzt Open Source Code, rückt ihn aber nicht heraus․ TV-Käufer dürfen Vizio deswegen verklagen, sagen zwei Gerichte in Kalifornien․
Neu in ․NET 8․0 [4]: Collection Expressions in C# 12․0 #NET80 #Net #CSharp #Microsoft Das aktuelle Release der Programmiersprache C# vereinfacht das Initialisieren von Collections wie Listen․
Showing the 12 most recent of 20 posts we hold for @heise_developer. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 2
- 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
- 2
- vacant every time we have ever looked
@heise_developer named 2 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 20 posts, 10 August 2026 – 10 August 2026
named in 20 posts, 10 August 2026 – 10 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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“heise Developer” (@heise_developer), 72 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/heise_developer.
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.