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.

the code in this case was already implemented, I have to improve it, because as I have mentioned earlier, the Upgrades or downgrades were made in a manual way, that left no trace of the actions, and so, the financial department was having issues to identify if one sale was Upgraded, or someone has been stealing the services from the company. The code, unfortunately is very rigid, and is very hard to optimize it in the short time I have to resolve the issue

Ange1
– Ange1

2015-09-28 07:25:08 +00:00
Commented Sep 28, 2015 at 7:25
Right, "so much code trying to second guess the indirection that you cannot fix it". In your own coding diary, try to keep track of your estimate about doing it "right" versus the time you spend patching around. It may be illuminating.

Charles Merriam
– Charles Merriam

2015-09-28 19:06:47 +00:00
Commented Sep 28, 2015 at 19:06

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 »