Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,123 | Comments: 45,470

filter by tags archive

A developer so retarded

time to read 2 min | 294 words

I just run into this post, that talks about a presentation about mocking, and included this statement (about using Rhino Mocks):

I once heard a story about a developer so retarded that he and his team spent a good amount of time trying to debug a mock only to find out that he forgot about ReplayAll()*.  Who hires guys like that anyway?

That developer, it would be me, and it can happens quite often. And I wrote the tool, so I should know what I am doing when I am using it.

Stuff happens, it is easy to forget a line of code and waste some time as a consequences. The most common sentence from me when I am developing is "Oh, man, I am so stupid that I did that".

To give an example that would be a bit easier to grok, what is wrong with this code:

using(TransactionScope scope = new TransactionScope())
   Appointment[] appointments = SpanOnCalendar(appointmentSepc, DateTime.Today, DateTime.Today.AddDays(7));
   foreach(Appointment appointment in appointments)





The developer in question that I was talking about was ME. I forgot to put the note in there.

I have to edit that right away - now I just sound like an ass!


You forgot the commit.

Ayende Rahien

How many time did you made this error before you learned to see the code that isn't there?


Too many times to count :-)

Ken Egozi

A guy on my team has recently spent about two hours trying to figure why an email is not being sent from some action, just to find out that there's a AppConfig switch named "LogEmailsButDontSendThem", set to "True" on dev machines.

That's not about being a retarded dev. He is actually a very promising and talented young guy, and he is generally doing a very good work.

Shane Courtrille

Hahaha.. Justice is all about upsetting the big names these days :)


I think we know some key differences between Ayende and the Other Developer We Can Never Name Again Through Threat of Legal Action...;)

Comment preview

Comments have been closed on this topic.


  1. RavenDB 3.5 whirl wind tour: You want all the data, you can’t handle all the data - 3 days from now
  2. The design of RavenDB 4.0: Making Lucene reliable - 4 days from now
  3. RavenDB 3.5 whirl wind tour: I’ll find who is taking my I/O bandwidth and they SHALL pay - 5 days from now
  4. The design of RavenDB 4.0: Physically segregating collections - 6 days from now
  5. RavenDB 3.5 Whirlwind tour: I need to be free to explore my data - 7 days from now

And 13 more posts are pending...

There are posts all the way to May 30, 2016


  1. RavenDB 3.5 whirl wind tour (14):
    29 Apr 2016 - A large cluster goes into a bar and order N^2 drinks
  2. The design of RavenDB 4.0 (12):
    28 Apr 2016 - The implications of the blittable format
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series



Main feed Feed Stats
Comments feed   Comments Feed Stats