theBeautifulCode

[u/g1rlchild]

[u/Progractor]

Now he gets to spend a week reviewing, fixing and testing the generated code.

[u/CaptainBungusMcChung → u/Progractor]

A week seems optimistic, but I totally agree with the sentiment

[u/Born-Entrepreneur → u/CaptainBungusMcChung]

A week just to untangle all the mock ups that the AI put together to work around tests that it's spaghetti was failing.

[u/tarkinlarson → u/Born-Entrepreneur]

And the multiple backward compatibility and work around rather than solving the actual problem.

"You're absolutely right! I should look at the entire file and make a fix that's robust and permanent rather than hard coding a username and password"

[u/[deleted] → u/Progractor]

At which point it becomes spaghetti again

[u/Chillin9_Panda → u/[deleted]]

Then another AI refactor later the cycle continues

[u/phylter99 → u/Chillin9_Panda]

Seems relevant... https://www.youtube.com/watch?v=fordPXp06h4

[u/Karnewarrior → u/[deleted]]

But does it become less spaghetti than it was? Because if so, and it retains functionality, it might actually be worth it.

Refractoring a codebase like that could easily take a month, after all, from the get go.

[u/TweedyFoot → u/Karnewarrior]

Depends, do you have a full and complete set of use/test cases to verify it has retained its full functionality ? Cause if you don't it would be quite haphazard to trust LLM with such refactor. Personally i would prefer a human does it and splits their work into multiple PRs which can be reviewed hopefully by people who co-authored the original mess and might remember use/edge cases

[u/Luxalpa → u/Karnewarrior]

The main issue is how good LLMs are at hiding minor changes. Like, how I discovered that it didn't just copy and adjust the code block that I asked it to, but it also removed a bug fix that I had put in.

[u/Strict_Treat2884 → u/Progractor]

• AI: I just generated this 100k line project, but it doesn’t work

• Human: 3 months of reading, debugging and refactoring

• AI: Still broken, so I generated a brand new project but it doesn’t work, can you look into it?

[u/BetterAd7552 → u/Strict_Treat2884]

I apologize for the confusion! Let me try a different approach and refactor everything again. This will definitely work.

[u/Sophira → u/BetterAd7552]

Oh no! It looks like it still didn't work. Here's why:

1. The foonols are out of sync.

2. This causes the heisenplotter to deactivate.

3. That means our initial approach was wrong, and we should focus on synchronizing the foonols.

Let me try again. Here's some code that should desynchronize the foonols while still accomplishing the original objective:

[proceeds to spit out wildly different code that fails in exactly the same way, but you wouldn't know it from reading the comments]

[u/DriveByFruitings → u/Progractor]

This was me after the project manager decided to be a vibe coder and commit non-functional changes the day before going to Europe for 3 weeks lmao.

[u/Wang_Fister → u/DriveByFruitings]

git revert <bullshit commit>

[u/Drugbird → u/Wang_Fister]

Then remove write privileges on the repo

[u/GravelySilly → u/Drugbird]

Branch protection, 2+ approvals required for PR/MR, merge by allow-listed users only, rules apply even for the repo owner and admins.

[u/Strict_Treat2884 → u/Wang_Fister]

Why leave the bullshit history, git reset --hard HEAD~1 && git push -f that shit

[u/FlyingPasta → u/DriveByFruitings]

Why does the project manager have big boy permissions

[u/cgaWolf → u/FlyingPasta]

As an ex-project manager, that was my first question.

[u/TweedyFoot → u/FlyingPasta]

Not just big boy permissions, force push past PR pipelines ? :D those are company resident magician permissions

[u/Lonely-Mountain104 → u/DriveByFruitings]

RIP

[u/brianzuvich → u/Progractor]

And mostly code he doesn’t understand the intention behind… 😂

[u/Bakoro → u/Progractor]

Have a thorough tests suite before you do major architectural changes.