Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

1

The problem is when you add a hack here and a hack there and before you know it your hiring ten developers to get fixing all of the hacks that are in place. Hacks are a consequence of poor design.

chrisw
– chrisw

2011-04-11 15:12:35 +00:00
Commented Apr 11, 2011 at 15:12
True, but they can also be the consequence of the market and tough business decisions. Also, hacks vary by severity. You're right, and that's why I call it technical debt, because it has to be repaid eventually, and intrest can build up quickly over time until it can be unbearable and your team has to declare bankruptcy and rewrite the thing.

Ryan Hayes
– Ryan Hayes

2011-04-11 15:15:34 +00:00
Commented Apr 11, 2011 at 15:15
3

Yes, allowing a hack or two is ok given you allocate time to fix them after the release. This will slow you down after the deadline, but may be worth it (as compared to not releasing at all).

Martin Wickman
– Martin Wickman

2011-04-11 15:18:18 +00:00
Commented Apr 11, 2011 at 15:18
martinfowler.com/bliki/TechnicalDebtQuadrant.html - Martin Fowler on Technical Debt: when it's good and when it's not

alexanderbird
– alexanderbird

2016-04-22 07:08:17 +00:00
Commented Apr 22, 2016 at 7:08

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »