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.

1

+1 for downstream systems. We have a few APIs that would need to be checked... Hmm, and it may affect third-party systems that use the APIs. I'll have to think about that, thanks.

m-smith
– m-smith

2012-05-14 16:00:23 +00:00
Commented May 14, 2012 at 16:00
1

Haha. Both of answers have "As for your *, it sounds reasonable". Great minds think alike? :P

Oleksi
– Oleksi

2012-05-14 16:00:45 +00:00
Commented May 14, 2012 at 16:00
If the legacy system is essentially still in place, be sure to check the code that references those dates is appropriately wrapped to reference only the date or only the time when appropriate.

mikebabcock
– mikebabcock

2012-10-23 21:15:04 +00:00
Commented Oct 23, 2012 at 21:15

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 »