Too high a focus on formatting linting (though python where whitespace is meaningful, so perhaps this makes sense) compared with linting rules that capture valuable problems. In many languages format lints are solved by running a formatter (rustfmt, gofmt, pretier, etc.). I absolutely love rust’s clippy lint and what it does to quality of my code and find the defaults are often pretty good and improve over time.
I’m curious to understand, as more and more tooling for code quality is written in Rust, how the Rust ecosystem thinks about its own tooling. I worked previously at SurrealDB and we have invested a lot in building own tools and OSSing it.
Why is it so obvious when something is at least mostly written by (or expanded/rewritten by) AI?
Disclaimer: I get it; some of you out there are Linters’ biggest fans, almost like they’re your favorite band. But to be clear, this is my humble opinion, not a call to arms! So, if you’re feeling feisty about your lint-enthusiasm, remember, it’s all in good fun!
Thanks for saying this. I should not have used Grammarly, believing more prose would deliver more meaning. I’m being too silly.
It is not just settings; just like code review, lint rules should be discussed with the team. And in software with multiple programming language modules – the complexity increases collaboration and agreement wise.
In my whole work experience, the only people I met who write code and do not like linters were data scientitst (and only a few of them). The premise of this article feels unfunded to me.
Right, and thanks for reading. I have met many who like ESLint but are disappointed with the results. I understand that you can reap so many benefits with the right sort of rules and time spent.
As I elucidated in the article, one needs to look from a team perspective, too, not configure it too strictly, etc.
I hate it that when it comes about Bluesky I always seem to be that guy, but we (or at least I) did it first using ActivityPub. This is a website that is composed out of ActivityPub objects: https://releases.bruta.link/outbox
There is of course some glue code that builds the web components from the json content, but all the interactions are done through ActivityPub.
This service is not yet plugged into the vaster fediverse yet (ie, it does not accept follows from random accounts), so if you’re looking for a way to get notices about new metal releases, it has a little brother as a mastodon bot at @releasebot@metalhead.club.
Continue building a flappy bird game using 3js and Cursor. Want to build this one for ever!
I saw a bunch of these. Mostly named as Ai commit, but I believe now VSCode itself offers it by default.
Fun part sometimes it apologizes.
Too high a focus on formatting linting (though python where whitespace is meaningful, so perhaps this makes sense) compared with linting rules that capture valuable problems. In many languages format lints are solved by running a formatter (rustfmt, gofmt, pretier, etc.). I absolutely love rust’s clippy lint and what it does to quality of my code and find the defaults are often pretty good and improve over time.
I’m curious to understand, as more and more tooling for code quality is written in Rust, how the Rust ecosystem thinks about its own tooling. I worked previously at SurrealDB and we have invested a lot in building own tools and OSSing it.
Why is it so obvious when something is at least mostly written by (or expanded/rewritten by) AI?
Just yikes.
Not a native english speaker. I use Grammarly, and yes I agree it is killing the tone. Making it look terrible.
You can check my other blogs here https://aravind.dev/layoff/
Good developers love linters. They might just disagree on what settings to use ;)
Thanks for saying this. I should not have used Grammarly, believing more prose would deliver more meaning. I’m being too silly.
It is not just settings; just like code review, lint rules should be discussed with the team. And in software with multiple programming language modules – the complexity increases collaboration and agreement wise.
In my whole work experience, the only people I met who write code and do not like linters were data scientitst (and only a few of them). The premise of this article feels unfunded to me.
Right, and thanks for reading. I have met many who like ESLint but are disappointed with the results. I understand that you can reap so many benefits with the right sort of rules and time spent.
As I elucidated in the article, one needs to look from a team perspective, too, not configure it too strictly, etc.
I hate it that when it comes about Bluesky I always seem to be that guy, but we (or at least I) did it first using ActivityPub. This is a website that is composed out of ActivityPub objects: https://releases.bruta.link/outbox
There is of course some glue code that builds the web components from the json content, but all the interactions are done through ActivityPub.
Thanks for sharing this.
This service is not yet plugged into the vaster fediverse yet (ie, it does not accept follows from random accounts), so if you’re looking for a way to get notices about new metal releases, it has a little brother as a mastodon bot at @releasebot@metalhead.club.
Pretty interesting read.