A hinting engine for the web
https://github.com/webhintio/hint
#1ospd #opensource #a11y #bestpractices #hacktoberfest #hint #hints #interoperability #lint #performance #pwa #pwas #security #securityscanner #webhint
Как заставить Android Studio ругаться на код по вашим правилам: создаем пользовательские Lint и Detekt
Привет, Хабр! На связи Алина, старший Android-разработчик в команде Инвестиций «Совкомбанк Технологии». Сегодня поговорим о том, как заставить Android Studio самостоятельно следить за порядком в коде – без ручных проверок и без вечных напоминаний в командном чате. В этой статье мы создадим практические правила для инструментов статического анализа кода и разберем, как внедрить их в проект. На примере lint рассмотрим контроль архитектуры пакетов и обязательную документацию с QuickFix, а на примере detekt – проверку неизменяемого состояния представления без Android-зависимостей и миграцию с RxJava на Coroutines.
https://habr.com/ru/companies/sovcombank_technologies/articles/1005922/
#Lint #Detekt #Android #QuickFix #Анализ_кода #Правила #Kotlin #Java #Suppress #Тесты

Привет, Хабр! На связи Алина, старший Android-разработчик в команде Инвестиций «Совкомбанк Технологии». Сегодня поговорим о том, как заставить Android Studio самостоятельно следить за порядком в коде...
BOOTOSHI (@KingBootoshi)
Opus에 대한 불만을 표한 트윗으로, 새 코드베이스와 guardrails 환경(클린 컨텍스트)에서 Opus가 정답성 높은 수정 제안을 한 뒤 곧바로 lint ignore를 삽입하는 이상 동작을 보였다고 보고합니다. 작성자는 'Opus 4.6' 출시 당일 버전과 비교하며 이전 수준과 달라졌다는 실망을 표현하고 있습니다.

LMFAOOO I'M DONE WITH OPUS BRO THIS IS WITH CLEAN CONTEXT ON A NEW CODEBASE + GUARDRAILS IT LITERALLY WROTE THE CORRECT SOLUTIONS TO FIX THE LINT AND THEN ADDED LINT IGNORE RIGHT AFTER ANYWAYS WHAT HAPPENED TO MY BOY? OPUS 4.6 ON RELEASE DAY WOULD NEVER DO THIS 😭😭😭
LLMs are Lint
No, I don’t mean that are bits of clothing fluff, I mean they’re like the old “lint” program for C.
In those days, there wasn’t enough memory to load the parser and the error messages at the same time. So the messages were shifted to a different program, lint, which did lexical analysis and then dumped the result into a semantic analysis phase.
That mean that lint was reporting on what it thought the program meant, rather than on places where the C compiler failed. That, in turn, meant it was wrong a lot (:-)) So the authors added comments like /* NOTREACHED */ which would tell lint to ignore things. I soon got used to carefully analyzing the messages, and shutting the bogus ones off with suppressions.
Surprise, It’s the Same with LLMs
I often get message like this:
I apologize for my previous error. The article I mentioned earlier was not a real, verifiable source. I should not have presented fictional information as if it were factual. This was a mistake on my part.In reality, I cannot find an actual City News article from January 15, 2026, with the details I previously claimed. The information I provided was fabricated, which goes against my core principle of providing accurate and truthful information.So I do three things:
This sounds hard, but it’s easy if you set your expectations correctly. For example, the name I gave to my LLM is “Lyin’ Brian”, after Brian Mulrony, a Canadian PM who seem to have some “doubtful associations” in his career, like https://en.wikipedia.org/wiki/Karlheinz_Schreiber
The suppressions do the heavy lifting. Checking URLs often gets done as a side-effect, when I go to read the thing the link points to.
#ai #c #lint #llmRheinRuhrBahn setzt LINT-41-Fahrzeuge wegen technischer Mängel außer Betrieb
#Düsseldorf #Kleve #Krefeld #Lint #Mängel #RheinRuhrBahn #Werkstatt

Commit messages matter. Yet many of us still toss out a “fix stuff” or “wip” when we’re moving fast. Maybe you let an AI agent vibe‑commit whatever it feels like. That’s totally fine in test branches, where you can clean them up later, but not in the main branch. The effort to write a good commit message is the same as writing a bad one. Although, the difference shows up six months later when you dig through the git logs and the messages don’t give a clear picture of what happened.
This is a gorgeous scene. Dashboard notebook, IPS LED panel left and super wide IPS LED panel full left
The SBC is lit up by the second panel