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

The existing code is not stable. The users don't see most things as 'bugs' they see them as 'quirks.' So they area aware that in order for the program not to crash they have to check a mis-labeled checkbox before clicking OK. We have access to 1 of the maintainers of the project who joined about 5 years into its development. Time is our main concern. We would like to have something commercially available 'soon.' However, as-is the software is not sellable due to all the 'quirks.' There are many of them and we are unfamiliar with the code base.

Boumbles
– Boumbles

2013-09-17 14:00:43 +00:00
Commented Sep 17, 2013 at 14:00
That is a fairly strong indicator of the need to re-factor, and that the cost of delaying it may be quite high. However, you still need to be sure you know enough of what the product needs to do for this to be successful.

Michael Shaw
– Michael Shaw

2013-09-17 14:03:07 +00:00
Commented Sep 17, 2013 at 14:03
This approach only works if you have enough developers to do both things at the same time. Also, it's difficult to do a new architecture when you have zero knowledge of the existing product (which seems to be the case here).

17 of 26
– 17 of 26

2013-09-17 14:26:13 +00:00
Commented Sep 17, 2013 at 14:26
This is our current plan. We've got a couple guys working on fixing existing bugs while I work on porting to Qt. Bug fixes are merged as we go along. I'll be getting a few devs to help me with the port so hopefully we'll be working on fixing bugs in the Qt version sooner rather than later.

Boumbles
– Boumbles

2013-09-17 15:38:35 +00:00
Commented Sep 17, 2013 at 15:38

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 »