Oh shit the replies afe even better. This is... yeah lol no. Not sure why anyone would willingly risk turning their game's codebase into what these folks are describing.
November 8, 2026 at 9:48 PM
Oh shit the replies afe even better. This is... yeah lol no. Not sure why anyone would willingly risk turning their game's codebase into what these folks are describing.
Refactor this entire codebase. Make no mistakes
November 8, 2026 at 11:31 PM
Refactor this entire codebase. Make no mistakes
I feel like I’ve been warning about this for ages.
November 8, 2026 at 1:21 PM
I feel like I’ve been warning about this for ages.
love how every big software company is staffed with developers who don't understand the codebase. i'm sure this won't have any consequences down the line
November 10, 2026 at 9:31 AM
love how every big software company is staffed with developers who don't understand the codebase. i'm sure this won't have any consequences down the line
it usually takes new hires a while to understand the codebase. imagine if every programmer at the company was a new higher every day forever
November 8, 2026 at 10:20 PM
it usually takes new hires a while to understand the codebase. imagine if every programmer at the company was a new higher every day forever
honest to god i’d happily get claude to boil the atlantic away before i’d dare go spelunking in the unity codebase
what a complete and utter engineering failure on unity's part holy fucking shit
November 10, 2026 at 8:05 AM
honest to god i’d happily get claude to boil the atlantic away before i’d dare go spelunking in the unity codebase
Jeez someone emailed me about if I had a clean copy of a mud codebase because I am notoriously one of the few who was ever granted permission to create a recognized derivative. It occurs to me that the original creator of the codebase was much older than me and might actually be deceased by now.
November 10, 2026 at 7:44 AM
Jeez someone emailed me about if I had a clean copy of a mud codebase because I am notoriously one of the few who was ever granted permission to create a recognized derivative. It occurs to me that the original creator of the codebase was much older than me and might actually be deceased by now.
yeah the vicious cycle is that llms overengineer shit and make huge commits. this then increases the amount of code in the codebase. repeat this over time and this larger codebase takes up more and more of the context window until it can't be kept in anymore. errors build, the codebase is spaghetti
November 9, 2026 at 4:34 AM
yeah the vicious cycle is that llms overengineer shit and make huge commits. this then increases the amount of code in the codebase. repeat this over time and this larger codebase takes up more and more of the context window until it can't be kept in anymore. errors build, the codebase is spaghetti
ten lines of code in the codebase of an entire modern game == diarrhea lettuce in burger. got it!
November 10, 2026 at 8:47 AM
ten lines of code in the codebase of an entire modern game == diarrhea lettuce in burger. got it!
like imagine if 1/100th of the investment in "AI" was just put into a really good codebase visualizer 😭
November 10, 2026 at 12:25 AM
like imagine if 1/100th of the investment in "AI" was just put into a really good codebase visualizer 😭
Hey cool, I DIDN'T get fired showing how the client's AI blew up the codebase even though they were the ones that forced my team to use it.
Hazbin Hotel Charlie
ALT: Hazbin Hotel Charlie
static.klipy.com
November 9, 2026 at 4:28 PM
Hey cool, I DIDN'T get fired showing how the client's AI blew up the codebase even though they were the ones that forced my team to use it.
Sorry, but our codebase is now more secure, has far fewer bugs, is better monitored, and has less duplication of concerns.
*And* is better documented.
Git gud?
*And* is better documented.
Git gud?
November 9, 2026 at 3:58 AM
Sorry, but our codebase is now more secure, has far fewer bugs, is better monitored, and has less duplication of concerns.
*And* is better documented.
Git gud?
*And* is better documented.
Git gud?
"slop creep"
agents pick at insignificant things, cover too many edge cases, and miss existing functionality. over time, that bloats the codebase and makes everything more complex.
many times i've asked claude "do you really need to do that?" and the answer (in the form of a wall of text) is "no"
agents pick at insignificant things, cover too many edge cases, and miss existing functionality. over time, that bloats the codebase and makes everything more complex.
many times i've asked claude "do you really need to do that?" and the answer (in the form of a wall of text) is "no"
November 7, 2026 at 12:02 PM
"slop creep"
agents pick at insignificant things, cover too many edge cases, and miss existing functionality. over time, that bloats the codebase and makes everything more complex.
many times i've asked claude "do you really need to do that?" and the answer (in the form of a wall of text) is "no"
agents pick at insignificant things, cover too many edge cases, and miss existing functionality. over time, that bloats the codebase and makes everything more complex.
many times i've asked claude "do you really need to do that?" and the answer (in the form of a wall of text) is "no"
no generative AI art, only 0.1% of the codebase, and only at the end to get the worse bugs?
this is not a debate, they should be considered for the award
this is not a debate, they should be considered for the award
November 10, 2026 at 10:59 AM
no generative AI art, only 0.1% of the codebase, and only at the end to get the worse bugs?
this is not a debate, they should be considered for the award
this is not a debate, they should be considered for the award
when I was tech lead, I knew which parts of the codebase I needed to pay careful attention to, and reviewed 100% of that. And pointed out flaws before they made it into I&T - flaws that passed automated tests but were fatal to the overall system itself.
That level is knowledge is now likely gone.
That level is knowledge is now likely gone.
November 8, 2026 at 1:41 PM
when I was tech lead, I knew which parts of the codebase I needed to pay careful attention to, and reviewed 100% of that. And pointed out flaws before they made it into I&T - flaws that passed automated tests but were fatal to the overall system itself.
That level is knowledge is now likely gone.
That level is knowledge is now likely gone.
I mean…
Good luck, I guess?
Good luck, I guess?
November 8, 2026 at 1:18 PM
I mean…
Good luck, I guess?
Good luck, I guess?
Today’s attempted decent Stirling picture of the day, the stairs on my way into Codebase Stirling where I am coworking for now.
November 5, 2026 at 12:08 PM
Today’s attempted decent Stirling picture of the day, the stairs on my way into Codebase Stirling where I am coworking for now.
I'd imagine it was the scraped codebase of someone who previously would have been hired to fix that problem
November 10, 2026 at 8:42 AM
I'd imagine it was the scraped codebase of someone who previously would have been hired to fix that problem
"how bad has the Windows 11 codebase gotten", I hear you ask
it’s mspaint. there is an RCE in mspaint
November 5, 2026 at 11:13 PM
"how bad has the Windows 11 codebase gotten", I hear you ask
I mean once management has drunk the AI Kool-Aid, anyone who tries to maintain some sanity in the codebase is just 'holding up progress' and they either get pushed out or see the handwriting on the wall and leave for someplace saner. Then the inmates are running the asylum.
November 8, 2026 at 7:26 PM
I mean once management has drunk the AI Kool-Aid, anyone who tries to maintain some sanity in the codebase is just 'holding up progress' and they either get pushed out or see the handwriting on the wall and leave for someplace saner. Then the inmates are running the asylum.
Having worked in tech, I'd say itd be closer to:
A woman speaks to you, do you:
A) tell her you're married and show her your codebase
B) show her your codebase
Was the last question written by AI?
A) Yes, upload your codebase as proof
B) No, it was written by a young woman, show her your codebase
A woman speaks to you, do you:
A) tell her you're married and show her your codebase
B) show her your codebase
Was the last question written by AI?
A) Yes, upload your codebase as proof
B) No, it was written by a young woman, show her your codebase
November 9, 2026 at 9:51 AM
Having worked in tech, I'd say itd be closer to:
A woman speaks to you, do you:
A) tell her you're married and show her your codebase
B) show her your codebase
Was the last question written by AI?
A) Yes, upload your codebase as proof
B) No, it was written by a young woman, show her your codebase
A woman speaks to you, do you:
A) tell her you're married and show her your codebase
B) show her your codebase
Was the last question written by AI?
A) Yes, upload your codebase as proof
B) No, it was written by a young woman, show her your codebase
You have to wonder how Mark Zuckerberg is spending his last few months of freedom. Maybe he’s sentimentally going through the codebase of Facesmash, or thinking about the Winklevii twins, wondering where it all went wrong.
Mark, it was when you were born. Another sad case.
Mark, it was when you were born. Another sad case.
November 8, 2026 at 6:42 PM
You have to wonder how Mark Zuckerberg is spending his last few months of freedom. Maybe he’s sentimentally going through the codebase of Facesmash, or thinking about the Winklevii twins, wondering where it all went wrong.
Mark, it was when you were born. Another sad case.
Mark, it was when you were born. Another sad case.
People in the replies split between “keep using AI to try and hold the whole mess together” and “dump the whole codebase and having AI make fresh slopcode”.
November 8, 2026 at 7:22 PM
People in the replies split between “keep using AI to try and hold the whole mess together” and “dump the whole codebase and having AI make fresh slopcode”.
You're working on a codebase that's large enough you can't be familiar with every part. How do you approach/conceptualise/navigate that?
November 10, 2026 at 4:11 AM
You're working on a codebase that's large enough you can't be familiar with every part. How do you approach/conceptualise/navigate that?
"the codebase is around 3x the size it was and nobody can explain how most of it works"
And they fired the people whose job was to look at complaints about code malfunctions.
I'm sure this business is going to go far, A+ work.
And they fired the people whose job was to look at complaints about code malfunctions.
I'm sure this business is going to go far, A+ work.
November 8, 2026 at 6:16 PM
"the codebase is around 3x the size it was and nobody can explain how most of it works"
And they fired the people whose job was to look at complaints about code malfunctions.
I'm sure this business is going to go far, A+ work.
And they fired the people whose job was to look at complaints about code malfunctions.
I'm sure this business is going to go far, A+ work.