3 ms·
Other people's time is also valuable. Try not to write code that's impossible to read.
by jredwards 10y ago
Other people's time is also valuable. Try not to write code that's impossible to read.
- cloverich 10y agoI think pure style (e.g. that a linter would catch) and DRY could be treated separately. The former should always be followed. To the latter: I find weak or incorrect abstractions much harder to follow than repetitive code. And I find those much more commonly when implemented early rather than later. There's definitely a balance, and if you know the type of problem you are solving ahead of time you can probably abstract early. But if you're just kind of feeling around in the dark, which seems to be relatively common in complex business applications (for instance), I much appreciate an implement-test-reflect-refator cycle.
- AstralStorm 10y agoFor actual redesign, you end up with a long true refactoring iteration when no new features can be added. There is no guarantee you will not repeat the same mistakes or make it worse. It is a very tough sell to most customers. The quick cycle does not scale with project size.