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: 10 | Comments: 35

filter by tags archive

I refuse to be an [type] developer

time to read 1 min | 76 words

Recently I was asked, in two different situations, what kind of a developer I am. I refused. I am not a C# developer, or a database developer, or an agile developer (I don't even know what that means).

If pressed, I would admit that I am mostly familiar with the .Net platform, but I am not going to limit myself to that. I don't even believe that trying to put such tabs on people is useful.



As you said before, specialization if for insects.



Daniel Lidström

At the same time, who wants to be an amateur at many things, but pro at nothing?


I solve problems in with code. That answer works for me.


couldn't you be a Type() developer?

Mike Brown

I don't see myself as a developer at all. I see myself as a problem solver. The less code I have to write to get to a solution, the better in my eyes. The closer I can get a client to a solution with an off the shelf solution, the less code I have to code/maintain.

Of course there's a trade-off involved but you know what I mean.

That being said, I'd have to admit that my Java platform skills have diminished over the years I've been involved with .NET...I do have a strong natural aversion to learning/refreshing on a customer's dime (even to the extent of billing half when doing work that is exploratory). So even though I can claim more knowledge in Java development than most Java "consultants", my likelihood to accept a project drops significantly once Java enters the picture.

Neal Blomfield

why not simply "I am a good developer" (I would actually argue for great in your case but then people might accuse you of being arrogant)


Comment preview

Comments have been closed on this topic.


  1. Production postmortem: The case of the memory eater and high load - 2 days from now
  2. Production postmortem: The case of the lying configuration file - 3 days from now
  3. Production postmortem: The industry at large - 4 days from now
  4. The insidious cost of allocations - 5 days from now
  5. Find the bug: The concurrent memory buster - 6 days from now

And 4 more posts are pending...

There are posts all the way to Sep 10, 2015


  1. Find the bug (5):
    20 Apr 2011 - Why do I get a Null Reference Exception?
  2. Production postmortem (10):
    14 Aug 2015 - The case of the man in the middle
  3. What is new in RavenDB 3.5 (7):
    12 Aug 2015 - Monitoring support
  4. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats