They can see the policy working...
-
My eye just twitched
Move over vibe coding, we vibe reviewing now
-
This. Commenting out code is bad practice
In general, I'm with you
But sometimes I need to revert/comment out a code block, because another code part isn't finished/working as it should.
Sure, it clutters code, but if I just comment out a function call and temporarily replace it with the workaround, it should imho stay in code.Else the workaround will stay forever and the commented out code will act as a reminder, that this part isn't clean yet.
But maybe it really is a case by case thing, where sometimes it's better to branch it out for later merge - although that can get really messy, while having the future implementation commented out, others will also see, how it is supposed to work and don't try to further extend the workaround, which makes future merging hell
Out of interest, how would your best practice look in such cases?
-
Hum... Ignore linter advice for code that you temporarily mangled.
It's not like you have to act upon it as soon as a blue line appears under your code.
Depending on the configuration, a linter may cause the compilation or a CI pipeline to fail.
-
The duality of Programmer Humor: You get posts complaining about bloat, and posts complaining about this.
Competent people vs incompetent people.
-
The duality of Programmer Humor: You get posts complaining about bloat, and posts complaining about this.
-
Depending on the configuration, a linter may cause the compilation or a CI pipeline to fail.
Failing your local compilation due to linter problems is just stupid.
Sending "temporary" changes into your CI pipeline isn't even stupid, it's borderline malicious.
-
In general, I'm with you
But sometimes I need to revert/comment out a code block, because another code part isn't finished/working as it should.
Sure, it clutters code, but if I just comment out a function call and temporarily replace it with the workaround, it should imho stay in code.Else the workaround will stay forever and the commented out code will act as a reminder, that this part isn't clean yet.
But maybe it really is a case by case thing, where sometimes it's better to branch it out for later merge - although that can get really messy, while having the future implementation commented out, others will also see, how it is supposed to work and don't try to further extend the workaround, which makes future merging hell
Out of interest, how would your best practice look in such cases?
wrote on last edited by [email protected]I would make it a TODO so that it's clearly temporary and so the linter bugs me about it until the intended permanent code is restored.
In general I prefer to keep separate branches and maybe a draft PR open for visibility for that kind of situation, though.
-
Hot take: Clean up your darn imports. Otherwise you just make the links between modules confusing and messy.
Sounds like a perfectly normal take.
-
Failing your local compilation due to linter problems is just stupid.
Sending "temporary" changes into your CI pipeline isn't even stupid, it's borderline malicious.
Sending “temporary” changes into your CI pipeline isn’t even stupid, it’s borderline malicious.
No? “Hey customer, I’ve deployed the changes you requested to the staging area. Is this what you had in mind? Keep in mind it only looks good and isn’t fully functional yet.”
-
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.I might get physical in that sitiation. And I'm very tame.
-
Move over vibe coding, we vibe reviewing now
wrote on last edited by [email protected]Copilot does do reviews in Github now. And they're decent actually, in my experience.
-
This post did not contain any content.
The Trade Federation greatly appreciates useful imports.
-
Sounds like a perfectly normal take.
Really, OP might have had the hot one with "unnecessary imports sitting around are fine".
-
Move over vibe coding, we vibe reviewing now
Yeah code rabbit does a decent job of pointing out things you may have missed.
-
Really, OP might have had the hot one with "unnecessary imports sitting around are fine".
...if only that were the case.
-
Move over vibe coding, we vibe reviewing now
wrote on last edited by [email protected]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?
-
Competent people vs incompetent people.
Also, slightly less competent ppl vs slightly more competent ppl.
-
This. Commenting out code is bad practice
wrote on last edited by [email protected]Yeah, I stopped using comments as a code ON/OFF switch when I started using
git.
But then I handed over my project to someone without OCD and now the repo is full of code inside comments.
And because I don't use
git stashproperly enough, in some projects, my stash is 3+ stacks long, with almost the same changes in each of the stashed entries. -
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?
