Channel
@codervlogger
On this record: Growth · Engagement · What this channel posts · Posts · Cite this entry
78subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001235471475 |
|---|---|
| Type | Channel |
| Username | @codervlogger |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/codervlogger |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 17:37 | 78 | -1 |
| 9 Aug 2026, 19:46 | 79 | no change |
| 7 Aug 2026, 20:37 | 79 | first reading |
16 posts held, back to 15 July 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 16 posts for this entry, the most recent from 22 April 2025. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 videos 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.
If you are building a tool for Redis, this might interest you. maxDEV requires a lot of manual testing, so I put together some tooling to automate part of the testing: 1) create a Redis server with initial data, 2) simulate live traffic with different data types, 3) stop, clean up, and restart from scratch. This short video demonstrates these capabilities. Source code: https://github.com/KenanBek/maxDEV/tree/main/…
This is the reason why you should not entirely rely on stats. #buildinpublic
Enhanced Note Viewing Experience for Talking Mind This update focuses on enhancing the user experience when viewing and interacting with your notes: 1. Improved Audio Note Display: Audio notes now show both the player and transcription (if available) in a more organized layout. 2. Full-Width Layout: Note items now utilize the entire width of the screen for better readability and content display. 3. Consistent Spa…
Just published this devlog My first dev log after a long break: https://www.codervlogger.com/building-a-native-ios-app/
Xcode crushed when I wanted to split a 600-line Swift file into two different files by copying and pasting.
There are still many missing features, but I am slowly preparing for the release of Talking Mind (this name has yet to be approved by Apple). You can join the waitlist here: https://www.appbaza.com/talking-mind
Today's progress with my note-taking app. It is a "native" iOS and Xcode project using Swift and Swift Data. Left side: previous version with old UI Right side: updated version with refreshed UI It will take a few more iterations before I am happy with the UI and the User Experience (UX), but I like the updated audio recording components.
Quick product demo. I added voice to text to create notes. Sound on 📢
I love this view in Xcode, which shows resource utilization as the app is run on a real iOS device.
Renaming a model in Swift and Xcode. Xcode has all the potential to become the best programming IDE. I hope Apple adopts new AI features without sacrificing the core editing functionality.
But I was switching between Xcode and Cursor all the time. After all these AI tools, writing code in Xcode seems like the Stone Age.
With no native iOS development experience, it took me a couple of hours to get from 0 to a List/Details-based application. Next, will try similar app using React Native/Expo.
Showing the 12 most recent of 16 posts we hold for @codervlogger. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“CoderVlogger” (@codervlogger), 78 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/codervlogger.
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.