+972 52-548-6969
Coworker:
We see this issue on this use case, is this a bug?
Me:
Well, it works exactly the way we intended it to work, just not as the client expected it to work.
Markdown turns plain text formatting into fancy HTML formatting.
*italic* **bold**
_italic_ __bold__
Inline:
An [example](http://url.com/ "Title")
Reference-style labels (titles are optional):
An [example][id]. Then, anywhere
else in the doc, define the link:
[id]: http://example.com/ "Title"
Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"
Setext-style:
Header 1
========
Header 2
--------
atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6
Ordered, without paragraphs:
1. Foo
2. Bar
Unordered, with paragraphs:
* A list item.
With multiple paragraphs.
* Bar
You can nest them:
* Abacus
* answer
* Bubbles
1. bunk
2. bupkis
* BELITTLER
3. burper
* Cunning
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Three or more dashes or asterisks:
---
* * *
- - - -
End a line with two or more spaces:
Roses are red,
Violets are blue.
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |YellowTerm 1
: Definition 1
Term 2
: Definition 2Body text with a footnote [^1]
[^1]: Footnote text here
MDD <- will have title
*[MDD]: MarkdownDeep
And 2 more posts are pending...
There are posts all the way to Jul 31, 2017
| Main feed |
|
| Comments feed | |
Comments
I have seen this in cases where the customer was implementing a new process (so they had never done this before) and also when I had optimized a step (they expected to export an order file, then import it again, but I piped the data straight into the order processing system). Sometimes a report or a summary screen that gives a good overview of some internal operation will give the customer the confidence to accept your implementation of the process. Managing customer expectations is an ART, and I don't always do a good job when I am also the only developer on the project. It's all about communicating and managing expectations. If you do that well during the early phases of a project, the customer will usually be pleased by the results.
I guess the phrase "The customer is always right" doesn't apply here...
Comment preview