+972 52-548-6969
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
No future posts left, oh my!
| Main feed | |
| Comments feed |
Comments
One subject in basic pure math that I wish all developers would take is factorization - taking an equation, recognising and removing the duplicates and simplifying.
I still can't fathom how a developer can see the same thing over and over again - like 6 lines of code repeated every single time an exception needs to be logged - and not recognize that they can factor it out.
Paul
"Using a naming convention where the company name is prefixed to all local variables"
I've witnessed a Database that was prefixed with the DEVELOPERS initials, as were all tables in it...
I still shiver while writing this.
If you count the brace lines, it's 6 lines for the exception, too. But absolute necessary unless
Castle.ActiveRecord.Framework.ActiveRecordException: Could not perform Save for Foo at ... in ...
is enough for you to see the error's cause, which isn't the case for me.
Markus, is there a reason that you are doing it this way?
ex.ToString() gives you the inner exception as well, after all
Hmm, it seems that the fact that I always use Logging now avenges. Perhaps I should have just used
Console.WriteLine(exception)
:-(
What is Logging?
No special product, I simply wrote it with a capital letter because I'm accustomed to that practice. German language capitalizes all nouns, hence "Logging" instead of logging.
Well, most of the logging frameworks that I am aware of will handle this correctly.
Windsor's LoggingFacility with loggingApi="console" obviously doesn't.
@Markus:
class LogHelper
{
{
Logger.WarnFormat(ex, format, args);
while (ex.InnerException != null)
{
ex = ex.InnerException;
Logger.Info("Inner Exception", ex);
}
}
Now in the many places you use that code, you can have:
try
{
ActiveRecordMediator<Foo>.Save(foo);
}
catch (Exception ex)
{
LogHelper.Log("Error saving Foo {0}", foo.Name, ex);
}
}
There are thousands of libraries which require multiple lines to do something. There's no reason you should write those multiple lines twice.
Comment preview