448
you are viewing a single comment's thread
view the rest of the comments
[-] NocturnalMorning@lemmy.world 2 points 3 months ago

Sure, refactoring is sometimes necessary. But refactoring also introduces new bugs often. Our code base is constantly being refactoring, and it's not more reliable, stuff is constantly breaking.

[-] MyNameIsRichard@lemmy.ml 5 points 3 months ago

Tell me that you don't have a test suite without telling you don't have a test suite

[-] NocturnalMorning@lemmy.world -3 points 3 months ago

Why are programmers so arrogant? They do have unit tests, and a dedicated test team. Refactoring can and does introduce bugs. It's a fact.

[-] MyNameIsRichard@lemmy.ml 3 points 3 months ago

Frankly, if your test suite isn't catching 95% or more of the bugs, there's a problem with the test suite and if uat aren't catching 95% or more of the remainder, there's a problem with uat

[-] luciferofastora@lemmy.zip 2 points 3 months ago

How solid is the unit test coverage? What about regression tests? If you get new bugs creeping in all the time, your bug-catchers aren't doing their job

[-] NocturnalMorning@lemmy.world 2 points 3 months ago* (last edited 3 months ago)

Yeah, I've said that before. I don't think they have enough regression tests, and unit tests.

[-] luciferofastora@lemmy.zip 2 points 3 months ago

I did a sting writing tests for a team that previously had none. Fun times, the things that were uncovered that day...

[-] magic_lobster_party@kbin.run 4 points 3 months ago

Refactoring for the sake of refactoring is rarely a good thing. It should be done with a clear purpose in mind.

this post was submitted on 06 Jul 2024
448 points (95.5% liked)

Programmer Humor

32281 readers
950 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS