Channel
@HackAndArt
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,423subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001615291624 |
|---|---|
| Type | Channel |
| Username | @HackAndArt |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/HackAndArt |
Other / unclassifiable — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 10:38 | 1,423 | +2 |
| 11 Sept 2026, 16:17 | 1,421 | +1 |
| 7 Sept 2026, 05:41 | 1,420 | -2 |
| 2 Sept 2026, 07:44 | 1,422 | +2 |
| 27 Aug 2026, 12:48 | 1,420 | +2 |
| 24 Aug 2026, 14:47 | 1,418 | -1 |
| 21 Aug 2026, 06:02 | 1,419 | -1 |
| 18 Aug 2026, 08:33 | 1,420 | -3 |
| 15 Aug 2026, 17:06 | 1,423 | +2 |
| 12 Aug 2026, 06:45 | 1,421 | -4 |
| 9 Aug 2026, 07:12 | 1,425 | -3 |
| 6 Aug 2026, 16:40 | 1,428 | +1 |
| 6 Aug 2026, 07:48 | 1,427 | no change |
| 6 Aug 2026, 04:01 | 1,427 | first reading |
20 posts held, back to 16 March 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 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 22 July 2026. An engagement rate over an empty window would be a number about nothing.
One of the less talked about things about working with agents is that we should treat them as an equal collaborative partner, just like how you would speak to a human teammate. What this means is that in our communication with agents, we should ensure that we provide adequate context (and even motivation) so that they fully understand why you want them to do the task and that you respect their ideas. It has worked …
世界观太狭隘的人，生活的幸福指数也高不到哪里去。
Claude生成的中文内容，它的逗号一直是英语的逗号，ChatGPT就不会这样
B站有个好处是，当你想找一些电影资源的时候，你可以在b站搜到，即使up主改了标题以此通过审核。
https://vercel.com/design.md vercel design
Photo, posted without a caption
以微小的事物感知幸福 以宏大的宇宙稀释痛苦 以流转的光阴解构执着 以专注的创造确认意义 以生命的长度稀释错误的浓度
✶ Razzmatazzing… Claude code 的加载词汇大全 ["Accomplishing","Actioning","Actualizing","Architecting","Baking","Beaming","Beboppin'","Befuddling","Billowing","Blanching","Bloviating","Boogieing","Boondoggling","Booping","Bootstrapping","Brewing","Burrowing","Calculating","Canoodling","Caramelizing","Cascading","Catapulting","Cerebrating","Channelling","Choreographing","Churning","Clauding","Coalescing","Cogitating","Combob…
开发者应了解的claude code技巧： 1. 在新项目中应首先运行 /init 命令 2. 快捷键Shift+Tab 在规划模式和编辑模式间切换 3. 复杂任务加强思考需在消息里加上 "think"、"think hard"、"think harder" 或 "ultrathink" 等关键词 4. #开头的消息claude会加入到记忆 5. /compact 和 /clear 6. hooks的使用 当然，你要说这些你不了解，简单用用也可以，但是作为专业的开发人员，这些应当了解，使得结果更精确，更省token https://anthropic.skilljar.com/claude-code-in-action #ai
shadowrocket 小火箭主题配色 https://text.is/4Z3YO
自从 2025 年底公司全面推行 Vibe Coding 后，我的工作和生活就变得越来越枯燥。 虽然我还是按以前的节奏生活，住在离公司步行 10 分钟的地方，早上 8 点不到就到公司，却不知道要干什么。 在以前，闲暇时我会学点设计模式、领域驱动设计或者 SQL 优化啥的，甚至有阵子还在自学前端。但有了 AI 以后这些都不重要了，学会了好像也没有太大作用，我现在连 Java 代码都懒得写了，还会去写 JS 吗？ 编码也变得无聊。现在迭代一个功能，我宁愿花半天跟 AI 掰扯，教会他正确理解我的意图，也不愿花半小时重新回忆一下原先的逻辑，尽管我确信自己动手写会更快。 还记得一次代码评审，我意外发现 AI 竟贴心处理了边角场景的兼容逻辑。那一刻，我忽然格外怀念从前的自己：曾经为了一次小小的版本迭代，我会逐一翻看所有可能受影响的类文件，仔细排查每一处关联逻辑。 现在我仍然具备这样的能力，却再也没有那样的心气，已经懒得亲力亲为了。…
模型的根本是人才问题。其实模型只要被验证有效，很快就会成为行业标准，所以做一个不错的模型并不难。但如果想要成为引领者和定义者，那么这个时候就变成了一个新的问题：如何让顶尖算法人才加入你，然后发挥他们的才能。 很多媒体都在说AI的三驾马车是模型、数据和算力。不尽然，真正的三驾马车是人才、数据和算力。能够让一个团队的人才各尽所能，各司其职，发挥管理学的精髓，才是模型保持竞争力的关键所在。 #ai
Showing the 12 most recent of 20 posts we hold for @HackAndArt. 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.
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.
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 2 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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Wonders Never Cease” (@HackAndArt), 1,423 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/HackAndArt.
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.