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

2

Regardless of the assumptions in the preface and background, this doesn't answer the fundamental question of "how to favor fast over clean in practice"

Gulzar
– Gulzar

2022-04-11 09:15:30 +00:00
Commented Apr 11, 2022 at 9:15
@Gulzar I've expanded my answer to try to make it more clear. The TLDR is, writing "unlclean" code is not only not a guarantee of getting things done faster, it may in fact slow you down. If you want fast and dirty, just write as fast as you can and write dirty code. It may get you to your endpoint faster or may not, and the "dirty" code may or may not be a disadvantage then or later on.

cjs
– cjs

2022-04-12 09:26:33 +00:00
Commented Apr 12, 2022 at 9:26

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 »