Answering customer questions
time to read 1 min | 45 words
This made me laugh:
And yes, I am aware that laughing at my own action is… strange.
Markdown formatting
ESC to close
Markdown turns plain text formatting into fancy HTML formatting.
Phrase Emphasis
*italic* **bold**
_italic_ __bold__
Links
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"
Images
Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"
Headers
Setext-style:
Header 1
========
Header 2
--------
atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6
Lists
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
Blockquotes
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Horizontal Rules
Three or more dashes or asterisks:
---
* * *
- - - -
Manual Line Breaks
End a line with two or more spaces:
Roses are red,
Violets are blue.
Fenced Code Blocks
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Header IDs
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Tables
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |YellowDefinition Lists
Term 1
: Definition 1
Term 2
: Definition 2Footnotes
Body text with a footnote [^1]
[^1]: Footnote text here
Abbreviations
MDD <- will have title
*[MDD]: MarkdownDeep
Comments
@Ayende, Off-topic.
Every time i accidently use IE to read your blog, the RavenDBProfiler throws errors at me.
The error is on templates.forEach (line 13) - forEach throws "Object doesn't support this property or method"
Moti,
Your feedback is very important to us. We value customer feedback and participation. Your question has been forwarded to the responsible people who will contact you shortly with a full and complete answer.
In the meantime, would you like to complete a customer satisfaction survey?
Owen,
Your feedback is very important to us. We value customer feedback and participation. Your question has been forwarded to the responsible people who will contact you shortly with a full and complete answer.
In the meantime, would you like to complete a customer satisfaction survey?
I once asked a question on the RavenDB google group before I was a real paying RavenDB customer. In less than 30 minutes, the question was answered with "It's a bug, I just fixed it and it will be in the next nightly build" or something similar.
I (or rather the customer I was working for) became a paying RavenDB customer shortly thereafter.
Jason, it's really a blessing if customers don't mind being also beta-testers ;)
@Rafal,
There is no such thing as bug free software. And when you can get a fix within 24 hours as opposed to waiting 6 months for a service pack, or two years for a new release, that is a vastly better system for the customer.
When I first started experimenting with RavenDB about a month or so ago, honestly I've lost track of how long ago it was, could probably find it in the google group archives, I was having a problem starting the RavenDB server on both my home machine and the one at work. I gave a shout-out for help on the google group and after exchanging a couple of emails Oren contacted me on Skype and we had the problem resolved within 20 minutes or so. BTW, I never did figure out how NLOG got into the GAC on those two machines. I haven't found anything that was broken by removing it.
Comment preview