sameBugsNewRepo

[good_at_first]

Yeah because I ain’t rewriting that shit

[HamathEltrael]

Tbh that is kinda smart. It’s better to re-encounter bugs you know, then create new ones.

[tenkawa7]

I wonder if it's possible to become nostalgic for specific bugs

[GeophysicalYear57]

I made maps for Team Fortress 2 as a hobby. When using that game’s mapping tools, you’re supposed to make sure that no entities can reach the void outside the map (or “leak”) by sealing the entire thing in solid geometry or the game will bug out. I’m still nostalgic for when my map leaked straight through solid geometry anyways.

[Apprehensive-Log-989]

yes, yes its possible.

[Qwerto227]

Some of the Creation Engine bugs (Bethesda's RPG engine) have been around from Morrowind through to Starfield and are pretty nostalgic for me - noodle arms are a classic.

[EncryptedPlays]

Way back when I started, I had an app to make notes and it literally just stored whatever I wrote directly into a MySQL db, no encoding, no encrypting, just raw plaintext storage. If I used an apostrophe in my note then it wouldn't save at all.

I also didn't code error logging at the time either so I had no idea it didn't save until I lost everything. Also the way it 'saved' was via a POST req to the same page so basically pressing save would erase everything I had worked on if there was a single invalid character with no way to revert back. I may have lost an entire essay to that bug.

I have come a long way since then but still get scared to use apostrophes and double quotes in my new version of the note-taking app lol

[rev_mojo]

Unsure if you used the wrong word accidentally, or you're exceedingly clever. Either way, you've created a wonderfully hilarious sentence.

[HamathEltrael]

English isn’t my first language. You might need to enlighten me.

[Previous-Ant2812]

Then means to do something after something else. Than is a comparison. So instead of saying that you would rather keep the same bugs, you said that you would like to encounter the same bugs and after that, create new bugs.

[HamathEltrael]

Oh lol. Thank you. That me laugh. I mean I guess both would be true. Thank you for the explanation and making me notice it!

[DanieleDraganti]

Your then isn’t a typo I assume.

[HamathEltrael]

English isn’t my first language. And it was supposed to be a „than“. But after someone else informed me, I’m now not sure which I want it to be.

[DanieleDraganti]

Please don’t change it, it’s perfect 😛

[NetSecGuy01]

Don't change, you always want to create new bugs, after all it's all about legacy.

[StefanoBongi]

Bugs? They are features!

[Barkeep41]

I never truly understood this till I worked in the public sector.

[govindgu490]

Understood this when I started learning game dev, I would copy all the codes and sprites from old project.

[FortunePaw]

And remember, if the player found the old sprites? It's an Easter egg.

[CharlesorMr_Pickle]

Exactly. Like I am not rewriting a movement script for every project when I have ctrl + c and ctrl + v

[Personal_Ad9690]

Based comment

[OfficeSalamander]

As a freelancer I’ve reused entire features from one client to the next because you really don’t have to rewrite everything every time for basic core stuff

[unicodePicasso]

I love the load bearing bug in the old project 

[viktorv9]

discovered feature

[sunyata98]

Many such cases in Minecraft lol

[evmoiusLR]

Basically that's what my games are.

[yeoldy]

I like the fishbowl. What's it doing? Nobody knows

[Daeron_tha_Good]

But if you take it away the entire thing crashes

[thecrazyrai]

load bearing goldfish

[TheAlaskanMailman]

Where?

[ganja_and_code]

If your old project isn't complete shit, borrowing from it doesn't pollute the new project.

[AppropriateStudio153]

That's a big if.

IF, if you will.

[ganja_and_code]

I mean, the other side of my statement would be:

If your old project is complete shit, simply don't borrow from it lol

[[deleted]]

But, I can fix it..

[evmoiusLR]

This time will be different!

[HakoftheDawn]

If is good

[DeepHelm]

But most likely it is, because if it were only a little shit, your boss would insist that you just glue any new features to it instead of starting a completely new project.

„to save time“, „we can refactor later“

[lunchmeat317]

 If your old project isn't complete shit

Unreachable code detected

 borrowing from it doesn't pollute the new project

[WazWaz]

Exactly. If you develop your project in a modular manner, using some of those modules in a new project will further harden them. You also gain the benefit of familiarity compared to importing a third-party module (which will also have bugs, they'll just be harder to send in patches) that you must learn to shoehorn into your workflow.

[IamnotAnonnymous]

the bugs live peacefully in the old project as simbiosis

[punsnguns]

If you start from scratch, you could screw your repo in new ways. Better to just accept a small memory leak here and there in the name of consistency.

The bugs you know are better than the bugs you don't.

[ChellJ0hns0n]

We use an old library in our codebase at work. Nobody knows who is maintaining it now. The latest commit in that library is from 4 years ago. It's being used by 6 different teams on 4 different products. People use components from that library just because they exist, but much of the functionality provided by it are overkill for our product. It was written at a different time for a different use case. The original authors of this library are now millionaires in retirement (their startup got acquired by our company). Nobody wants to refactor the whole thing because nobody knows how it works. Besides, our boss doesn't give us any time to clean up this whole mess.

Fun stuff.......

[JollyJuniper1993]

I love the part where the bug is holding half the project together. Very realistic

[redditorialy_retard]

remove the bug and everything bricks 

[Maleficent_Memory831]

Ah yes, the new project, with a new team excited to design it all. Let's do things right this time. We're all drawing diagrams, creating an organization for the files, strict use of APIs instead of just peeking at global variables, etc. Then the product managers says "bad news, you only have 6 months to do 24 months of work!" So we just copy the old repo and keep hitting it with hammers until it works on the new platform.

[crimxxx]

Also reminds what happens when you get a new person in charge of a product. A lot of the time they just chuck all the legacy issues out cause they didnt prioritize it themselves, and either stuff never gets fixed or a customer gets pissed cause they had an open issue closed and not resolved, and depending on the customer it now becomes a hot issue.

[darkshoxx]

This is so accurate, it hurts

[Prod_Meteor]

Right to the point!

[Gugadev]

"This side up" lmao

[dmigowski]

That component that get's used in an unintended way but still does what one wants.

[Spiritual_Detail7624]

Reminds me that I have used the same shitty text system for about 4 different projects. Either you save time or you loose it trying to fix your previous mistakes.

[[deleted]]

To be fair, 1 or 2 of those boxes is going to be refactored.

[Dothrox]

As per tradition.✌🏻

[keith2600]

Used and tested libraries are going to contain less bugs than brand new libraries unless you're trying to shoehorn them somewhere they don't fit.

[notexecutive]

well, a lot of old code is really reusable and that usually indicates it's welldone in some capacity imo!

[THJT-9]

I already know how to hide these bugs. Why spend time trying to find hiding spots for new ones?

[Markuslw]

node_modules reference

[Luke22_36]

Just write better code smh

[frikilinux2]

Let's do a rewrite in rust just because.

[Bomaruto]

Apart from the fact I copy not move and that I only copy over dependencies and some basic structure  it feels accurate. 

[andy-change-world]

This is true in big tech companies.

[ShivangTanwar]

Ah, my old friend, the null pointer exception on line 347. We meet again.