3 ms·
> When you find out that the architecture is wrong, do you fix it? Or do you just hack it to get the next bit to work? That's very project and organization dep
by davedx 13y ago
> When you find out that the architecture is wrong, do you fix it? Or do you just hack it to get the next bit to work?
That's very project and organization dependent. Some projects are short lived prototypes (I'm working on one now) that are for internal use only, so it makes sense to try and get the damn thing finished without worrying too much about architecture.
Other projects are built to last, or have very high quality requirements, so you want to really get the architecture right, even if that means costly rewrites.
- BugBrother 13y ago(Reading this a few days later in an open tab. :-) ) Imho the most important thing is to have a good design document for the data model. Partly because it often decides a lot of the structure of the code. It is e.g. easier to rewrite code than realize that you lack some stuff you should have captured about customers years ago...