What can I do to maintain respect for a poorly written codebase? [duplicate]
This question already has answers here: I’ve inherited 200K lines of spaghetti code — what now? (19 answers) Closed 11 years ago. In my job I have to maintain a poorly written codebase which is both hard to understand, has tons of comments that are just plain wrong, has a bunch of weird decisionmaking going […]
How should I behave as a developer in a project that’s headed for failure?
Want to improve this post? Provide detailed answers to this question, including citations and an explanation of why your answer is correct. Answers without enough detail may be edited or deleted. I am a developer in a 5-member team and I believe our project is headed for disaster. I’ll describe why in a moment, but […]
What to do as a Dev when for years their team has lacked product innovation, not used project mgmt methodologies, and kept bad Software Dev practices? [closed]
Closed 10 years ago.
Painfully Stupid Method Names in Legacy Code: Fix or Leave as Warning? [duplicate]
This question already has answers here: Best Practices for Renaming, Refactoring, and Breaking Changes with Teams (3 answers) Closed 11 years ago. For this case let’s assume something like… “removedNonPriceChangingConfermations” that is in no way relating to things that happened in the past tense, nor does it return a list of removed items (which you […]
Painfully Stupid Method Names in Legacy Code: Fix or Leave as Warning? [duplicate]
This question already has answers here: Best Practices for Renaming, Refactoring, and Breaking Changes with Teams (3 answers) Closed 11 years ago. For this case let’s assume something like… “removedNonPriceChangingConfermations” that is in no way relating to things that happened in the past tense, nor does it return a list of removed items (which you […]
Painfully Stupid Method Names in Legacy Code: Fix or Leave as Warning? [duplicate]
This question already has answers here: Best Practices for Renaming, Refactoring, and Breaking Changes with Teams (3 answers) Closed 11 years ago. For this case let’s assume something like… “removedNonPriceChangingConfermations” that is in no way relating to things that happened in the past tense, nor does it return a list of removed items (which you […]
Painfully Stupid Method Names in Legacy Code: Fix or Leave as Warning? [duplicate]
This question already has answers here: Best Practices for Renaming, Refactoring, and Breaking Changes with Teams (3 answers) Closed 11 years ago. For this case let’s assume something like… “removedNonPriceChangingConfermations” that is in no way relating to things that happened in the past tense, nor does it return a list of removed items (which you […]
Painfully Stupid Method Names in Legacy Code: Fix or Leave as Warning? [duplicate]
This question already has answers here: Best Practices for Renaming, Refactoring, and Breaking Changes with Teams (3 answers) Closed 11 years ago. For this case let’s assume something like… “removedNonPriceChangingConfermations” that is in no way relating to things that happened in the past tense, nor does it return a list of removed items (which you […]
Painfully Stupid Method Names in Legacy Code: Fix or Leave as Warning? [duplicate]
This question already has answers here: Best Practices for Renaming, Refactoring, and Breaking Changes with Teams (3 answers) Closed 11 years ago. For this case let’s assume something like… “removedNonPriceChangingConfermations” that is in no way relating to things that happened in the past tense, nor does it return a list of removed items (which you […]
I have 200k lines of poorly designed code, will units tests or integration tests be more valuable? [duplicate]
This question already has answers here: I’ve inherited 200K lines of spaghetti code — what now? (19 answers) What is the most effective way to add functionality to unfamiliar, structurally unsound code? [duplicate] (7 answers) Closed 11 years ago. I’ve inherited a lot of poorly designed code; the code has no tests. I am putting […]