Ayende @ Rahien

Oren Eini aka Ayende Rahien CEO of Hibernating Rhinos LTD, which develops RavenDB, a NoSQL Open Source Document Database.

Get in touch with me:

oren@ravendb.net

+972 52-548-6969

Posts: 7,143 | Comments: 50,106

filter by tags archive

architecture (448) rss
bugs (396) rss
challanges (93) rss
community (309) rss
databases (344) rss
design (757) rss
development (494) rss
hibernating-practices (46) rss
humor (170) rss
miscellaneous (588) rss
performance (324) rss
programming (962) rss
raven (1210) rss
ravendb.net (191) rss
reviews (181) rss
uberprof (40) rss

2021
- April (6)
- March (11)
- February (15)
- January (14)
2020
- December (10)
- November (13)
- October (15)
- September (6)
- August (9)
- July (9)
- June (17)
- May (15)
- April (14)
- March (21)
- February (16)
- January (13)
2019
- December (17)
- November (14)
- October (16)
- September (10)
- August (8)
- July (16)
- June (11)
- May (13)
- April (18)
- March (12)
- February (19)
- January (23)
2018
- December (15)
- November (14)
- October (19)
- September (18)
- August (23)
- July (20)
- June (20)
- May (23)
- April (15)
- March (23)
- February (19)
- January (23)
2017
- December (21)
- November (24)
- October (22)
- September (21)
- August (23)
- July (21)
- June (24)
- May (21)
- April (21)
- March (23)
- February (20)
- January (23)
2016
- December (17)
- November (18)
- October (22)
- September (18)
- August (23)
- July (22)
- June (17)
- May (24)
- April (16)
- March (16)
- February (21)
- January (21)
2015
- December (5)
- November (10)
- October (9)
- September (17)
- August (20)
- July (17)
- June (4)
- May (12)
- April (9)
- March (8)
- February (25)
- January (17)
2014
- December (22)
- November (19)
- October (21)
- September (37)
- August (24)
- July (23)
- June (13)
- May (19)
- April (24)
- March (23)
- February (21)
- January (24)
2013
- December (23)
- November (29)
- October (27)
- September (26)
- August (24)
- July (24)
- June (23)
- May (25)
- April (26)
- March (24)
- February (24)
- January (21)
2012
- December (19)
- November (22)
- October (27)
- September (24)
- August (30)
- July (23)
- June (25)
- May (23)
- April (25)
- March (25)
- February (28)
- January (24)
2011
- December (17)
- November (14)
- October (24)
- September (28)
- August (27)
- July (30)
- June (19)
- May (16)
- April (30)
- March (23)
- February (11)
- January (26)
2010
- December (29)
- November (28)
- October (35)
- September (33)
- August (44)
- July (17)
- June (20)
- May (53)
- April (29)
- March (35)
- February (33)
- January (36)
2009
- December (37)
- November (35)
- October (53)
- September (60)
- August (66)
- July (29)
- June (24)
- May (52)
- April (63)
- March (35)
- February (53)
- January (50)
2008
- December (58)
- November (65)
- October (46)
- September (48)
- August (96)
- July (87)
- June (45)
- May (51)
- April (52)
- March (70)
- February (43)
- January (49)
2007
- December (100)
- November (52)
- October (109)
- September (68)
- August (80)
- July (56)
- June (150)
- May (115)
- April (73)
- March (124)
- February (102)
- January (68)
2006
- December (95)
- November (53)
- October (120)
- September (57)
- August (88)
- July (54)
- June (103)
- May (89)
- April (84)
- March (143)
- February (78)
- January (64)
2005
- December (70)
- November (97)
- October (91)
- September (61)
- August (74)
- July (92)
- June (100)
- May (53)
- April (42)
- March (41)
- February (84)
- January (31)
2004
- December (49)
- November (26)
- October (26)
- September (6)
- April (10)

Workshop Online - Best Practices and Performance

Feb 13 2013

RavenDB has the best users

time to read 1 min | 51 words

Talk about making my job easy. Thank you Barry, and I am sorry it took me 17 minutes to get the fix out.

Tweet Share Share 5 comments

Tags:

Comments

13 Feb 2013
11:01 AM

jon samwell

You've got the best business model in the world, don't pay developers just have the community fix your product! You should start offering reduced licenses for people who find/fix bugs. That should iron out a few more kinks in the product.

13 Feb 2013
12:24 PM

Kiliman

@jon I hope you were being sarcastic. Most of these types of bugs are edge cases that don't show up outside of real world use. Oren has a great track record of fixing these bugs quickly. Even quicker if the customer provides a failing test. If I'm not mistaken a bug report is NOT a bug fix.

13 Feb 2013
13:20 PM

jon samwell

@Killman of course!

13 Feb 2013
15:53 PM

Graham

There should actually be a strong incentive for users to do this. If they provide you a failing test for an issue, chances are you will incorporate that into your automated runs. Thus, the likelihood that the issue that broke them specifically will re-emerge has dropped drastically.

13 Feb 2013
20:57 PM

Bryan Johns

I wouldn't presume to expect any form of free or reduced price for a non-OSS license just for submitting a bug report, even one that came in the form of a failing test. But, that would be a nice incentive to go so far as to fork the github project, fix the bug, then issue a pull request.

A free or reduced license for use in closed source project(s) would be a nice bonus for getting a pull request accepted into the core. But if you think about it, having ones name in the list of contributors of such a large project would be a real bonus for the old resume and the value of that might far exceed the cost of a free production license.

Comment preview

Comments have been closed on this topic.

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):

![alt text](/path/img.jpg "Title")

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  |Yellow

Definition Lists

Term 1
: Definition 1
Term 2
: Definition 2

Footnotes

Body text with a footnote [^1]
[^1]: Footnote text here

Abbreviations

MDD <- will have title
*[MDD]: MarkdownDeep

FUTURE POSTS

AWS Roles, AWS Lambda and eventual consistency - about one day from now

There are posts all the way to Apr 12, 2021

RECENT SERIES

Building a phone book (3):
02 Apr 2021 - Part III
Building a social media platform without going bankrupt (10):
05 Feb 2021 - Part X–Optimizing for whales
Webinar recording (12):
15 Jan 2021 - Filtered Replication in RavenDB
Production postmortem (30):
07 Jan 2021 - The file system limitation
Open Source & Money (2):
19 Nov 2020 - Part II

View all series

Syndication

Main feed
Comments feed