#lint — Public Fediverse posts

In today's round of merely passing on Polish rail industry news…

Poles will soon be able to ~~enjoy~~ suffer from the infamous LINT diesel units - the first one imported from the West by Polregio has received the company livery: https://www.rynek-kolejowy.pl/wiadomosci/pierwszy-z-lintow-juz-w-barwach-polregio-152876.html

#kolej #rail #LINT #Polregio

In today's round of merely passing on Polish rail industry news…

Poles will soon be able to ~~enjoy~~ suffer from the infamous LINT diesel units - the first one imported from the West by Polregio has received the company livery: https://www.rynek-kolejowy.pl/wiadomosci/pierwszy-z-lintow-juz-w-barwach-polregio-152876.html

#kolej #rail #LINT #Polregio

In today's round of merely passing on Polish rail industry news…

Poles will soon be able to ~~enjoy~~ suffer from the infamous LINT diesel units - the first one imported from the West by Polregio has received the company livery: https://www.rynek-kolejowy.pl/wiadomosci/pierwszy-z-lintow-juz-w-barwach-polregio-152876.html

#kolej #rail #LINT #Polregio

In today's round of merely passing on Polish rail industry news…

Poles will soon be able to ~~enjoy~~ suffer from the infamous LINT diesel units - the first one imported from the West by Polregio has received the company livery: https://www.rynek-kolejowy.pl/wiadomosci/pierwszy-z-lintow-juz-w-barwach-polregio-152876.html

#kolej #rail #LINT #Polregio

In today's round of merely passing on Polish rail industry news…

Poles will soon be able to ~~enjoy~~ suffer from the infamous LINT diesel units - the first one imported from the West by Polregio has received the company livery: https://www.rynek-kolejowy.pl/wiadomosci/pierwszy-z-lintow-juz-w-barwach-polregio-152876.html

#kolej #rail #LINT #Polregio

Линт проектов: собираем ESLint, Prettier и Stylelint в один пакет

В большинстве компаний линтинг со временем превращается в хаос: разные правила ESLint, устаревшие конфиги и копипаста между проектами. Покажу, как навести порядок – собрать линт-инфраструктуру в один пакет и выстроить систему контроля кода для всех репозиториев.

https://habr.com/ru/articles/1038340/

#eslint #prettier #линтинг_кода #stylelint #husky #lint #javascript #typescript #react #madge

Линт проектов: собираем ESLint, Prettier и Stylelint в один пакет

В большинстве компаний линтинг со временем превращается в хаос: разные правила ESLint, устаревшие конфиги и копипаста между проектами. Покажу, как навести порядок – собрать линт-инфраструктуру в один пакет и выстроить систему контроля кода для всех репозиториев.

https://habr.com/ru/articles/1038340/

#eslint #prettier #линтинг_кода #stylelint #husky #lint #javascript #typescript #react #madge

Линт проектов: собираем ESLint, Prettier и Stylelint в один пакет

В большинстве компаний линтинг со временем превращается в хаос: разные правила ESLint, устаревшие конфиги и копипаста между проектами. Покажу, как навести порядок – собрать линт-инфраструктуру в один пакет и выстроить систему контроля кода для всех репозиториев.

https://habr.com/ru/articles/1038340/

#eslint #prettier #линтинг_кода #stylelint #husky #lint #javascript #typescript #react #madge

Линт проектов: собираем ESLint, Prettier и Stylelint в один пакет

В большинстве компаний линтинг со временем превращается в хаос: разные правила ESLint, устаревшие конфиги и копипаста между проектами. Покажу, как навести порядок – собрать линт-инфраструктуру в один пакет и выстроить систему контроля кода для всех репозиториев.

https://habr.com/ru/articles/1038340/

#eslint #prettier #линтинг_кода #stylelint #husky #lint #javascript #typescript #react #madge

War eher meh btw.

Motor natürlich flüsterleise, aber alles andere irgendwie ..nicht.

Ich weiß nicht, ob das einfach nur an der Strecke lag (war gefühlt auch fast eher so ein Gütergleis?), aber es war sehr ruckelig und die Fahrgestelle haben dementsprechend geklungen. Like, deutlich wackeliger als ein #Itino.
Zusätzlich auch konstant Resonanzen in den Heizkörpern, die mit den Mülleimern einer #BR425 mithalten können..

Die #LINT​s von der #VIAS sind da um einiges bequemer – trotz Dieselmotoren.

War eher meh btw.

Motor natürlich flüsterleise, aber alles andere irgendwie ..nicht.

Ich weiß nicht, ob das einfach nur an der Strecke lag (war gefühlt auch fast eher so ein Gütergleis?), aber es war sehr ruckelig und die Fahrgestelle haben dementsprechend geklungen. Like, deutlich wackeliger als ein #Itino.
Zusätzlich auch konstant Resonanzen in den Heizkörpern, die mit den Mülleimern einer #BR425 mithalten können..

Die #LINT​s von der #VIAS sind da um einiges bequemer – trotz Dieselmotoren.

War eher meh btw.

Motor natürlich flüsterleise, aber alles andere irgendwie ..nicht.

Ich weiß nicht, ob das einfach nur an der Strecke lag (war gefühlt auch fast eher so ein Gütergleis?), aber es war sehr ruckelig und die Fahrgestelle haben dementsprechend geklungen. Like, deutlich wackeliger als ein #Itino.
Zusätzlich auch konstant Resonanzen in den Heizkörpern, die mit den Mülleimern einer #BR425 mithalten können..

Die #LINT​s von der #VIAS sind da um einiges bequemer – trotz Dieselmotoren.

War eher meh btw.

Motor natürlich flüsterleise, aber alles andere irgendwie ..nicht.

Ich weiß nicht, ob das einfach nur an der Strecke lag (war gefühlt auch fast eher so ein Gütergleis?), aber es war sehr ruckelig und die Fahrgestelle haben dementsprechend geklungen. Like, deutlich wackeliger als ein #Itino.
Zusätzlich auch konstant Resonanzen in den Heizkörpern, die mit den Mülleimern einer #BR425 mithalten können..

Die #LINT​s von der #VIAS sind da um einiges bequemer – trotz Dieselmotoren.

Nifty.
Looks like rumdl support for Markdown linting has just been added to Vim's ALE plugin.

https://github.com/dense-analysis/ale/commit/c59c0d1a573a7b2fe491f78af4f2033bde454753

#Vim #VimPlugin #Lint #Markdown #rumdl

Nifty.
Looks like rumdl support for Markdown linting has just been added to Vim's ALE plugin.

https://github.com/dense-analysis/ale/commit/c59c0d1a573a7b2fe491f78af4f2033bde454753

#Vim #VimPlugin #Lint #Markdown #rumdl

Nifty.
Looks like rumdl support for Markdown linting has just been added to Vim's ALE plugin.

https://github.com/dense-analysis/ale/commit/c59c0d1a573a7b2fe491f78af4f2033bde454753

#Vim #VimPlugin #Lint #Markdown #rumdl

Nifty.
Looks like rumdl support for Markdown linting has just been added to Vim's ALE plugin.

https://github.com/dense-analysis/ale/commit/c59c0d1a573a7b2fe491f78af4f2033bde454753

#Vim #VimPlugin #Lint #Markdown #rumdl

Nifty.
Looks like rumdl support for Markdown linting has just been added to Vim's ALE plugin.

https://github.com/dense-analysis/ale/commit/c59c0d1a573a7b2fe491f78af4f2033bde454753

#Vim #VimPlugin #Lint #Markdown #rumdl

One Open-source Project Daily

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

One Open-source Project Daily

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

One Open-source Project Daily

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

One Open-source Project Daily

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

One Open-source Project Daily

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 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 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 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 #Тесты

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:

• Add suppressions to my defaults, like “don’t tell me about Oxford commas”
• check absolutely everything that doesn’t come with a URL
• and check the URLS, too.

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.

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:

• Add suppressions to my defaults, like “don’t tell me about Oxford commas”
• check absolutely everything that doesn’t come with a URL
• and check the URLS, too.

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.

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:

• Add suppressions to my defaults, like “don’t tell me about Oxford commas”
• check absolutely everything that doesn’t come with a URL
• and check the URLS, too.

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.

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:

• Add suppressions to my defaults, like “don’t tell me about Oxford commas”
• check absolutely everything that doesn’t come with a URL
• and check the URLS, too.

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.

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:

• Add suppressions to my defaults, like “don’t tell me about Oxford commas”
• check absolutely everything that doesn’t come with a URL
• and check the URLS, too.

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.

RheinRuhrBahn setzt LINT-41-Fahrzeuge wegen technischer Mängel außer Betrieb

#Düsseldorf #Kleve #Krefeld #Lint #Mängel #RheinRuhrBahn #Werkstatt

https://bahnblogstelle.com/247225/rheinruhrbahn-setzt-lint-41-fahrzeuge-wegen-technischer-maengel-ausser-betrieb/

RheinRuhrBahn setzt LINT-41-Fahrzeuge wegen technischer Mängel außer Betrieb

#Düsseldorf #Kleve #Krefeld #Lint #Mängel #RheinRuhrBahn #Werkstatt

https://bahnblogstelle.com/247225/rheinruhrbahn-setzt-lint-41-fahrzeuge-wegen-technischer-maengel-ausser-betrieb/

RheinRuhrBahn setzt LINT-41-Fahrzeuge wegen technischer Mängel außer Betrieb

#Düsseldorf #Kleve #Krefeld #Lint #Mängel #RheinRuhrBahn #Werkstatt

https://bahnblogstelle.com/247225/rheinruhrbahn-setzt-lint-41-fahrzeuge-wegen-technischer-maengel-ausser-betrieb/

RheinRuhrBahn setzt LINT-41-Fahrzeuge wegen technischer Mängel außer Betrieb

#Düsseldorf #Kleve #Krefeld #Lint #Mängel #RheinRuhrBahn #Werkstatt

https://bahnblogstelle.com/247225/rheinruhrbahn-setzt-lint-41-fahrzeuge-wegen-technischer-maengel-ausser-betrieb/

RheinRuhrBahn setzt LINT-41-Fahrzeuge wegen technischer Mängel außer Betrieb

#Düsseldorf #Kleve #Krefeld #Lint #Mängel #RheinRuhrBahn #Werkstatt

https://bahnblogstelle.com/247225/rheinruhrbahn-setzt-lint-41-fahrzeuge-wegen-technischer-maengel-ausser-betrieb/

Friday #FOSS release - Gommitlint - linting tool for commits - CLI and CI, written in Go.https://itiquette.codeberg.page/posts/gommitlint-release/ #opensource #cli #ci #git #commit #lint

a report on using web based LLMs for fluffy stuff...
> I'd estimate my direct use of ChatGPT at 2-6 hrs, 3-4 days a week ... therefore, most ChatGPT users spend much less time on it. https://write.as/3gmbckphg4wjpwj4.md

#LLMs #ChatGPT #ChatGPT5 #Claude #Lint

a report on using web based LLMs for fluffy stuff...
> I'd estimate my direct use of ChatGPT at 2-6 hrs, 3-4 days a week ... therefore, most ChatGPT users spend much less time on it. https://write.as/3gmbckphg4wjpwj4.md

#LLMs #ChatGPT #ChatGPT5 #Claude #Lint

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

#Hardware #lint #cable #snapped #technology #RetroComputing

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

#Hardware #lint #cable #snapped #technology #RetroComputing

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

#Hardware #lint #cable #snapped #technology #RetroComputing

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

#Hardware #lint #cable #snapped #technology #RetroComputing

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

#Hardware #lint #cable #snapped #technology #RetroComputing

Another last photograph of dashboard notebook.
Rest in peace

#Hardware #lint #cable #snapped #technology #RetroComputing

Another last photograph of dashboard notebook.
Rest in peace

#Hardware #lint #cable #snapped #technology #RetroComputing

Another last photograph of dashboard notebook.
Rest in peace

#Hardware #lint #cable #snapped #technology #RetroComputing

Another last photograph of dashboard notebook.
Rest in peace

#Hardware #lint #cable #snapped #technology #RetroComputing

Another last photograph of dashboard notebook.
Rest in peace

#Hardware #lint #cable #snapped #technology #RetroComputing