EVERY programmer needs this tool 👩‍💻 #programming #tech #code #technology #software #developer

[CodingWithLewis]

Luckily for me, I don’t need AI to write bad code 😎

[J.Crime]

Ths sad thing is that Something like this is needed as some companies evaluate you not by the quality of your work but by how much you have written, no matter if good or not.

[rammrras]

This has been trained with my codebase and libraries 🤣😭

[MarkBelain]

I actually love the idea of this, because having a de facto example of bad code can help people raise the bar.
Imagine running this on someone’s code you know to be good only to look at the spaghetti and think, “now it looks like my code.”

I’m a private setting, this could be such a good wakeup call. And healthy reminders of what not to do or even what needs a most immediate fix.

[alliesteele]

Doing this right before quitting is elite

[dffab]

overly descriptive variable names are actually a good thing. They keep it cognitively easy to read the code, less strain on work memory

[ValidT]

This actually sounds like a really good way of learning.

[asero.]

> introduce a random bug

Ok, now AI really is replacing us all 😅

[metalcrusher]

I dont need this tool to write bad code😎

[flordelphinta]

Riot needs this so that the program will realize that un-spaghettifying the code is the only way to troll Riot.

[felipeferreira]

All my code goes through 3 to 4 rounds of review. And I don’t get paid for lines of code and my team mates appreciate easy to read and understand code. Minimum comments is best

[lynda]

Now we need this for emails and essays

[gabrielpelegrini]

The random bug might be useful for interns/begginers to practice debugging i guess

[anarkhos]

Careful though, an experienced lead dev will quickly get to you through your commits, since lead devs often are responsible for the quality of code they'll have to do something about it.

[Sjoerd]

Honestly I'm usually more annoyed by overly shortened variable names than overly descriptive ones.

There should be a balance, but being a little more verbose actually helps code readability in many cases.

[lunalildragon]

when you get paid per line of code you should put comments in between every line, if possible even split up lines.

[DerRumo]

I would write my code, run this tool and then hand it in as the solution.
Then I can get paid another time for improving the code when I hand in the ubchanged version.

[tahaak]

Instructions unclear: AI destroyed itself because the code it generated was better than mine

[DrachenKaiser]

You dont need a tool if you have the right people.

[cf-unicorn]

okay so this might be a dumb question, but I'm genuinely curious
are there actually people who get paid based on how many lines of code they've written?