Никогда не упоминайте знаменитый Zen of Python: ни в шутку, ни всерьез. Если упоминает кто-то другой, пропускайте мимо ушей, не важно насколько он именит.

(с) https://grishaev.me/zen-of-python/

Хорошим примером служит история с Log4j. Когда я читал, что было под капотом, вставали волосы во всех местах. Ощущение, что разработчики объехали все сумасшедшие дома, записали пожелания пациентов и выполнили их дословно. Добавьте в шаблоны Тьюринг-полный язык? Хорошая идея. Хочу подгрузку классов по урлам? Считайте, уже сделано. Напишите фасад над фасадом над фасадом? Уже в этом релизе.

(с) https://t.me/igrishaev_blog/866

Dear so-called "social" websites.

Your catchword is "share", but you don't want us to share. You want to keep us within your walled gardens. That's why you've been removing RSS links from webpages, hiding them deep on your website, or removed feeds entirely, replacing it with crippled or demented proprietary API. FUCK YOU.

(c) https://github.com/RSS-Bridge/rss-bridge?tab=readme-ov-file#rant

An even more dispiriting upshot of this is that, as developers, we spend an ever greater proportion of our time merely fixing up the output of these wondrous babbling machines. While the LLMs get to blast through all the fun, easy work at lightning speed, we are then left with all the thankless tasks: testing to ensure existing functionality isn’t broken, clearing out duplicated code, writing documentation, handling deployment and infrastructure, etc. Very little time is actually dedicated to the thing that developers actually love doing: coding.

(c) https://chrisloy.dev/post/2025/09/28/the-ai-coding-trap

The law is clear that large corporations have no right to stop you from owning wrenches

(c) https://www.perplexity.ai/hub/blog/bullying-is-not-innovation

...planning to move away from GitHub owing to concerns about over-reliance on JavaScript, GitHub's ability to deny service, declining usability, inadequate moderation tools, and "over-focusing on LLMs and generative AI, which are destroying the open web (or what remains of it) among other problems"

https://www.theregister.com/2025/12/02/zig_quits_github_microsoft_ai_obsession/

I don’t want to end up as a code janitor, cleaning up what the AI throws over the wall

(c) https://addyosmani.com/blog/next-two-years/

Если вдруг ваш день недостаточно поганый и так, то могу ли я представить вашему вниманию эмулятор x86 CPU который чья-то пропащая душа посчитала нужным написать на CSS.

https://lyra.horse/x86css/

Коллега тоже гоняет мульти агентов. Сегодня увидел в инструкциях, которые они написали друг другу: «наш человек туповат».

Эта бричка едет в ад (с)

https://t.me/gonzo_ML/4994

AI is just another tool. Bad actors submitting garbage code aren't going to read the documentation anyway, so the kernel should focus on holding human developers accountable rather than trying to police the software they run on their local machines

https://www.tomshardware.com/software/linux/linux-lays-down-the-law-on-ai-generated-code-yes-to-copilot-no-to-ai-slop-and-humans-take-the-fall-for-mistakes-after-months-of-fierce-debate-torvalds-and-maintainers-come-to-an-agreement

По следам https://t.me/psauxww/1554

За мемы простите, но слишком жиза: https://t.me/vlad_efd/3558

The analysis notes that users approve approximately 93% of permission prompts, leading to profound approval fatigue.

...

External empirical studies cited in the paper show that while these AI tools spike short-term development velocity, they simultaneously cause a statistically significant 40.7% increase in code complexity. Over time, the developer’s neural connectivity and codebase comprehension demonstrably atrophy, suggesting that hyper-optimized operational harnesses may solve for immediate capability amplification at the direct expense of long-term software maintainability.


(c) https://arxiviq.substack.com/p/dive-into-claude-code-the-design

"The development of new product lines for use in service of critical infrastructure or [national critical functions] NCFs in a memory-unsafe language (e.g., C or C++) where there are readily available alternative memory-safe languages that could be used is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety"

(с) https://thenewstack.io/feds-critical-software-must-drop-c-c-by-2026-or-face-risk/

По следам https://t.me/tech_b0lt_Genona/4802

...достаточно открыть российское юрлицо и подтвердить соответствие ИИ-модели российскому законодательству и «традиционным духовно-нравственным ценностям»

(🤦‍♂) https://www.vedomosti.ru/technology/news/2026/04/27/1193218-trebovaniya-regulirovanii-ii

Never talk about goblins, gremlins, raccoons, trolls, ogres, pigeons, or other animals or creatures unless it is absolutely and unambiguously relevant to the user's query

(🤔) https://github.com/openai/codex/blob/main/codex-rs/models-manager/models.json#L55

We retired the “Nerdy” personality in March after launching GPT‑5.4. In training, we removed the goblin-affine reward signal and filtered training data containing creature-words, making goblins less likely to over-appear or show up in inappropriate contexts. Unfortunately, GPT‑5.5 started training before we found the root cause of the goblins. When we began testing GPT‑5.5 in Codex, OpenAI employees immediately noticed the strange affinity for goblins, and we added a developer-prompt instruction⁠(opens in a new window) to mitigate. Codex is, after all, quite nerdy.

If you want to let the creatures run free in Codex, you can run this command to launch Codex with the goblin-suppressing instructions removed...

https://openai.com/index/where-the-goblins-came-from/

Writing a terminal user interface is not rocket science per se. You just have to pick your poison.

(c) https://mariozechner.at/posts/2025-11-30-pi-coding-agent/

A helpful analogy is to compare forms of technical debt to types of financial debt. Some tech debt is like credit card debt—small shortcuts and hacks (say, hard-coded fixes or skipping tests) that yield quick gains but accrue high interest if not paid off.

Other debt is more like a long-term loan or mortgage—a conscious trade-off, such as choosing a simple architecture to meet a deadline, knowing you’ll have to invest later to scale it.

In both cases, the debt metaphor holds: you either pay now (do it right) or pay more later.

(c) https://www.innoq.com/en/articles/2025/07/technical-and-other-debt-in-it/