We have linting set up in our codebase, I had to switch and focus on one half of our project, and I nearly lost my mind when I came back to the other side and realized that every time someone said they were ‘addressing linting issues’, that actually meant they were putting
eslint-disableeverywhere until the pipeline stopped complaining.Code reviews?
“It passed CI, LGTM”
My eye just twitched
Move over vibe coding, we vibe reviewing now
Next what?
Vibe marketing?
Then vibe selling and vibe buying?
Then vibe using? Because software is now made out of AI, by AI, for AI?So now, if your AI user likes the program that your AI buyer bought, it will inject some dopamine in your bloodstream, giving you the vibes, while you lay on your bed?
The developer I report to was in charge of that side of the code base and doing all the code reviews for it … I thought he had a handle on it :/
I might get physical in that sitiation. And I’m very tame.
Hot take: Clean up your darn imports. Otherwise you just make the links between modules confusing and messy.
Sounds like a perfectly normal take.
Really, OP might have had the hot one with “unnecessary imports sitting around is fine”.
The duality of Programmer Humor: You get posts complaining about bloat, and posts complaining about this.
Competent people vs incompetent people.
Also, slightly less competent ppl vs slightly more competent ppl.
- Case 1:
- Just typed the ending ‘>’ for the include and see the annotation come up.
- Case 2:
- Did not include the header, so not getting the code completion recommendation, making me have to type the function/class/whatever name.
- Case 3:
- The code completion comes up with an option of including the header (except that it is including the wrong header, despite me having already included the correct one)
- Case 1:
