5
votes
3answers
134 views

Engineering a better solution, coming from existing codebase [duplicate]

The Code I have high-business-value daily-used-by-customer software that is written in PHP and spans approximately 600K lines of code. Customer for a long time needs, wants, and demands new features ...
2
votes
4answers
210 views

Considerations before rewriting a software component from scratch? [duplicate]

A piece of software is a patchwork of old and undocumented efforts. There are no comments, no documentation, and the code is hairy -- it involves Unix shell scripts that check for dummy files and then ...
15
votes
10answers
647 views

suggesting large changes/a rewrite as an intern

The context: it's an internal project (that I don't think a lot of people use) it's old we're updating it The issues: it abuses the mvc framework (no use of models, business logic in views, etc) ...
9
votes
5answers
818 views

When should you rewrite? [duplicate]

Possible Duplicate: When is a BIG Rewrite the answer? In Joel Spolsky's famous (or infamous) article Thins You Should Never Do, Part I, he makes the case that doing a rewrite is always a ...
2
votes
8answers
779 views

Should this code be rewritten or refactored?

There is a module in our telecoms equipment which is written in C. I think the code in this module has a bad smell because it has a number of symptoms: When new features are added to this module, ...
14
votes
9answers
1k views

We're not a software company. Is a complete re-write still a bad idea? [duplicate]

I understand the reasoning behind Joel Spolsky's article "Things You Should Never Do, Part I", but I always see it referenced in regards in situations where the end goal is the production of software. ...